Yes. Every piece of pl/sql ever written can tell v$session exactly what it is doing via Dbms_application_info. I've earned good one over the years because it didn't so please don't tell anyone;-( On 5/13/09, Jared Still <jkstill@xxxxxxxxx> wrote: > On Wed, May 13, 2009 at 12:17 PM, Paresh Patel > <paresh.patel@xxxxxxxxxxxxxx>wrote: > >> I have one procedure which contains no of DML statements. We have used >> DBMS_SCHEDULER to kick off this procedure every night. This procedure gets >> stuck intermittently and we tried to find out the exact SQL statement >> which >> is getting stuck using data dictionary views but we couldn’t as Oracle >> server doesn’t provide SQL_ID/SQL_HASH_VALUE/SQL_ADDRESS or in v$SESSION. >> If anyone has any idea please do let me know. >> >> Hmm, hit the space bar and gmail thought it was <SEND> ... > > I will try again. > > What does 'stuck' actually mean? > > Error messages? > > Is this a procedure you can modify? > > If so, then instrument it to do logging, and you can easily see where it > dies. > > > Jared Still > Certifiable Oracle DBA and Part Time Perl Evangelist > -- Sent from Google Mail for mobile | mobile.google.com Niall Litchfield Oracle DBA http://www.orawin.info -- //www.freelists.org/webpage/oracle-l