interface suggesions

[Dmitry A Rybakov]

1) one more tab for program window : "Session information".
It would be usefull to watch fields from gv$session and other views for current session of current window. Also adding button for current session killing would be usefull.

2) dbms output window
a) watch dbms_output data while script is running
b) indicate if output uccured without visiting output tab.
c) possibility to place output window below script to view both script and ouput simultaneously

3) Before package compilation check if it is possible. I mean check if package is not locked. Sometime i start package compilation but it is locked so i need to wait about 10 minutes to get timeout.

Best wishes,
Dim

 

[patch]

You could perhaps use a system level trigger to check this. Have this raise an exception to stop compilation or something like that. Read a bit about this:http://bar-solutions.com/weblog/?p=326

 

[Marco Kalter]

I have added this to the list of enhancement requests. Note that 2a may not be possible. The output buffer is restricted to the session that is running the script.

 

[RobertK]

Time to read the fine manuals.

1) one more tab for program window : "Session information".
It would be usefull to watch fields from gv$session and other views for current session of current window.

Why specifically "for program window" ?

Have you seen : "Toos > Sessions" ?
You can define your own queries there under "Define session queries"
I have one called "my_session" for this:

SELECT username,:sid "sid",serial#,status,osuser,machine,program,module,action,logon_time,saddr,audsid,paddr,user#,
command,ownerid,taddr,lockwait,server,schema#,schemaname,process,terminal,client_info
FROM v$session WHERE audsid = sys_context('userenv', 'sessionid')

2) dbms output window
a) watch dbms_output data while script is running
b) indicate if output uccured without visiting output tab.
c) possibility to place output window below script to view both script and ouput simultaneously

"dbms_output" does not work that way. It is server-side buffer.
You get the whole output in all at the END of the code run, NOT during run-time.
Suggest you log to a table if you have to see it real-time.

3) Before package compilation check if it is possible. I mean check if package is not locked.
Sometime i start package compilation but it is locked so i need to wait about 10 minutes to get timeout.

And you probably "messed up" the other session(s) that are using that package at the time.
Someone correct me if I'm wrong but I don't think "lock on package" can be checked.

Check "v$access" before you compile.

 

[Dmitry A Rybakov]

Time to read the fine manuals.
SELECT ...
FROM v$session WHERE audsid = sys_context('userenv', 'sessionid')

I am aware about this feature but this query shows main session. But i think about session information bound to the running window. I need always guess what session is bound to target window.

Actually most usefull for me is "Kill current session" button placed at running window.

But event this button not enough. Sometime I need to know process_id in order to kill oralce process. This is sad need of oracle database.

2) dbms output window
a) watch dbms_output data while script is running
b) indicate if output uccured without visiting output tab.
c) possibility to place output window below script to view both script and ouput simultaneously

"dbms_output" does not work that way. It is server-side buffer.
You get the whole output in all at the END of the code run, NOT during run-time.

Sorry, you are wrong. One thread can execute script while another thread can read buffer. Both threads should use the same session with thread safe mode.

I tested this feature with Delphi and Oracle 10 few minutes ago. I can event post source code and screenshots.

Suggest you log to a table if you have to see it real-time.

Too long way.

3) Before package compilation check if it is possible. I mean check if package is not locked.
Sometime i start package compilation but it is locked so i need to wait about 10 minutes to get timeout.

And you probably "messed up" the other session(s) that are using that package at the time.
Someone correct me if I'm wrong but I don't think "lock on package" can be checked.

Check "v$access" before you compile.

I use query below to kill session which impede compilation. But this is not a good way. Sometime i get annoying deadlocks when package is locked for recompillation, and other sessions locked waiting recompilation.

select
s.MODULE,
s.OSUSER,
t.*,
'ALTER SYSTEM KILL SESSION '''|| sid||', '||serial#||''';'
from dba_ddl_locks t ,
v$session s
where name = 'THE-NAME' and t.type='Body'
and s.SID=t.session_id;

May be this feature should be included into extended version of pl/sql dev

 

[RobertK]

sounds like you're pretty good w/ Delphi-on-Oracle programming...maybe AAA can use some consulting w/ you

 

[Dmitry A Rybakov]

Lets discuss this by email,
dim1r@yandex.ru