Re: Physical Standby Issue
- From: "Sreejith Nair" <sreejithsna@xxxxxxxxx>
- To: bill@xxxxxxxxxxxx
- Date: Sun, 10 Jul 2011 07:00:03 +0530
You can use 'set until' clause in the restore command in standby to restore and
rcover the database to archive log sequence number just before the corrupted
log sequence number.
Best Regards,
Sreejith
~ Sent from my Samsung Smartphone.
------- Original message -------
From: <bill@xxxxxxxxxxxx>
To: oracle-l@xxxxxxxxxxxxx
Sent: 5/7/'11, 22:57
Oracle 9.2.0.8.0
Have a physical standby database on an alternate server/location which received a corrupt log file from the primary. Attempted to copy the
logfile from the primary, but original file must be corrupt. Oracle support has not been any help and unable to escalate the issue at
this time. We figure the best solution is to restore the database from a recent backup and recreate the physical standby. When
this was done and the database recovery was initiated again, the standby database was still looking for the corrupt logfile even though it was
created before the backup. When I query v$archived_log it shows all of the log files that need to be applied, including the
corrupt file. Is there any way to reset the primary so I can create a new physical standby? It seems to still have
information related to the old standby database. Thoughts??
Thanks,
Bill
-- //www.freelists.org/webpage/oracle-l --
//www.freelists.org/webpage/oracle-l
Other related posts:
