Thanks, Dimitre. I did apply logs well past the end of the backup, but I will try again and apply all of the logs currently available from the source database.
Paul Baumgartel CREDIT SUISSE Information Technology DBA & Admin - NY, KIGA 1 11 Madison Avenue New York, NY 10010 USA Phone 212.538.1143 paul.baumgartel@(protected) www.credit-suisse.com
-- --Original Message-- -- From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]On Behalf Of Radoulov, Dimitre Sent: Thursday, June 01, 2006 4:46 PM To: paul.baumgartel@(protected) Cc: oracle-l@(protected) Subject: Re: Open read only after incomplete recovery?
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
============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<STYLE></STYLE>
<META content="MSHTML 6.00.2800.1529" name=GENERATOR></HEAD> <BODY bgColor=#ffffff background=""> <DIV><SPAN class=546505720-01062006><FONT face=Arial color=#0000ff size=2>Thanks, Dimitre. I did apply logs well past the end of the backup, but I will try again and apply all of the logs currently available from the source database.</FONT></SPAN></DIV> <DIV> </DIV> <P><B><FONT face=Arial size=2>Paul Baumgartel</FONT></B> <BR><B><FONT face =Arial size=2>CREDIT SUISSE</FONT></B> <BR><FONT face=Arial size=2>Information Technology</FONT> <BR><FONT face=Arial size=2>DBA & Admin - NY, KIGA 1</FONT> <BR><FONT face=Arial size=2>11 Madison Avenue</FONT> <BR><FONT face=Arial size=2>New York, NY 10010</FONT> <BR><FONT face=Arial size=2>USA</FONT> <BR><FONT face=Arial size=2>Phone 212.538.1143</FONT> <BR><FONT face=Arial size=2>paul.baumgartel@(protected)</FONT> <BR><FONT face=Arial size=2>www.credit-suisse.com</FONT> </P> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-- --Original Message-- --<BR><B>From:</B> oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]<B>On Behalf Of </B>Radoulov, Dimitre<BR><B>Sent:</B> Thursday, June 01, 2006 4:46 PM<BR><B>To:</B> paul.baumgartel@(protected)<BR><B>Cc:</B> oracle-l@(protected)<BR><B>Subject:</B> Re: Open read only after incomplete recovery?<BR><BR></FONT></DIV> <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></BLOCKQUOTE> <P><pre wrap>================================================================== ============ Please access the attached hyperlink for an important electronic communications disclaimer:
