Cause In order for the database to open after recovery, the datafiles must be consistent. If incomplete recovery is performed, the recovery must be (at least) enough to make the files consistent. With online backups, because the files are changing as the backup occurs, recovery must apply all archives generated between the beginning through the end of the backup.
The main error is the ORA-01152 (See ORA-01152.ora-code.com). This occurs because one file is ahead of the others at the requested recovery stop time.
Fix To implement the solution, please execute the following steps:
1. Reexecute script using a longer recovery with the 'set until' clause.
If using 'SET UNTIL LOGSEQ' consider the definition of 'set until logseq' from Oracle9i Recovery Manager Reference, untilclause:
"Specifies a redo log sequence number and thread as an upper limit. RMAN selects only files that can be used to recover up to but not including the specified sequence number. For example, REPORT OBSOLETE UNTIL SEQUENCE 8000 THREAD 1 reports only backups that could be used to recover through log sequence 7999."
In short, be sure the LOGSEQ specified is one greater than the last one created after the database backup completes.
Regards Dimitre <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.5346.5" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff background=""> <DIV><FONT face=Arial size=2>> Specify log: {<RET>=suggested | filename | AUTO | CANCEL}<BR>> cancel<BR>> ORA-01547 (See ORA-01547.ora-code.com): warning: RECOVER succeeded but OPEN RESETLOGS would get error below<BR>> ORA-01194 (See ORA-01194.ora-code.com): file 1 needs more recovery to be consistent<BR>> ORA-01110 (See ORA-01110.ora-code.com): data file 1: '/data/oracle/PNYTP102/u01/system_01.dbf'<BR><BR><BR>MetaLink Note:290985.1 Incomplete RMAN Recovery gives error ORA-01547 (See ORA-01547.ora-code.com)</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><BR><BR><FONT face=Arial size=2>Symptoms<BR>RMAN recovery with an 'until' clause giving errors:<BR><BR>RMAN-11001: Oracle Error: ORA-01547 (See ORA-01547.ora-code.com): warning: RECOVER succeeded but OPEN<BR>RESETLOGS would get error below<BR>ORA-01152 (See ORA-01152.ora-code.com): file ... was not restored from a sufficiently old backup<BR>ORA-01110 (See ORA-01110.ora-code.com): data file ............<BR><BR><BR>Cause<BR>In order for the database to open after recovery, the datafiles must be consistent. If incomplete<BR>recovery is performed, the recovery must be (at least) enough to make the files consistent. With<BR>online backups, because the files are changing as the backup occurs, recovery must apply all archives generated between the beginning through the end of the backup.<BR><BR>The main error is the ORA-01152 (See ORA-01152.ora-code.com). This occurs because one file is ahead of the others at the requested recovery stop time.<BR><BR><BR>Fix<BR>To implement the solution, please execute the following steps:<BR><BR>1. Reexecute script using a longer recovery with the 'set until' clause.<BR><BR>If using 'SET UNTIL LOGSEQ' consider the definition of 'set until logseq' from Oracle9i Recovery Manager Reference, untilclause:<BR><BR> "Specifies a redo log sequence number and thread as an upper limit. RMAN selects only files that can be used to recover up to but not including the specified sequence number. For example, REPORT OBSOLETE UNTIL SEQUENCE 8000 THREAD 1 reports only backups that could be used to recover through log sequence 7999."<BR><BR><U><STRONG><FONT color=#0000ff>In short, be sure the LOGSEQ specified is one greater than the last one created after the database backup completes.</FONT></STRONG></U> </FONT></DIV> <DIV><STRONG><U><FONT face=Arial color=#0000ff size=2></FONT></U></STRONG> </DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Regards</FONT></DIV> <DIV><FONT face=Arial size=2>Dimitre</FONT></DIV></BODY></HTML>
