| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: re-build physical standby in DG setup
EdStevens wrote:
> 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?)
everything, including controlfiles. as i regularly rebuild physical standby databases i use the following rman script:
backup as compressed backupset
check logical
full database
include current controlfile for standby;
> 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)
can be skipped if controlfile was already backed up in 3.2.1
> 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)
yes, the existing spfile should be fine. if using OMF/ASM there could be a little problem with the controlfilenames that can easily be solved by renaming the controlfiles in the spfile.
> 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)
copy all backupsets created in 3.2.1 (including the controlfile). i personally use rmans 'duplicate' for creating the standby, very comfortable.
> 3.2.6 - start the physical standby
> -- startup mount
> -- alter database recover managed standby database disconnect from
> session;
> (yes)
did you consider to use dgmgrl for managing dataguard? i recommend it.
> 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?
i would first catalog everything recovery related on the standby, then crosscheck and delete all expired stuff. db in mount state is ok, no open db needed.
you should consider making multiple backups of archived redologs. i for myself back up all archivelogs on a daily basis and delete only logs sucessfully backed up 3 times:
delete archivelog all backed up 3 times to device type sbt;
regards,
-ap
Received on Thu Jul 20 2006 - 16:01:13 CDT
![]() |
![]() |