As far as I know, the SQL statement level trace is only available as of 11g. http://oraclue.com/2009/03/20/oracle-diagnostic-events-part-4/ http://oraclue.com/2009/03/24/oracle-event-sql_trace-in-11g/ For instance, alter system set events 'trace[sql_costing][sql:<sql_id_here>]'; -- 10053 alter system set events 'sql_trace[sql:<sql_id_here>]'; -- 10046 But in 10g and lower, the lowest level of the diagnostic event is the SESSION. ================================ Dion Cho - Oracle Performance Storyteller http://dioncho.wordpress.com (english) http://ukja.tistory.com (korean) http://dioncho.blogspot.com (japanese) http://ask.ex-em.com (q&a) ================================ 2010/3/2 Rich <richa03@xxxxxxxxx> > Hi all, > > This is 64-bit 10.2.0.4 on RHEL 5.1 (kernel 2.6.18-53). > > Is there any way to set 10046 and/or 10053 tracing on for a single SQL > statement in another session without access to the SQL code? > > Thanks, > Rich > -- > //www.freelists.org/webpage/oracle-l > > >
