| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Can't get rid of event "1403 trace name errorstack"
To check if it is really still set for the instance:
oradebug dump events 4
Or are some sessions still active that are still seeing the event at the
process level or at the session level. This is more difficult to determine.
I think if you get a process id list from ps for dedicated server
connections, attach to those with:
oradebug setospid
and then dump events at level 2 for each of them, you’ll find one or more
with the event still set.
If not, and you are running shared server, you can find the sessions
attached in shared server config and doe the same type of thing – attach to
the session:
oradebug setorapid
then dump events at level 1 for each session.
A much easier way would be to bounce the instance, but this may not be possible.
PS Please correct me if any of this is incorrect.
Hello list,
at a client, we've set event 1403 trace name errorstack to track down a batch process that exits with this error, and have therefore set the event using
alter system set events '1403 trace name errorstack level 1';
which worked fine.
but now, we can't get rid of the event anymore, even after turning it off using
alter system set events '1403 trace name errorstack off';
there are still *occasional* entries in the alert log of an ora-1403 happening (not as frequently as when it was active in the whole instance - which was a lot as Oracle internally raises this event with virtually every select statement -- see note 271490.1 ).
database will be bounced tonight either way - but I'd like to know why this happened, and how to get rid of it in case it would happen to me again
Regards Stefan
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Jun 19 2006 - 16:22:08 CDT
 |
 |