< 518:ORA-00308: cannot open archived log '/arch_log1/CDWQ/CDWQ_1_907600_574942170.dbf'
< 519:ORA-27041: unable to open file
Oracle Alert Log Is Reporting Archive Log Status Is Not Available For Logs That Have Long Been Backed Up [ID 1161573.1]
Prior to 11g certain errors that would not normally be reported such as "ORA-8103: object no longer exists" would result in redo from the all the online redo logs being scanned. From 11.1 onwards Oracle now potentially scans the past 12 hours of redo, and that can mean looking at archived logs too.
The fact that in 11.1 the diagnostic redo scans/dumps potentially search for the past 12 hours of redo and if the redo dump tries to access an archived log that has been deleted then ORA-27037 and ORA-308 are raised, and caught and handled internally, but in the alert log, this is effectively publicizing the internally handled exception conditions, and could be confusing to the DBA viewing the alert log.
* 11.1.0.7.3 (Patch Set Update)
* 11.2.0.1 (Base Release)
A workaround would be to not remove archive logs from the system unless they are older than 12 hours.
< 519:ORA-27041: unable to open file
Oracle Alert Log Is Reporting Archive Log Status Is Not Available For Logs That Have Long Been Backed Up [ID 1161573.1]
Cause
Per unpublished bug 9207154: GET ORA-00308 ORA-27037 ATTEMPTING TO ACCESS VERY OLD ARCHIVE LOG.Prior to 11g certain errors that would not normally be reported such as "ORA-8103: object no longer exists" would result in redo from the all the online redo logs being scanned. From 11.1 onwards Oracle now potentially scans the past 12 hours of redo, and that can mean looking at archived logs too.
The fact that in 11.1 the diagnostic redo scans/dumps potentially search for the past 12 hours of redo and if the redo dump tries to access an archived log that has been deleted then ORA-27037 and ORA-308 are raised, and caught and handled internally, but in the alert log, this is effectively publicizing the internally handled exception conditions, and could be confusing to the DBA viewing the alert log.
Solution
This process was changed via patch for Bug 8825048: 11.1 - DUMPING DIAGNOSTIC INFO FOR ORA-8103 RESULTS IN ORA-308 which is fixed in:* 11.1.0.7.3 (Patch Set Update)
* 11.2.0.1 (Base Release)
A workaround would be to not remove archive logs from the system unless they are older than 12 hours.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/11976525/viewspace-703583/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/11976525/viewspace-703583/