Oracle 10g Data gaurd

Question

Hi all,
I cloned my prod by using RMAN.
my Q is ..is there any diff between cloned db , Duplicate Database.
if any diff please let me know..
if i have cloned one by using that how to create standby instance.

Answer 1

Hi,
I mean that to create a standby you have a procedure and that rman copy is part of it and duplicate.
1) make a rman backup
run {
allocate channel C1 type disk;
backup database;
backup archivelog all ;
2) Create a Control File for the Standby Database on the primary:
ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/oracle/local/data/backup/crunchs_controlfile.bkp2';
3) Standby redo log is optionnal... (but adviced to do)
Exemple:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 ('+DATPRTEST1', '+FLAPRTEST1' ) size 50M ;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 12 ('+DATPRTEST1', '+FLAPRTEST1' ) size 50M ;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 13 ('+DATPRTEST1', '+FLAPRTEST1' ) size 50M ;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 14 ('+DATPRTEST1', '+FLAPRTEST1' ) size 50M ;
SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
4) modify the aprameter file in primary and standby
Exemple:
On the primary:
alter system set db_name='crunch' scope=both sid='*';
alter system set db_unique_name='crunch' scope=both sid='*';
alter system set fal_client=crunch scope=both sid='*';
alter system set fal_server=crunchs scope=both sid='*';
alter system set db_create_file_dest='?????????????' scope=both sid='*';
alter system set db_recovery_file_dest='?????????????????????' scope=both sid='*';
alter system set log_archive_config='DG_CONFIG=(crunchs,crunch)' scope=both sid='*';
alter system set log_archive_dest_1 LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crunch scope=both sid='*';
alter system set log_archive_dest_2 SERVICE=crunchs.RVPONP.FGOV.BE VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) OPTIONAL DB_UNIQUE_NAME=crunchs scope=both sid='*';
alter system set log_archive_dest_state_2 defer scope=both sid='*';
alter system set standby_archive_dest LOCATION=USE_DB_RECOVERY_FILE_DEST scope=both sid='*';
On the standby:
alter system set db_name='crunch' scope=both sid='*';
alter system set db_unique_name='crunchs' scope=both sid='*';
alter system set fal_client=crunchs scope=both sid='*';
alter system set fal_server=crunch scope=both sid='*';
alter system set db_create_file_dest='????????????' scope=both sid='*';
alter system set db_recovery_file_dest='????????????' scope=both sid='*';
alter system set log_archive_config='DG_CONFIG=(crunch,crunchs)' scope=both sid='*';
alter system set log_archive_dest_1 LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=crunchs scope=both sid='*';
alter system set log_archive_dest_2 SERVICE=crunchs.RVPONP.FGOV.BE VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) OPTIONAL DB_UNIQUE_NAME=crunch scope=both sid='*';
alter system set log_archive_dest_state_2 defer scope=both sid='*';
alter system set standby_archive_dest LOCATION=USE_DB_RECOVERY_FILE_DEST scope=both sid='*';
5) We copy the password file of the primary and rename it for the standby:
/oracle/product/10.2.0/db/dbs
Start standby database unmounted
sqlplus sys as sysdba
startup nomount pfile='oracle/product/10.0.2/db/dbs/initcrunchs.ora' ;
(ou startup nomount; si le spfile existe déja d'avant)...
Recover standby database from RMAN backup
. oraenv
crunchs
rman nocatalog
connect target sys/????@crunch
connect auxiliary sys/????
duplicate target database for standby;
Create a server parameter file for the standby database
sqlplus sys as sysdba
create spfile from pfile;
shutdown immediate;
startup mount;
On standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
On primary:
alter system set log_archive_dest_state_2='enable';
Up and running...
Now you can after doing your copy and if the parameter files are both good, try to :
On standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
On primary:
alter system set log_archive_dest_state_2='enable';