Re: Tracing an ORA-01410 error
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: peter.schauss@xxxxxxx
- Date: Fri, 6 Feb 2009 14:23:46 +0000
If you don't want to set an event, you will probably find that you can write
a trigger on the AFTER SERVERERROR system event to catch this in action. I
blogged about this getting on for 5 years ago (that's scary in itself) at
http://www.niall.litchfield.dial.pipex.com/archive/2004_06_01_archives.html -
blogger doesn't get the link correct in the archives - my script is at
http://www.niall.litchfield.dial.pipex.com/scripts/utils/server_error.zip.
Usual warnings about blindly downloading stuff off the interweb and running
in production apply, in particular
1) read the script first
2) note Larry's warning in my June16th update that likely doesn't apply to
you.
You can use the approach I outline for more that just 1410, and you can
switch it off and on without bouncing the database just be
enabling/disabling the trigger or deleting rows from a table. if you get
this frequently think about just capturing a representative occurrence or
two and not bothering again.
Niall
On Thu, Feb 5, 2009 at 9:12 PM, Schauss, R. Peter (IT) <
peter.schauss@xxxxxxx> wrote:
> Oracle 8.1.7.4/ 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?
>
> Thanks,
> Peter Schauss
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
