17 | 08 | 2017
Latest Articles
Popular Articles

Data Guard

Create a physical standby database and a Data Guard Broker configuration

User Rating:  / 0
PoorBest 

Create a physical standby database and a Data Guard Broker configuration.



1. Move password file and spfile towards standby database server %ORACLE_HOME%\database ( or $ORACLE_HOME/dbs )
2. Configure tnsnames to primary database and standby database on both primary database server and standby database server
3. Create a full backup of your primary database using RMAN on a file system also accessible from your standby database server
4. Create a backup standby control file using RMAN on a file system also accessible from your standby database server ( see below )
5. Restore the database on the standby server as a standby database
6. Configure dg_broker_start and db_unique_name
7. Create a Data Guard Broker Conifguration
8. Monitor and troubleshoot replication initialization
9. Post configuration tasks



RMAN> run {
2> allocate channel ch1 device type disk;
3> backup as compressed backupset archivelog all filesperset 5 format '\\backupserver001\export00$\standby-silverdb001\SILVER\AL_%d_%u' skip inaccessible delete all input;
4> backup current controlfile for standby format '\\backupserver001\export00$\standby-silverdb001\SILVER\CT_STANDBY%d_%U';
5> }

allocated channel: ch1
channel ch1: sid=1627 devtype=DISK

Starting backup at 10-AUG-11
current log archived
channel ch1: starting compressed archive log backupset
channel ch1: specifying archive log(s) in backup set
input archive log thread=1 sequence=12 recid=16 stamp=758814012
channel ch1: starting piece 1 at 10-AUG-11
channel ch1: finished piece 1 at 10-AUG-11
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0SMJL59Ttag=TAG20110810T134013 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:02
channel ch1: deleting archive log(s)
archive log filename=D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_12_744VJWHW_.ARC recid=16 stamp=758814012
Finished backup at 10-AUG-11

Starting backup at 10-AUG-11
channel ch1: starting full datafile backupset
channel ch1: specifying datafile(s) in backupset
including standby control file in backupset
channel ch1: starting piece 1 at 10-AUG-11
channel ch1: finished piece 1 at 10-AUG-11
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\CT_STANDBYSILVER_0TMJL5A1_1_1 tag=TAG20110810T134017 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-AUG-11
released channel: ch1

RMAN> exit


Recovery Manager complete.

C:\Documents and Settings\e132707a>sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Aug 10 13:48:47 2011

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> show parameter db_unique_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_unique_name                       string      SILVER
SQL> show parameter dg_broker

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
dg_broker_config_file1               string      D:\SILVER\ORACLE\ORACLE102\DATABASE\DR1SILVER.DAT
dg_broker_config_file2               string      D:\SILVER\ORACLE\ORACLE102\DATABASE\DR2SILVER.DAT
dg_broker_start                      boolean     FALSE

SQL> alter system set dg_broker_start=true scope=both;

System altered.

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

 

On your standby database server startup NOMOUNT the standby database instance



RMAN> connect target sys/secret@SILVER

connected to target database: SILVER (DBID=1900454790)

RMAN> connect catalog rman/rman@rmandb

connected to recovery catalog database

RMAN> connect auxiliary /

connected to auxiliary database: SILVER (not mounted)

RMAN> run {
2> allocate auxiliary channel ch1 device type disk;
3> allocate auxiliary channel ch2 device type disk;
4> allocate auxiliary channel ch3 device type disk;
5> allocate auxiliary channel ch4 device type disk;
6> duplicate target database for standby nofilenamecheck;
7> }

allocated channel: ch1
channel ch1: sid=1639 devtype=DISK

allocated channel: ch2
channel ch2: sid=1638 devtype=DISK

allocated channel: ch3
channel ch3: sid=1637 devtype=DISK

allocated channel: ch4
channel ch4: sid=1636 devtype=DISK

Starting Duplicate Db at 10-AUG-11

contents of Memory Script:
{
restore clone standby controlfile;
sql clone 'alter database mount standby database';
}
executing Memory Script

Starting restore at 10-AUG-11

channel ch1: starting datafile backupset restore
channel ch1: restoring control file
channel ch1: reading from backup piece \\backupserver001\EXPORT00$\standby-silverdb001\SILVER\CT_STANDBYSILVER_0TMJL5A1_1_1
channel ch1: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\CT_STANDBYSILVER_0TMJL5A1_1_1 tag=TAG20110810T134017
channel ch1: restore complete, elapsed time: 00:00:02
output filename=D:\SILVERDATABASE\ORADATA\SILVER\CONTROL01.CTL
output filename=D:\SILVERMIRRORDB\ORADATA\SILVER\CONTROL02.CTL
output filename=D:\SILVERMIRRORDB\ORADATA\SILVER\CONTROL03.CTL
Finished restore at 10-AUG-11

sql statement: alter database mount standby database

contents of Memory Script:
{
set newname for tempfile  1 to
"D:\SILVERDATABASE\ORADATA\SILVER\TEMP01.DBF";
switch clone tempfile all;
set newname for datafile  1 to
"D:\SILVERDATABASE\ORADATA\SILVER\SYSTEM01.DBF";
set newname for datafile  2 to
"D:\SILVERDATABASE\ORADATA\SILVER\UNDOTBS01.DBF";
set newname for datafile  3 to
"D:\SILVERDATABASE\ORADATA\SILVER\SYSAUX01.DBF";
set newname for datafile  4 to
"D:\SILVERDATABASE\ORADATA\SILVER\INDEX01.DBF";
set newname for datafile  5 to
"D:\SILVERDATABASE\ORADATA\SILVER\USERS01.DBF";
set newname for datafile  6 to
"D:\SILVERDATABASE\ORADATA\SILVER\USERS02.DBF";
set newname for datafile  7 to
"D:\SILVERDATABASE\ORADATA\SILVER\USERS03.DBF";
set newname for datafile  8 to
"D:\SILVERDATABASE\ORADATA\SILVER\USERS04.DBF";
restore
check readonly
clone database
;
}
executing Memory Script

executing command: SET NEWNAME

renamed temporary file 1 to D:\SILVERDATABASE\ORADATA\SILVER\TEMP01.DBF in control file

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 10-AUG-11

channel ch1: starting datafile backupset restore
channel ch1: specifying datafile(s) to restore from backup set
restoring datafile 00003 to D:\SILVERDATABASE\ORADATA\SILVER\SYSAUX01.DBF
restoring datafile 00004 to D:\SILVERDATABASE\ORADATA\SILVER\INDEX01.DBF
restoring datafile 00006 to D:\SILVERDATABASE\ORADATA\SILVER\USERS02.DBF
restoring datafile 00008 to D:\SILVERDATABASE\ORADATA\SILVER\USERS04.DBF
channel ch1: reading from backup piece \\backupserver001\EXPORT00$\standby-silverdb001\SILVER\DB_SILVER_0LMJJOP4_1_1
channel ch2: starting datafile backupset restore
channel ch2: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\SILVERDATABASE\ORADATA\SILVER\SYSTEM01.DBF
restoring datafile 00002 to D:\SILVERDATABASE\ORADATA\SILVER\UNDOTBS01.DBF
restoring datafile 00005 to D:\SILVERDATABASE\ORADATA\SILVER\USERS01.DBF
restoring datafile 00007 to D:\SILVERDATABASE\ORADATA\SILVER\USERS03.DBF
channel ch2: reading from backup piece \\backupserver001\EXPORT00$\standby-silverdb001\SILVER\DB_SILVER_0KMJJOP4_1_1
channel ch1: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\DB_SILVER_0LMJJOP4_1_1 tag=TAG20110810T010020
channel ch1: restore complete, elapsed time: 00:01:05
channel ch2: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\DB_SILVER_0KMJJOP4_1_1 tag=TAG20110810T010020
channel ch2: restore complete, elapsed time: 00:01:05
Finished restore at 10-AUG-11

contents of Memory Script:
{
switch clone datafile all;
}
executing Memory Script

datafile 1 switched to datafile copy
input datafile copy recid=9 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\SYSTEM01.DBF
datafile 2 switched to datafile copy
input datafile copy recid=10 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\UNDOTBS01.DBF
datafile 3 switched to datafile copy
input datafile copy recid=11 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\SYSAUX01.DBF
datafile 4 switched to datafile copy
input datafile copy recid=12 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\INDEX01.DBF
datafile 5 switched to datafile copy
input datafile copy recid=13 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\USERS01.DBF
datafile 6 switched to datafile copy
input datafile copy recid=14 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\USERS02.DBF
datafile 7 switched to datafile copy
input datafile copy recid=15 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\USERS03.DBF
datafile 8 switched to datafile copy
input datafile copy recid=16 stamp=758814459 filename=D:\SILVERDATABASE\ORADATA\SILVER\USERS04.DBF
Finished Duplicate Db at 10-AUG-11
released channel: ch1
released channel: ch2
released channel: ch3
released channel: ch4


RMAN> exit


Recovery Manager complete.


Adjust initialization parameters


C:\Documents and Settings\e132707a>sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Aug 10 13:50:01 2011

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>  alter system set dg_broker_start=true scope=both;

System altered.

SQL> show parameter db_unique_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_unique_name                       string      SILVER


SQL> alter system set db_unique_name='SILVER_SDB' scope=spfile;

System altered.

SQL> shutdown immediate;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size                  2067104 bytes
Variable Size             486540640 bytes
Database Buffers         1644167168 bytes
Redo Buffers               14708736 bytes
Database mounted.


SQL> show parameter db_unique_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_unique_name                       string      SILVER_SDB




On primary site create a Data Guard Broker configuration


C:\Documents and Settings\e132707a>dgmgrl
DGMGRL for 64-bit Windows: Version 10.2.0.4.0 - 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect /
Connected.

DGMGRL> create configuration 'SILVER_STANDBY' as primary database is 'SILVER' connect identifier is SILVER;
Configuration "SILVER_STANDBY" created with primary database "SILVER"

DGMGRL> add database 'SILVER_SDB' as connect identifier is SILVER_SDB maintained as physical;
Database "SILVER_SDB" added

DGMGRL> show configuration;

Configuration
Name:                SILVER_STANDBY
Enabled:             NO
Protection Mode:     MaxPerformance
Fast-Start Failover: DISABLED
Databases:
SILVER     - Primary database
SILVER_SDB - Physical standby database

Current status for "SILVER_STANDBY":
DISABLED

DGMGRL> enable configuration;
Enabled.
DGMGRL>


On the standby database server, examine the alert log of the standby instance

Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 6880
RFS[3]: Identified database type as 'physical standby'
RFS[3]: Archived Log: 'D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_15_744X0KC3_.ARC'
Wed Aug 10 14:06:05 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 10-12
DBID 1900454790 branch 758026438
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------



On the primary database ( since we have a GAP ( I actually should not have backed up some archives, no problem we restore them )



C:\Documents and Settings\e132707a>rman

Recovery Manager: Release 10.2.0.4.0 - Production on Wed Aug 10 14:17:42 2011

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

RMAN> connect target sys/secret

connected to target database: SILVER (DBID=1900454790)

RMAN> connect catalog rman/rman@rmandb

connected to recovery catalog database

RMAN> restore archivelog from logseq 10 until logseq 12;

Starting restore at 10-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1614 devtype=DISK

channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=11
channel ORA_DISK_1: reading from backup piece \\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0PMJJOPP
channel ORA_DISK_1: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0PMJJOPP
tag=TAG20110810T010041
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=10
channel ORA_DISK_1: reading from backup piece \\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0OMJJOPP
channel ORA_DISK_1: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0OMJJOPP
tag=TAG20110810T010041
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=12
channel ORA_DISK_1: reading from backup piece \\backupserver001\EXPORT00$\CENEMPDB0
01\SILVER\AL_SILVER_0SMJL59T
channel ORA_DISK_1: restored backup piece 1
piece handle=\\backupserver001\EXPORT00$\standby-silverdb001\SILVER\AL_SILVER_0SMJL59T
tag=TAG20110810T134013
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
Finished restore at 10-AUG-11


On the standby database server, examine the alert log of the standby instance.



Wed Aug 10 14:19:10 2011
RFS[3]: Archived Log: 'D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_10_744XSWF5_.ARC'
RFS[3]: Archived Log: 'D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_11_744XSYQC_.ARC'
RFS[3]: Archived Log: 'D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_12_744XSYS9_.ARC'
Wed Aug 10 14:19:35 2011
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_10_744XSWF5_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_11_744XSYQC_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_12_744XSYS9_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_13_744WYVTR_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_14_744WYWNF_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_10\O1_MF_1_15_744X0KC3_.ARC
Media Recovery Waiting for thread 1 sequence 16




Adding standby redo logs and standby file management auto. On the primary database server, verify standby file management.



SQL> show parameter standby_file_management

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
standby_file_management              string      manual

On the standby server we add standby redo log files, we adjust log expedition mode to ASYNC (we then use the standby redo logs)Note that this despite the attribute LOGXPTMODE and we set standby file management to AUTO.

 

 

C:\Documents and Settings\e132707a>dgmgrl /
DGMGRL for 64-bit Windows: Version 10.2.0.4.0 - 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.
DGMGRL> edit database 'SILVER_SDB' set state='LOG-APPLY-OFF';
Succeeded.
DGMGRL> exit

C:\Documents and Settings\e132707a>sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Aug 11 09:27:15 2011

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select group#,bytes/(1024*1024) from v$log;

GROUP# BYTES/(1024*1024)
---------- -----------------
1               512
4               512
3               512
2               512

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------

D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_1_744WYSWQ_.LOG
D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_2_744WYWH1_.LOG
D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_3_744WZ0JJ_.LOG
D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_4_744WZ54S_.LOG

SQL> alter database add standby logfile group 10 size 512M;

Database altered.

SQL> alter database add standby logfile group 11 size 512M;

Database altered.

SQL> alter database add standby logfile group 12 size 512M;

Database altered.

SQL> alter database add standby logfile group 13 size 512M;

Database altered.

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64
bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

C:\Documents and Settings\e132707a>dgmgrl /
DGMGRL for 64-bit Windows: Version 10.2.0.4.0 - 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.
DGMGRL> show database verbose 'SILVER_SDB';

Database
Name:            SILVER_SDB
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State:  LOG-APPLY-OFF
Instance(s):
SILVER

Properties:
InitialConnectIdentifier        = 'SILVER_sdb'
ObserverConnectIdentifier       = ''
LogXptMode                      = 'ARCH'
Dependency                      = ''
DelayMins                       = '0'
Binding                         = 'OPTIONAL'
MaxFailure                      = '0'
MaxConnections                  = '1'
ReopenSecs                      = '300'
NetTimeout                      = '180'
LogShipping                     = 'ON'
PreferredApplyInstance          = ''
ApplyInstanceTimeout            = '0'
ApplyParallel                   = 'AUTO'
StandbyFileManagement           = 'MANUAL'
ArchiveLagTarget                = '0'
LogArchiveMaxProcesses          = '2'
LogArchiveMinSucceedDest        = '1'
DbFileNameConvert               = ''
LogFileNameConvert              = ''
FastStartFailoverTarget         = ''
StatusReport                    = '(monitor)'
InconsistentProperties          = '(monitor)'
InconsistentLogXptProps         = '(monitor)'
SendQEntries                    = '(monitor)'
LogXptStatus                    = '(monitor)'
RecvQEntries                    = '(monitor)'
HostName                        = 'standby-silverdb001'
SidName                         = 'SILVER'
LocalListenerAddress            = '(ADDRESS=(PROTOCOL=tcp)(HOST=standby-silverdb001)(PORT=1521))'
StandbyArchiveLocation          = '%ORACLE_HOME%\RDBMS'
AlternateLocation               = ''
LogArchiveTrace                 = '0'
LogArchiveFormat                = 'ARC%S_%R.%T'
LatestLog                       = '(monitor)'
TopWaitEvents                   = '(monitor)'

Current status for "SILVER_SDB":
SUCCESS

DGMGRL> edit database 'SILVER_SDB' set property LogXptMode = ASYNC;
Property "logxptmode" updated
DGMGRL> edit database 'SILVER_SDB' set property standbyfilemanagement = AUTO;
Property "standbyfilemanagement" updated
DGMGRL> edit database 'SILVER' set property standbyfilemanagement = AUTO;
Property "standbyfilemanagement" updated
DGMGRL> edit database 'SILVER_SDB' set state=ONLINE;
Succeeded.

We verify the primary database alert file.



Thread 1 advanced to log sequence 25 (LGWR switch)
Current log# 1 seq# 25 mem# 0: D:\SILVERDATABASE\ORADATA\SILVER\REDO01.LOG
Current log# 1 seq# 25 mem# 1: D:\SILVERMIRRORDB\ORADATA\SILVER\REDO201.LOG
Thu Aug 11 09:42:01 2011
******************************************************************
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_1
******************************************************************
LNS: Standby redo logfile selected for thread 1 sequence 25 for destination LOG_ARCHIVE_DEST_1


We verify the standby database alert file.



Waiting for all non-current ORLs to be archived...
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_11\O1_MF_1_22_74711LSS_.ARC
Thu Aug 11 09:41:59 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE
Thu Aug 11 09:42:01 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[10]: Assigned to RFS process 5344
RFS[10]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Re-archiving standby log 10 thread 1 sequence 24
Primary database is in MAXIMUM PERFORMANCE mode
RFS[10]: Successfully opened standby log 10: 'D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_10_7471L298_.LOG'
Thu Aug 11 09:42:24 2011
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_11\O1_MF_1_23_7471WP52_.ARC
Media Recovery Log D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ARCHIVELOG\2011_08_11\O1_MF_1_24_7471Y9O4_.ARC
Media Recovery Waiting for thread 1 sequence 25 (in transit)
Thu Aug 11 09:42:25 2011
Recovery of Online Redo Log: Thread 1 Group 10 Seq 25 Reading mem 0
Mem# 0: D:\SILVER\ORACLE\FLASH_RECOVERY_AREA\SILVER\ONLINELOG\O1_MF_10_7471L298_.LOG
Thu Aug 11 09:42:42 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[11]: Assigned to RFS process 1116
RFS[11]: Identified database type as 'physical standby'



At level of primary database adjust force logging to force generation of redo, to protect against nologging operations.


SQL> alter database force logging;

Database altered.



At level of standby database adjust archive logging deletion policy to applied on standby.




RMAN> configure archivelog deletion policy to applied on standby;

using target database control file instead of recovery catalog
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\SILVER\ORACLE\ORACLE102\DATABASE\SNCFSILVER.ORA'; # default

 

For archivelog deletion policy see also Data Guard : Adjust RMAN' s archivelog deletion policy