![]() Step a) in a quiet database, run the script Currently Executing Packages ****ġ prompt **** Currently Executing Packages ****Ĥ 7, 'PROCEDURE', 8, 'FUNCTION', 9, 'PACKAGE', 12, 'TRIGGER', 13, Where module||action||client_info is not null Īnother possible idea : the following script was adapted from the original idea & research from Steve Adams (I tested in Personal 8ir3 and it worked as desired : Y.sql_text not like '%RAWTOHEX(SQL_ADDRESS)%')ĭbms_output.put_line( '-' ) ĭbms_output.put_line( x.logon_time || ' ' ||Ĭolumn client_info format a30 word_wrapped If ( y.sql_text not like '%listener.get_cmd%' and To_char(sysdate,' Day HH24:MI') current_time,Īnd username is not null order by last_call_et )įor y in ( select max(decode(piece,0,sql_text,null)) || To_char(LOGON_TIME,' Day HH24:MI') logon_time, Select username, sid, serial#, process, status sqlplus uses it to show you what script someone is running for example. showsql exposes this information to you as well. In this fashion, you can see where in a procedure someone is based on the values in these columns. #PL SQL DEVELOPER 7.1 SERIAL NUMBER CODE#What I like to do is have everyone "instrument" their code with calls to dbms_application_info which can fill in the client_info, action, and module columns in v$session. if the plsql is doing lots of PLSQL work - you'll see that code. If the plsql is doing SQL, you'll see the SQL. If someone is executing PLSQL, what you will see will depend on what the plsql is currently doing. ![]() It shows everyone logged in and if they are active, what they are doing and how long they've been doing it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |