(repost)
Few comments inline:
> 1. Easier, but requires a bounce : Add the
following event into init.ora> > event="1652 trace name
processstate level 10"
You can use alter system and dbms_system.set_ev in
combination to force an event for all new and existing sessions, without a
bounce (al
Few comments inline:
> 1. Easier, but requires a bounce : Add the
following event into init.ora> > event="1652 trace name
processstate level 10"
You can use alter system and dbms_system.set_ev in
combination to force an event for all new and existing sessions, without a
bounce (alter syste
> 1. Easier, but requires a bounce : Add the
> following event into init.ora
>
> event="1652 trace name processstate level 10"
You should be able to set this dynamically as well (tested on 8.1.7).
SQL> alter system set events '1652 trace name processstate level 10';
System altere
John has already shown you how to generate a trace when
an error is encountered via the 'events' mechanism.
If you would like to see what events are available,
peruse the file $ORACLE_HOME/rdbms/mesg/oraus.msg if
you are on *nix. If you are on win32, the file is
unfortunately not available.
Star
You could also use a trigger to get the info to a temp table as follows. This will probably fire after any error and could be performance hit. (happy new year to all). :
create or replace trigger system.server_1652_error_trig
after servererror
on database
declare
v_audsid number;
v_usernam
Chris,
There are two options:
1. Easier, but requires a bounce : Add the following event into init.ora
event="1652 trace name processstate level 10"
This will dump the processstate for processing that encounter an ORA-01652.
And you can even add the following to capture 1555 and 4031 errors
e
