Re: Stragne Recovery problem
- From: Hemant K Chitale <hkchital@xxxxxxxxxxxxxx>
- To: oramail@xxxxxxxxxxxxxxxx, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 17 Jul 2006 21:35:18 +0800
I would think that the controlfile that the STARTUP MOUNT and RECOVER
commands are reading is _*not*_ the "current" (ie this, now, point-in-time)
file.
eg when you said you restored the controlfile and online logs and
the recovery applied only archive 8555, that would mean that the controlfile
that you "restored" is as of the 8555 point in time.
Possibilities :
a. Your restoration command is not restoring the files that you think
it is restoring.
b. Your backup command is not backing-up the files that you think
it is backing-up.
c. The init.ora of the database instance is referencing a _different_
controlfile,
already present on disk, other than the one you are restoring.
To verify you could just do a STARTUP MOUNT and __before__ attempting
a RECOVER, query the controlfiles -- eg query V$LOG and see what the
controlfile thinks is the current Log Sequence Number.
Hemant
At 09:17 PM Monday, Rich Holland [oramail] wrote:
<snip>
We then logged on to the new system, did a 'startup mount' and a 'recover
database' and the system recovered from the first archive log and then said
media recovery was complete - it skipped the other 40-50 logs we'd copied
over. We're able to open the database (it's marked consistent), but it
didn't roll through the last 2 weeks worth of archived redo, so I know it
can't be right (we have logs 8555 - 8598 to play back, and it only used
8555).
--
//www.freelists.org/webpage/oracle-l
Hemant K Chitale
http://web.singnet.com.sg/~hkchital
--
//www.freelists.org/webpage/oracle-l
Other related posts:
