I know that, but the DBA doesn't have to learn about oradebug and events any more. If only oracle would come up with DBMS_DISEMBOWEL_OPTIMIZER to replace 10053. On 03/03/2004 10:51:11 AM, Tanel Põder wrote: > > So, event 10046 is no longer necessary, the tracing mechanism can do that > with the usual SQL_TRACE. > > The "usual SQL_TRACE" is event 10046 at level 1 :) > > Tanel. > > > ---------------------------------------------------------------- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > ---------------------------------------------------------------- > To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx > put 'unsubscribe' in the subject line. > -- > Archives are at //www.freelists.org/archives/oracle-l/ > FAQ is at //www.freelists.org/help/fom-serve/cache/1.html > ----------------------------------------------------------------- > ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------