Re: DataGuard Standby Database usage
From: daniel koehne <koehned_at_gmail.com>
Date: Fri, 30 May 2008 13:38:17 -0400
Message-ID: <22d95d970805301038g5e686abdp5db7c36769ca3044@mail.gmail.com>
Date: Fri, 30 May 2008 13:38:17 -0400
Message-ID: <22d95d970805301038g5e686abdp5db7c36769ca3044@mail.gmail.com>
I am not sure if Oracle support would support this, but after
activating our 10gR2 EE (10.2.0.3) databases for disaster recovery
testing we use the flashback database feature to restore the databases
to being a physical standby database.
Here is a brief overview of our steps:
- Make sure flashback is enabled and that your flashback area has enough space.
- create a flashback restore point. May want to look into a guaranteed restore point.
- activate 10gR2 EE database for testing.
- flashback database to restore point.
- ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
- database flashback uses archive logs. We use home grown data guard scripts to we need to use RMAN to catalog the archive logs before the db activate (i.e. rman with no catalog, then use catalog command). If not done flashback database command will complain about being unable to find the required archive log files. This is more of a problem with our large high-activity database.
- After flashback and convert to physical standby, the "recover standby database" command still looks for some archive log files from the time the db was activated. We just create a new standby control file using the primary db and this issue goes away.
I hope someone finds this useful.
Daniel
-- http://www.freelists.org/webpage/oracle-lReceived on Fri May 30 2008 - 12:38:17 CDT