Re: Tracing an ORA-01410 error
Date: Fri, 6 Feb 2009 13:29:09 +0100
If you're experiencing ORA-1401, but set the errorstack trace for ORA-1440 -- you will not see any information at all :)
The number you're putting into the alter session command has to be the number of the oracle-error you're getting. You'll see a tracefile with the stacktrace and the current sql statement executing (along with a whole lot of other information). Just try it out, no harm done:
alter session set events '942 trace name errorstack level 1';
select * from does_not_exist; -- this causes ora-942
then check your user_dump_dest for the tracefile.
On Thu, Feb 5, 2009 at 10:12 PM, Schauss, R. Peter (IT) < peter.schauss_at_ngc.com> wrote:
> Oracle 220.127.116.11/ Solaris 9
> Some of our user reports are failing with ORA-1401- invalid rowid
> errors. Searching the archives I found a suggestion that I turn on
> tracing for this error with the command:
> alter session set events '1440 trace name errorstack forever, level 3';
> What kind of information can I expect to get from this trace?
> Peter Schauss