Re: application's raised error going to alert log
- From: lyallbarbour@xxxxxxxxxxxxxxx
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 01 Sep 2010 11:42:41 -0400
The end user doesn't get an error. End user can see errors if the navigate to
the screen that shows the rows in this error_logs table. The user defined
error is visible on top of the table insert, in the alert log, which is kind of
useless to me, the dba, since i can't fix that problem on the application side.
I'm really just trying to understand why this user defined error went to the
alert log in the first place. Alert log doesn't seem the place for those kinds
of errors. Should be seen on the screen for the end user to fix their problem.
-----Original Message-----
From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
To: lyallbarbour@xxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Sent: Wed, Sep 1, 2010 11:32 am
Subject: Re: application's raised error going to alert log
What is the issue here? That sounds like relatively sensible error handling -
log the error to a table and the alert log so that monitors pick it up and
diagnosis can happen at a suitable point and then raise an exception for the
end user.
On 1 Sep 2010 15:58, <lyallbarbour@xxxxxxxxxxxxxxx> wrote:
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@xxxxxxxxxxxxxx>
To: lyallbarbour@xxxxxxx
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@xxxxxxxxxxxxxxx> wrote:
>
> It's a user defined error num...
Other related posts:
