RE: Chasing a session...

Yep and if you have SQL statement logging as a requirement for future (e.g.
not just ad hoc), then you could set up fine grained auditing (DBMS_FGA).
 
FGA is able to log both SQL statements plus bind variables. Of course you
need storage for logging all that..
 
Tanel.



  _____  

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Anjo Kolk
Sent: Friday, August 25, 2006 20:33
To: tim@xxxxxxxxx
Cc: oracle-l
Subject: Re: Chasing a session...


The only real way is by sampling or tracing .......


On 8/24/06, tim@xxxxxxxxx <tim@xxxxxxxxx> wrote: 

Depending on how the application is written, then V$OPEN_CURSOR might
provide what you are looking for -- a "history" of SQL statements executed
by a session.  However, it is at best only the most primitive of logging for
that purpose, and if the application takes care to close unused cursors, it
will be a misleadingly incomplete history.  So, you almost have to hope for
a sloppily written application, which is sadly not too much to hope for...
:-) 

Just an idea...

Other related posts: