Yes, there may be lots of transactions in a session, but they're delimited by XCTEND lines. If you're using autonomous transactions, it might be a little tricky, but if you're not, then the job should be very straightforward. Cary Millsap On Tue, Feb 3, 2009 at 11:05 AM, Vishal Gupta <vishal@xxxxxxxxxxxxxxx>wrote: > yes trace is one of the way. But then there could be lot of transactions in > a session. I was more interested in finding information from v$ or x$ views. > > Say, you have session blocking another session. And you can find out what > objects are locked by blocking session and identify the session as well. But > one wanted to find out all the SQL statements already executed by this > blocking session in current transaction, how do you generate this list. > V$TRANSACTION gives information about current SQL_ID and pre_sql_id. But not > all of them. > > Regards, > Vishal Gupta > http://www.vishalgupta.com > > ________________________________ > > From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Cary Millsap > Sent: Tue 03/02/2009 16:07 > To: Vishal Gupta > Cc: oracle-l@xxxxxxxxxxxxx > Subject: Re: List of SQL involved in a transaction > > > dbms_monitor.session_trace_enable > > Cary > > > > On Tue, Feb 3, 2009 at 9:59 AM, Vishal Gupta <vishal@xxxxxxxxxxxxxxx> > wrote: > > > Hi, > > Does anyone know how to find list of all the SQLs involved in a > transaction? > > Regards, > Vishal Gupta > > http://www.vishalgupta.com > > >