| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: recovery puzzler
That is interesting. It should start with sequence 66 logically. Is it possible that some or few of the tablespaces were left in the hot backup mode on sunday/monday morning ? Please check the alert log. My guess is that, one of the tablespace was in the backup mode, say from Sunday at least, and 66 was the log sequence when the tablespace went in to the backup mode. Then, your begin backup command on Monday evening would have failed and hence the recovery is asking for 66.
BTW, Did you use the existing control file or did you use backup/new control file ?
Thanks
Riyaj "Re-yas" Shamsudeen
Certified Oracle DBA
i2 technologies www.i2.com
"Adams, Matthew (GEA, 088130)" <MATT.ADAMS_at_APPL.GE.COM>
Sent by: root_at_fatcity.com
06/08/01 03:05 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
cc:
Subject: recovery puzzler
This is puzzling me.
On monday morning, the log file switched from sequence 66 to 67.
On monday night, a hot backup was taken.
On Friday, this backup was written to an alternate machine
an attempt was made to do a point-in-time-recovery to Friday
Morning.
Why did it ask for archive file 66? I should have thought it
would start with file 67.
 |
 |