Re: EVENT 10053 not working

Dusan Bolek wrote:
> I do not understand it at all now. I have tried to trace a simple
> non-distributed query in the same database to get at least used
> parameters used by optimizer (the second 10053 trace section) to
> compare them side by side, but I do not get any information. The whole
> trace file looks like this:
>
> Dump file c:\oraadmin\db89\udump\db89_ora_5440.trc
> Tue Jan 31 08:37:59 2006
> ORACLE V9.2.0.7.0 - Production vsnsta=0
> vsnsql=12 vsnxtr=3
> Windows 2000 Version 5.2 Service Pack 1, CPU type 586
> Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
> With the OLAP and Oracle Data Mining options
> JServer Release 9.2.0.7.0 - Production
> Windows 2000 Version 5.2 Service Pack 1, CPU type 586
> Instance name: db89
>
> Redo thread mounted by this instance: 1
>
> Oracle process number: 9
>
> Windows thread id: 5440, image: ORACLE.EXE
>
>
> *** 2006-01-31 08:37:59.830
> *** SESSION ID:(18.2289) 2006-01-31 08:37:59.830
> QUERY
> select * from trace_test
> *** 2006-01-31 08:44:49.116
> QUERY
> alter session set events '10053 trace name context off'
>
> --
> Dusan Bolek

Dusan,

I believe you are not doing this right.

It appears that you are trying to get the 10053 trace using the
following:

alter session set events '10053 trace name context forever, level 1';

select * from trace_test;

alter session set events '10053 trace name context off';

While you should be doing this:

alter session set events '10053 trace name context forever, level 1';

EXPLAIN PLAN FOR select * from trace_test;

alter session set events '10053 trace name context off';


.... Also make sure that the table is analyzed (i.e. CBO is being used)
otherwise the trace will not show any trace details.

HTH

Anurag

.

Relevant Pages