Development list has been created

Since blog comments are not a suitable way of giving support I've created a new Mailing List for Development and Support. The current mailing list will only have Announcements like new versions of the script or important messages.

Regards,
Jose.

OraAlertCheck 0.1.5 released

Thanks Fayyaz for the feedback!

OraAlertCheck now is fully functional in AIX (tested on 5.3).

New features:

• Corrections on the way the script treats filenames. When the oracle error was ORA-00600 and had special characters on the arguments the script created temporary files with spaces or : characters which made the script failed.
  

Regards,
Jose.

OraAlertCheck is back! Version 0.1.4

Thanks to Raghu Maddula for the feedback!


OraAlertCheck now is functional in HPUX and Solaris.

New features:

• oratab file location can be specified in the Config file (in case you don't have root access to modify /etc or you SA is too slow ;) )
• The tail command needs to support the -n flag. In Solaris the default one did not, so I add a new config parameter to specify a new location (/usr/xpg4/bin/tail for Solaris).
• The "test" run of the script will not only show if it find the alert.log but also will let you now if that instance won't be checked becouse the startup parameter in oratab is "N".
• Finally we add the "encountered when generating server alert" message detection (althought I'm not sure if we should print the first ORA- or the server alert error...).

Have fun!

Jose.

Version 0.1.3

Only one annoying fix:

• The script now detects "caused by" and "signalled by" errors and alert them accordingly.

Version 0.1.2 is out

Only minor changes.

• GNU GPL License text added to the files
• Simpler config file lookup (just leave on the same directory as the run file)
• Run it from any directory
• Show the line error in the alert mails, not only the error code.

OraAlertCheck 0.1.1 is out

A couple of changes, I've add an automatic alert.log truncation: the script moves the file and then compress it in the same bdump directory. Just add TRUNCATE_BYTES="nnn" in the config file to enable, "0" to disable.

Also now the script send different alerts to reflect different ORA-00600 parameters instead of sending only one mail.

ChangeLog

0.1.5

• OraAlertCheck is fully functional in AIX (thanks Fayyaz, tested on 5.3).
• Corrections on the way the script treats filenames. When the oracle error was ORA-00600 and had special characters on the arguments the script created temporary files with spaces or : characters which made the script failed.

0.1.4

• OraAlertCheck is fully functional in HPUX and Solaris (thanks Raghu Maddula).
• oratab file location can now be specified in the Config file.
• The tail command needs to support the -n flag. In Solaris the default one did not, so a new config parameter exists to specify a new location (/usr/xpg4/bin/tail for Solaris).
• The "test" run of the script will not only show if it find the alert.log but also will let you now if that instance won't be checked becouse the startup parameter in oratab is "N".
• Support for detection of the "encountered when generating server alert" message was added.

0.1.3

• Detects "caused by" and "signalled by" errors and alert them accordingly.
  

0.1.2

• GNU GPL License text added to the files
• Simpler config file lookup (just leave on the same directory as the run file)
• Run it from any directory
• Show the line error in the alert mails, not only the error code.

0.1.1

• Automatic alert.log truncation
• Send different emails if ORA-00600 arguments are differents.
  

0.1

• Initial release.