Re: init.ora parameter to log errors to the alert log
- From: "Dennis Williams" <oracledba.williams@xxxxxxxxx>
- To: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
- Date: Wed, 30 Apr 2008 14:04:40 -0500
Thanks everyone, that enabled me to trap the pesky SQL statement.
Interestingly, the session received an ORA-03113 error, but fortunately the
statement was written to the alert log.
Dennis
On 4/30/08, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxx> wrote:
>
> Also, I think Brandon answered your question, but on a related note,
> dbms_system.ksdwrt can be used to write to the alert log or trace file,
> explicitly. It, along with some other alert log writing functionality, is
> documented here:
>
> http://www.psoug.org/reference/dbms_system.html
>
>
>
> -Mark
>
>
>
> *--
> Mark J. Bobak*
> *Senior Database Administrator, System & Product Technologies*
> ProQuest
> 789 E. Eisenhower, Parkway, P.O. Box 1346
> Ann Arbor MI 48106-1346
> +1.734.997.4059 or +1.800.521.0600 x 4059
> mark.bobak@xxxxxxxxxxxx <mark.bobak@xxxxxxxxxxxxxxx>
> www.proquest.com
> www.csa.com
>
> *ProQuest...*Start here.
>
>
>
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Dennis Williams
> *Sent:* Wednesday, April 30, 2008 12:45 PM
> *To:* oracle-l@xxxxxxxxxxxxx
> *Subject:* init.ora parameter to log errors to the alert log
>
>
>
> List,
>
>
>
> Years ago I found a tip, you could add an entry in the init.ora file for a
> specific Oracle error that wouldn't normally get logged. Then when a user
> session encountered that error, the error would get logged in the alert log.
> Does anyone recall that?
>
>
>
> Thanks,
>
> Dennis Williams
>
Other related posts:
