tag:blogger.com,1999:blog-51024412008-07-23T16:38:32.477-03:00Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-5102441.post-8997706436839581202007-10-19T16:27:00.000-03:002007-10-19T16:29:29.198-03:00

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.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-45174891502521340672007-10-17T18:32:00.000-03:002007-10-17T18:36:19.955-03:00

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.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1154732283057285992006-08-04T19:48:00.000-03:002006-11-10T19:19:26.916-03:00

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/

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1111524240603237302005-03-22T17:41:00.000-03:002006-11-10T19:19:26.849-03:00

Only one annoying fix: The script now detects "caused by" and "signalled by" errors and alert them accordingly.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108758396223883702005-02-18T17:23:00.000-03:002006-11-10T19:19:26.767-03:00

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.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108397527542247222005-02-14T13:08:00.000-03:002006-11-10T19:19:26.477-03:00

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.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108398646574398032005-02-13T13:29:00.000-03:002007-10-17T18:37:57.048-03:00

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

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108398499582826292005-02-13T13:18:00.000-03:002006-11-10T19:19:26.545-03:00

This is the list of features that currently OraAlertCheck supports: Parse "^ORA-NNNNN" errors and send emails depending on the severity of the error (this will be enhanced as other DBAs contribute with more and more errors). If the errors are on the errors list the alert will provide more information (example: if potential bug then sends a reference to the proper metalink notes). Errors

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108246176018379352005-02-12T18:58:00.000-03:002007-10-19T16:18:43.479-03:00

Download the latest release and uncompress on your unix oracle account home directory. Put all the files in the same directory (/home/oracle/OraAlertCheck for example). Rename OraAlertCheck_config.sh.sample to OraAlertCheck_config.sh. Edit the file and change the variables to suit your needs. It's important to set the WORKDIR to where the scripts are located. OraAlertCheck look for your

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108245251582670662005-02-12T18:52:00.000-03:002006-11-10T19:19:26.327-03:00

I've choose korn shell becouse it's considered the "standard" shell of Unix, and it's available by default on most *nix systems, so no extra things needs to be installed on your server.

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-1108157766987348802005-02-11T18:35:00.000-03:002006-11-10T19:19:26.268-03:00

Well, today I decide to get these scripts out. There are three files, you should only edit the config file and rename it. Put it in /etc or /home/user/etc. The other two can go anywhere, but be sure to complete the right parameters in the config file. You can use it from the crontab by calling the main script. You can add a "test" parameter in the call to see which instances it has detected and

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-897330272003-02-25T18:13:00.000-03:002006-11-10T19:19:25.991-03:00

Well, today I've started blogs. This is just a trial, perhaps later I'll do it non-anonymously (if that is how it is said ;) ).

Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.com