Re: Oracle errors not logging to alert log

The Administrator's Guide has a good description of what results in a message being written to the alert.log:

http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/ser ver.817/a76956/manproc.htm#1778

> All internal errors (ORA-600), block corruption errors (ORA-1578),
> and deadlock errors (ORA-60) that occur
>
> Administrative operations, such as CREATE/ALTER/DROP
> DATABASE/TABLESPACE/ROLLBACK SEGMENT SQL statements and STARTUP,
> SHUTDOWN, and ARCHIVE LOG
>
> Several messages and errors relating to the functions of shared
> server and dispatcher processes
>
> Errors occurring during the automatic refresh of a snapshot
>
> The values of all initialization parameters at the time the database
> and instance start

--
Jeremiah



> Ed Stevens <ed.stevens_at_home.com> wrote:

> >

> >Why would an Oracle error reported by an application not show up in

> >the alert log?


zatherus69_at_hotmail.com wrote:


> Not all errors will log themselves in the alert log.  Can you imagine

> how large it would get every time someone mistyped their password or

> misspelled a column name?  The alert log is specifically for problems

> that could potentially be critical to the health or usability of the

> database.  Running out of extents in a tablespace or table for

> example.  Or the infamous ORA-00600.

>

> The error you mention above was mearly the program trying to delete a

> row reference by a foriegn key.   Right off hand I can't think of a

> DML that would cause an alert log entry unless something more serious

> was wrong.  Like running out of room.



Sent via Deja.com
http://www.deja.com/