Re: set trace

From: Stefan Koehler <contact_at_soocs.de>
Date: Sat, 29 Aug 2015 10:46:46 +0200 (CEST)
Message-ID: <290690346.43413.1440838006194.JavaMail.open-xchange_at_app04.ox.hosteurope.de>

Hi Michael,
at first we should know what this event is doing.

shell> oerr ora 45053
45053, 0000, "Internal Debugging Event"

// *Document: NO
// *Cause:    This is an internal debugging event, and must be enabled
//            only under the supervision of Oracle Support Services or
//            development.
// *Action:   N/A

Based on your previous question about sub-pools in relation to this (undocumented) event, i guess you are suffering latch contention on dictionary / row cache or shared pool. This is related to bug #13902396. This fix is disabled by default and can be enabled with the mentioned event (and level). Be aware this is not about tracing!

> how can I check the database that it's running.
Best source for this: http://blog.tanelpoder.com/2013/10/07/why-doesnt-alter-system-set-events-set-the-events-or-tracing-immediately/

If you want to know more about the event syntax (and why it is called "trace") - for sure Tanel Poder again: http://blog.tanelpoder.com/2009/03/03/the-full-power-of-oracles-diagnostic-events-part-1-syntax-for-ksd-debug-event-handling/

Best Regards
Stefan Koehler

Freelance Oracle performance consultant and researcher Homepage: http://www.soocs.de
Twitter: _at_OracleSK

> Michael Calisi <oracle455_at_gmail.com> hat am 29. August 2015 um 04:52 geschrieben:
>
> If i set this trace
> 1 how can I check the database that it's running.
> 2. what's the best way to stop the trace?
>
> alter system set events '45053 trace name context forever, level 127';
>
> System altered.
 

--
http://www.freelists.org/webpage/oracle-l

Received on Sat Aug 29 2015 - 10:46:46 CEST