Re: application's raised error going to alert log
Date: Wed, 01 Sep 2010 10:55:48 -0400
Message-Id: <8CD17FCE56D7008-13C4-7DCB_at_web-mmc-m10.sysops.aol.com>
Oh, nope. no traces. The company who made the app is also inserting a record into an error log table. Maybe i should just ask them to do that and cut out the RAISE_APPLICATION_ERROR statement in the TRIGGER.
-----Original Message-----
From: Nigel Thomas <nigel.cl.thomas_at_googlemail.com>
To: lyallbarbour_at_sanfranmail.com
Sent: Wed, Sep 1, 2010 10:48 am
Subject: Re: application's raised error going to alert log
No, I meant has someone already set a trace for it (perhaps in init.ora, or a login trigger)?
On 1 September 2010 15:27, <lyallbarbour_at_sanfranmail.com> wrote:
It's a user defined error number. ora-20247 the application is using for this particular error. i haven't tried to trace it yet.
-----Original Message-----
From: Nigel Thomas <nigel.cl.thomas_at_googlemail.com>
To: lyallbarbour_at_sanfranmail.com
Cc: rjamya_at_gmail.com; oracle-l_at_freelists.org
Sent: Wed, Sep 1, 2010 9:52 am
Subject: Re: application's raised error going to alert log
What error number is it using? I believe ORA-006xx errors get written to alert log more or less automatically (but you shouldn't be using them for user exceptions, which start at 20000).
You can trace errors by number eg (ref http://wiki.oracle.com/page/Events):
ALTER SESSION SET EVENTS='6502 trace name ERRORSTACK level 1'
will cause all 6502 errors to be caught and added to the process trace file (not the alert log though). And of course you could set this in the pfile/spfile rather than by session.
Regards Nigel
On 1 September 2010 14:34, <lyallbarbour_at_sanfranmail.com> wrote:
The application code is calling RAISE_APPLICATION_ERROR with it's own user-defined PRAGMA EXCEPTION and text, but the TRIGGER that called the package to call raise_application_error isn't handling that error. I think that's why it's going to the alert log. Am i on the right track, anyone? i don't see ksdwrt anywhere in the application's code and DBMS_SYSTEM is wrapped, so i don't know if RAISE_APPLICATION_ERROR is calling it.
Lyall
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Sep 01 2010 - 09:55:48 CDT