Hi Jonathan,
You are right. it is per session .
Yes i am concerned about lot of sessions doing the dumps , there are like
7000 sessions through app and i dont want trace directory to get flooded.
Is there a way we can limit database wide to just 2 or some number i
decide?
On Tue, Nov 19, 2019 at 9:49 AM Jonathan Lewis <jonathan@xxxxxxxxxxxxxxxxxx>
wrote:
When you say "keeps dumping" do you mean a single session keeps dumping ?
Or are you concerned that you see lots of sessions doing dumps ?
You've used alter system, so every session gets a lifetime of 2. (In
fact, on some tests I did a while back when messing about with an
ORA-01652, it looked like I got "lifetime" (nearly identical) error stacks
at the same time on one occurrence of the error, but only got dumps on the
first dump.)
Regards
Jonathan Lewis
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of kunwar singh <krishsingh.111@xxxxxxxxx>
Sent: 19 November 2019 13:52
To: ORACLE-L
Subject: How to use "lifetime" clause to limit the number of traces
correctly
Hi Listers,
I am reading this link:
https://blog.tanelpoder.com/2009/03/03/the-full-power-of-oracles-diagnostic-events-part-1-syntax-for-ksd-debug-event-handling/
then i tried to test the tracing using the below example.
alter system set events '942 trace name errorstack level 3,lifetime 2';
but it keeps dumping error stack even after 2nd incident of the error.
Is something broken/wrong with my syntax or tracing level or do i have use
some alternative syntax.
I am trying this in 12.2.0.1 .
The reason i am playing with it is to troubleshoot issue in an 11.2.0.4
for a different ORA error thrown by the application.
--
Cheers,
Kunwar
