tag:blogger.com,1999:blog-5102441.post110824525158267066..comments2007-10-19T16:56:43.027-03:00Josehttp://www.blogger.com/profile/09578561231406657188noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-5102441.post-69509471524340456762007-10-19T16:56:00.000-03:002007-10-19T16:56:00.000-03:00

No problem, please use the new Dev and Support Mailing List if you have more isuues.Regards,Jose.

Jose Cancianihttp://www.4tm.com.ar/noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-59285390651824243742007-10-19T16:54:00.000-03:002007-10-19T16:54:00.000-03:00

Thanks for support

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-89625601958934671982007-10-19T16:01:00.000-03:002007-10-19T16:01:00.000-03:00

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,

Jose Cancianihttp://www.4tm.com.ar/noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-84983247572462614412007-10-19T15:03:00.000-03:002007-10-19T15:03:00.000-03:00

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

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-17713428327518819132007-10-19T11:44:00.000-03:002007-10-19T11:44:00.000-03:00

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

Jose Cancianihttp://www.4tm.com.arnoreply@blogger.comtag:blogger.com,1999:blog-5102441.post-67820916735156164642007-10-18T18:29:00.000-03:002007-10-18T18:29:00.000-03:00

Thanks but now i am unable to locate my alert log file and getting below messages[ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.sh testDetected cmaq but alertlog file NOT FOUND: /alert_cmaq.logDetected cmar but alertlog file NOT FOUND: /alert_cmar.logDetected cmat but alertlog file NOT FOUND: /alert_cmat.logDetected cmad but alertlog file NOT FOUND: /alert_cmad.log(citrine10g) [ora10g] /home

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-69575433003377138732007-10-18T17:48:00.000-03:002007-10-18T17:48:00.000-03:00

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.

Jose Cancianihttp://www.4tm.com.arnoreply@blogger.comtag:blogger.com,1999:blog-5102441.post-48820644696966065912007-10-18T17:44:00.000-03:002007-10-18T17:44:00.000-03:00

After replacing the older files with new one (0.1.5) I am getting below message on terminal[ora10g] /home/ora10g/OraAlertCheck > OraAlertCheck.shError: file not found alert.logThanks to advice accordingly.

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-12149004749624528632007-10-17T18:42:00.000-03:002007-10-17T18:42:00.000-03:00

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

Jose Cancianihttp://www.4tm.com.arnoreply@blogger.comtag:blogger.com,1999:blog-5102441.post-91299919653679929412007-10-17T15:26:00.000-03:002007-10-17T15:26:00.000-03:00

Here is the output of grep command[ora10g] /laraQctl/bkgrd > grep -i "pfri" alert_cmaq.logORA-00600: internal error code, arguments: [pfri.c: pfri8: plio mismatch ], [], [], [], [], [], [], []Please advise accordingly. Is it possible to send the English version of this utility?

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-20631979398545842072007-10-16T15:26:00.000-03:002007-10-16T15:26:00.000-03:00

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

Jose Cancianihttp://www.4tm.com.ar/noreply@blogger.comtag:blogger.com,1999:blog-5102441.post-71582843146338624752007-10-16T14:54:00.000-03:002007-10-16T14:54:00.000-03:00

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.shUsage: oerr facility errorFacility is identified by the prefix string in the error message.For example, if you get ORA-7300, "ora" is the facility and "7300

Fayyazhttp://www.blogger.com/profile/00293860179117885823noreply@blogger.com