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 errors are raised, and caught and handled internally, but in the alert log, this...
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 errors are raised, and caught and handled internally, but in the alert log, this...
Extract abends with: ERROR OGG-00446 Oracle GoldenGate Capture for Oracle, ej1.prm: Opening ASM file +ASM/2_11055_742755632.dbf in DBLOGREADER mode: (308) ORA-00308: cannot open archived log '+RECO/2_11055_742755632.dbf' ORA-17503....
ORA-00308: cannot open archived log '/<path>/arch_1_5379.dbf' ORA-27037: unable to obtain file status SVR4 Error: 2: No such file or directory Additional information: 3 ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery ...
alter database open resetlogs * ERROR at line 1: ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: 'D:\APP\ADMINISTRATOR\ORADATA\orcl\SYSTEM01.DBF' SQL> RECOVER DATABASE USING BACKUP CONTROLFILE; ...
ORA-00308: cannot open archived log '/oracle/CMP/oraarch/CMParch1_77453_511022248.dbf' ORA-27037: unable to obtain file status There was a structure validation check running (analyze table validate structure) during the time when those errors appeared. The file mentioned in the error message...