Re: set events: control the number of sessions that dump trace

Jared, Oracle will always dump trace for ORA-01555 and ORA-00060 (snapshot too old and deadlock). Also, trace will be dumped for ORA-00600 and ORA-07445. There is no need to trap snapshot too old separately. As for limiting the number of session that will report the error, this error normally happens very infrequently so it's not like you should be getting it every 10 seconds.

On 8/20/19 12:47 PM, Jared Still wrote:
> Hello,
>
> Does anyone know if it is possible to control the total number of
> trace files created by 'alter system set events' ?
>
> For example,  the following command will cause all sessions to dump
> stack traces when there have been at least 2 occurrences (armcount) of
> ORA-1555 in a session:
>
>   alter system set events '1555 trace name errorstack level 3,
> armcount 2, lifetime 2';
>
> After 2 events have occurred (lifetime) then the session will stop
> dumping stacks for this error.
>
> What I would like to be able to do is limit this system wide.
>
> Say for instance 3 sessions dump stack traces for ORA-1555.
>
> I would like to limit this to N system wide dumps of stack trace.
>
> So after 3 sessions have created a trace file, no other sessions
> should do so.
>
> The reason is that if left unattended, when many session incur
> ORA-1555, then this could potentially be quite a few rather large files.
>
> The idea of course is to be able to set and forget, until the next event.
>
> And yes, I know that TFA could be setup to deal with this, but that is
> another story...
>
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> Principal Consultant at Pythian
> Pythian Blog http://www.pythian.com/blog/author/still/
> Github: https://github.com/jkstill
>
>

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