RE: application's raised error going to alert log

Lyall

 

This should be simple 

Start with writing a small piece of test code that does
raise_application_error -

You will see that the default behavior of this is NOT to log error into
alert log

If it was sql forms and all plsql code would be filling up the alert log

From there review what the code is doing and how the error lands up in
the alert log.

As someone pointed out the only way that I also know of getting user
messages into alert log is via ksdwrt

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
lyallbarbour@xxxxxxxxxxxxxxx
Sent: Wednesday, September 01, 2010 9:34 AM
To: rjamya@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: application's raised error going to alert log

 

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

 

 

-----Original Message-----
From: rjamya <rjamya@xxxxxxxxx>
To: lyallbarbour@xxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Sent: Wed, Sep 1, 2010 8:33 am
Subject: Re: application's raised error going to alert log

I'd check the dependency of that package body, if it uses dbms_system
then your pacjage could be using dbms_system.ksdwrt call to output to
alert.log. 

 

-- Raj

On Wed, Sep 1, 2010 at 8:05 AM, <lyallbarbour@xxxxxxxxxxxxxxx> wrote:

Why would a package that does a RAISE_APPLICATION_ERROR send the
information to the alert log?  Is that the default functionality of
RAISE_APPLICATION_ERROR, if there's no STDOUT or no application to raise
the error to?
Lyall

 

 

 


Please visit our website at 
http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html 
for important disclosures and information about our e-mail 
policies. For your protection, please do not transmit orders 
or instructions by e-mail or include account numbers, Social 
Security numbers, credit card numbers, passwords, or other 
personal information.

Other related posts: