Re: Stragne Recovery problem
- From: Riyaj Shamsudeen <rshamsud@xxxxxxxxxxxx>
- To: oramail@xxxxxxxxxxxxxxxx
- Date: Mon, 17 Jul 2006 08:31:36 -0500
In other words, the first time we tried it we restored a test
system, opened it to verify it was good, stopped it, copied the "current"
control files, archived redo, and online redo, then did startup mount &
recover database, and it SKIPPED everything.
As soon as you open the database in read write mode, source and target database have parted, whether you have any activity or not is immaterial.. After that point in time, archivelog files generated in source database are not applicable in target database.
So, if you would like to do some verification before the recovery, open the
database in read only mode.
Rich Holland [oramail] wrote:
<.. lines snipped ..>
We've done this several times with test systems and it seemed to work as
long as we didn't open the database on the target host before we did the
recovery. In other words, the first time we tried it we restored a test
system, opened it to verify it was good, stopped it, copied the "current"
control files, archived redo, and online redo, then did startup mount &
recover database, and it SKIPPED everything. We re-restored it from tape
and this time didn't open it, but just did the startup mount & recover
database, and it recovered through all the archived redo correctly.
What effect does opening the database have that would cause it to skip all
that redo?
<.. lines snipped ..>
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If the reader of this message is not the intended recipient,
you are hereby notified that your access is unauthorized, and any review,
dissemination, distribution or copying of this message including any
attachments is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete the material from any
computer.
Other related posts:
