Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> re-build physical standby in DG setup

re-build physical standby in DG setup

From: EdStevens <quetico_man_at_yahoo.com>
Date: 20 Jul 2006 09:37:14 -0700
Message-ID: <1153413434.201662.274870@s13g2000cwa.googlegroups.com>


Subject: re-build physical standby in DG setup

Platform: Oracle 10.2.0.1.0 on Solaris 10

DataGuard configuration with a physical standby database. Through an unfortunate set of circumstances, a couple of archivelog files didn't get shipped, then got deleted from the primary site. (yes, I'm the guilty party) (And when I asked the server admin guys if they could restore the archivelog files from a server level backup, they discovered that *their* backup procedure had been failing!)

As I understand, that leaves the standby unable to complete it's recovery, so I need to rebuild it almost from scratch. I say 'almost' because, as I read the chapter on creating a physical standby in the DataGuard Concepts and Admin manual, it appears that several of the steps that were done on the initial setup are still good and can be bypassed for this exercise. Here's how I see this shaking out. Please tell me if I'm getting ready to dig the hole even deeper, if there's an easier way out, or if I'm on the right track but need to consider a few more items.

Following the setup steps in the doc, I should be able to bypass everything dealing with creating the primary database. It was/is up, and the only thing I've done is stop archive shipping, to prevent filling up the recovery area target on the standby.

On the standby, comments on each step:

3.2.1 - Create Backup Copy of the Primary Database datafiles.
(yes, use rman to backup datafiles. This will need to be a hot backup.
 Just the files listed in DBA_DATA_FILES? Include the SYSTEM tablespace?)

3.2.2 - Create Control file for standby
(it says "if the backup procedure required a shutdown of the primary
....". I would think I could skip this and go with the existing control file of the standby, but am unsure of its record of archive sequences)

3.2.3 - Prepare initialization parameter file for the standby
(again, I should be able to go with the spfile that is already in
place)

3.2.4 - copy files from the primary to the standby
(yes to the backup data files, but no to the control file and parm
file)

3.2.5 - Set up the environment to support the standby database
(already there)

3.2.6 - start the physical standby

(extra item: restart log shipping on the primary)

3.2.7 - verify physical standby is performing properly
(run log switches, examine results --- yes)

If this is essentially correct, I would also think I can simply delete a bunch of now obsolete archivelogs, followed by rman crosscheck and delete obsolete on the primary. What of archivelog cleanup on the standby, where the db is not open?

Anything I'm overlooking or failed to consider? Received on Thu Jul 20 2006 - 11:37:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US