OraAlertCheck is a (I hope) simple korn script that checks your Oracle databases alert log files and inform you when it detect problems (ORA-NNNNN errors).
Saturday, February 12, 2005
Why Korn shell??
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.
I have run the utility on AIX 5.3 with Oracle 10g (10.2.0.3). there are 4 databases running on this machine. I got below messages on my terminal. Where i can check to solve these problems? [ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh
Usage: oerr facility error
Facility is identified by the prefix string in the error message. For example, if you get ORA-7300, "ora" is the facility and "7300" is the error. So you should type "oerr ora 7300".
If you get LCD-111, type "oerr lcd 111", and so on. cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:. No recipient addresses found in header cat: 0652-050 Cannot open pfri8:. No recipient addresses found in header cat: 0652-050 Cannot open plio. No recipient addresses found in header cat: 0652-050 Cannot open mismatch. No recipient addresses found in header cat: Not a recognized flag: . Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...] No recipient addresses found in header rm: Not a recognized flag: . Usage: rm [-firRe] [--] File... cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:. No recipient addresses found in header cat: 0652-050 Cannot open pfri8:. No recipient addresses found in header cat: 0652-050 Cannot open plio. No recipient addresses found in header cat: 0652-050 Cannot open mismatch. No recipient addresses found in header cat: Not a recognized flag: . Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...] No recipient addresses found in header rm: Not a recognized flag: . Usage: rm [-firRe] [--] File... cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:. No recipient addresses found in header cat: 0652-050 Cannot open pfri8:. No recipient addresses found in header cat: 0652-050 Cannot open plio. No recipient addresses found in header cat: 0652-050 Cannot open mismatch. No recipient addresses found in header cat: Not a recognized flag: . Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...] No recipient addresses found in header rm: Not a recognized flag: . Usage: rm [-firRe] [--] File...
Fayyaz, thanks for trying this script. I've just run it in a 42Mb alert log file in AIX 5.3 without any errors. I had to change the tail command in the config file to use the default one (since AIX 5.3 tail has the -n option). Maybe the error is from this particular line (ORA-00600-pfri). Can you please do a grep in your alter.log file searching for the word "pfri" and paste me a line so I can test it in my box? Maybe some part of the script is not filtering that line as it should. Thanks, Jose.
Fayyaz, I've released a new version (0.1.5). It corrects a problem when finding special characters on the ora-600 arguments. Please try it out and let me know. What do you mean about an english version? I had on message on spanish, I just replaced it, do you see any other? Regards, Jose
Please remove line 143 of OraAlertCheck.sh (LOG_FILE="alert.log"). I leave it there by mistake after testing with your alert.log line. I'll be uploading the file again, thanks for checking! Jose.
Thanks but now i am unable to locate my alert log file and getting below messages [ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh test Detected cmaq but alertlog file NOT FOUND: /alert_cmaq.log Detected cmar but alertlog file NOT FOUND: /alert_cmar.log Detected cmat but alertlog file NOT FOUND: /alert_cmat.log Detected cmad but alertlog file NOT FOUND: /alert_cmad.log (citrine10g) [ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh Error: file not found /alert_cmaq.log
is it due to /var/oratab?
oratab has below entries and it has changed yesterday. I have to check with other DBAs for changes.
Yes, the script will go for each line of the oratab to find the instances. It will export the ORACLE_HOME and connect with sqlplus as internal (conn / as sysdba) to get the background_dump_dest directory (you can try it yourself by connecting to sqlplus and running "show parameter background_dump_dest). The value of the parameter is saved and the script will then try to get the alert_SID.log file in that directory. If the oratab information is not correct, consider creating a custom oratab in other directory and modify the config file to point to it. Regards, Jose.
But according to my collegues DBAs the entries in oratab are correct. The oratab has been changed for RMAN implementation. I think you have to consider this point of oratab. Also, i have tried the utility on another AIX machine where oratab is correct but auto start of db after machine reboot is set to "N". due to this the utility is failing, why? it should not. Because, it may only check the instance name from oratab
Fayyaz, did you read my last message? You can use a custom oratab file if your oratab has "N". Or you can modify the script to avoid that check, it's not so hard. I've already told you how the script finds out where the alert log file is. Find out the value of the background_dump_dest database parameter and see if it as something wrong in it. This is a custom script I've made and that I'm sharing, you can always modify it to suit your needs, but the basic behaviour is not going to change. Regards, Jose.
12 comments:
I have run the utility on AIX 5.3 with Oracle 10g (10.2.0.3). there are 4 databases running on this machine.
I got below messages on my terminal. Where i can check to solve these problems?
[ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh
Usage: oerr facility error
Facility is identified by the prefix string in the error message.
For example, if you get ORA-7300, "ora" is the facility and "7300"
is the error. So you should type "oerr ora 7300".
If you get LCD-111, type "oerr lcd 111", and so on.
cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:.
No recipient addresses found in header
cat: 0652-050 Cannot open pfri8:.
No recipient addresses found in header
cat: 0652-050 Cannot open plio.
No recipient addresses found in header
cat: 0652-050 Cannot open mismatch.
No recipient addresses found in header
cat: Not a recognized flag: .
Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...]
No recipient addresses found in header
rm: Not a recognized flag: .
Usage: rm [-firRe] [--] File...
cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:.
No recipient addresses found in header
cat: 0652-050 Cannot open pfri8:.
No recipient addresses found in header
cat: 0652-050 Cannot open plio.
No recipient addresses found in header
cat: 0652-050 Cannot open mismatch.
No recipient addresses found in header
cat: Not a recognized flag: .
Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...]
No recipient addresses found in header
rm: Not a recognized flag: .
Usage: rm [-firRe] [--] File...
cat: 0652-050 Cannot open /home/ora10g/OraAlertCheck/.tmp.ORA-00600-pfri.c:.
No recipient addresses found in header
cat: 0652-050 Cannot open pfri8:.
No recipient addresses found in header
cat: 0652-050 Cannot open plio.
No recipient addresses found in header
cat: 0652-050 Cannot open mismatch.
No recipient addresses found in header
cat: Not a recognized flag: .
Usage: cat [-qrSsu] [-n[b]] [-v[et]] [-|File ...]
No recipient addresses found in header
rm: Not a recognized flag: .
Usage: rm [-firRe] [--] File...
Fayyaz, thanks for trying this script. I've just run it in a 42Mb alert log file in AIX 5.3 without any errors. I had to change the tail command in the config file to use the default one (since AIX 5.3 tail has the -n option).
Maybe the error is from this particular line (ORA-00600-pfri). Can you please do a grep in your alter.log file searching for the word "pfri" and paste me a line so I can test it in my box? Maybe some part of the script is not filtering that line as it should.
Thanks,
Jose.
Here is the output of grep command
[ora10g] /laraQctl/bkgrd > grep -i "pfri" alert_cmaq.log
ORA-00600: internal error code, arguments: [pfri.c: pfri8: plio mismatch ], [], [], [], [], [], [], []
Please advise accordingly. Is it possible to send the English version of this utility?
Fayyaz, I've released a new version (0.1.5). It corrects a problem when finding special characters on the ora-600 arguments. Please try it out and let me know.
What do you mean about an english version? I had on message on spanish, I just replaced it, do you see any other?
Regards,
Jose
After replacing the older files with new one (0.1.5) I am getting below message on terminal
[ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh
Error: file not found alert.log
Thanks to advice accordingly.
Please remove line 143 of OraAlertCheck.sh (LOG_FILE="alert.log").
I leave it there by mistake after testing with your alert.log line. I'll be uploading the file again, thanks for checking!
Jose.
Thanks but now i am unable to locate my alert log file and getting below messages
[ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh test
Detected cmaq but alertlog file NOT FOUND: /alert_cmaq.log
Detected cmar but alertlog file NOT FOUND: /alert_cmar.log
Detected cmat but alertlog file NOT FOUND: /alert_cmat.log
Detected cmad but alertlog file NOT FOUND: /alert_cmad.log
(citrine10g) [ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh
Error: file not found /alert_cmaq.log
is it due to /var/oratab?
oratab has below entries and it has changed yesterday. I have to check with other DBAs for changes.
cmaq:/oracle/product/10.2.0:Y:ora10g:1
cmar:/oracle/product/10.2.0:Y:ora10g:1
cmat:/oracle/product/10.2.0:Y:ora10g:1
cmad:/oracle/product/10.2.0:Y:ora10g:1
Thanks for comments
Yes, the script will go for each line of the oratab to find the instances. It will export the ORACLE_HOME and connect with sqlplus as internal (conn / as sysdba) to get the background_dump_dest directory (you can try it yourself by connecting to sqlplus and running "show parameter background_dump_dest). The value of the parameter is saved and the script will then try to get the alert_SID.log file in that directory.
If the oratab information is not correct, consider creating a custom oratab in other directory and modify the config file to point to it.
Regards,
Jose.
But according to my collegues DBAs the entries in oratab are correct. The oratab has been changed for RMAN implementation. I think you have to consider this point of oratab. Also, i have tried the utility on another AIX machine where oratab is correct but auto start of db after machine reboot is set to "N". due to this the utility is failing, why? it should not. Because, it may only check the instance name from oratab
thanks for revert
Fayyaz, did you read my last message? You can use a custom oratab file if your oratab has "N". Or you can modify the script to avoid that check, it's not so hard.
I've already told you how the script finds out where the alert log file is. Find out the value of the background_dump_dest database parameter and see if it as something wrong in it. This is a custom script I've made and that I'm sharing, you can always modify it to suit your needs, but the basic behaviour is not going to change. Regards, Jose.
Thanks for support
No problem, please use the new Dev and Support Mailing List if you have more isuues.
Regards,
Jose.
Post a Comment