Yeah, I log those.  Some of the db's I support run with very small redo logs
and I can't change.  They get those quite frequently at times so I pretty
much ignore them.  My script also reacts (log,email,page, or run some
script) in the event of startups, shutdowns and alter database structure.
It also sends everything through a filter of "known" patterns and anything
that is not recognized falls out.  I call this the paranoid switch "-p".
One best practice I recommend is to automate control file backups anytime a
ALTER TABLESPACE, ALTER DATABASE etc...is in the alert log. 

-----Original Message-----
Sent: Wednesday, August 27, 2003 4:55 PM
To: Multiple recipients of list ORACLE-L


Hi!

I would add a check for "Checkpoint not complete" in alert just in case as
well.

Tanel.

> One enhancement I suggest to every script is to configure the a
SERVERERROR
> trigger to throw certain errors out to the alert log.  ORA-1555 is one
that
> will show up at the session level but not at the database level.  Out of
> TEMP space is another that is frequent at the session level but not the
> database level.  This way you know who is causing some important errors.
> Overtime I find more and more session errors that are really critical
> database errors.  Try DDL on a table with an unusable index.  Pretty big
> deal on most production databases but this is a session error and would
not
> typically show up in the alert log.  The risk of course is some huge loop
> throwing 1000's of lines into the alert log.  I would suggest a governor
of
> some sort in your servererror trigger.
>
> - Ethan
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Post, Ethan
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to