Tuesday, January 22, 2013

11gR2 :Create Physical standby from Active database using RMAN



Lots of such article in internet, also can refer to "

F.3 Using the DUPLICATE Command to Create a Standby Database" in Oracle® Data Guard Concepts and Administration 11g Release 2 (11.2)

1. In short, before we issue the DUPLICATE command, we need to prepare pfile, net service files and password file.


Here is my example.

#Primary db PFILE*.db_file_name_convert='/u01/oradata/DGS/','/u01/oradata/DG'
*.db_name='DG'
*.db_recovery_file_dest='/u01/oradata/DG/FRA'
*.db_recovery_file_dest_size=1048576000
*.DB_UNIQUE_NAME='DG'
*.fal_server='dgs'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(DG,DGS)'
*.LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DG'
*.log_archive_dest_2='service="dgs"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="dgs" net_timeout=30','valid_for=(all_logfiles,primary_role)'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DG_%t_%s_%r.arc'
*.log_file_name_convert='/u01/oradata/DGS/','/u01/oradata/DG'
*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
*.standby_file_management='AUTO'


#standby db PFILE

*.DB_NAME='DG'
*.db_recovery_file_dest='/u01/oradata/DG/FRA'
*.db_recovery_file_dest_size=1048576000
*.DB_UNIQUE_NAME='DGS'
*.fal_server='dg'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(DG,DGS)'
*.LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DGS'
*.log_archive_dest_2='service="dg"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="dg" net_timeout=30','valid_for=(all_logfiles,primary_role)'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DG_%t_%s_%r.arc'
*.log_file_name_convert='/u01/oradata/DG/','/u01/oradata/DG/'
*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
*.sga_target=681574400
*.standby_file_management='AUTO'

2. In my environment,  I use same directory structure for standby database, so need to add NOFILENAMECHECK option.

#error out, without specifying NOFILENAMECHECK
orarac1poc:DG:/u01/app/oracle/product/11.2.0/db_2/network/admin> rman target sys/oracle123@DG auxiliary sys/oracle123@DGS

Recovery Manager: Release 11.2.0.2.0 - Production on Tue Jan 22 11:41:01 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: DG (DBID=1716975309)
connected to auxiliary database: DG (not mounted)

run {
allocate channel prmy1 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database;
release channel prmy1 ;
release channel stby ;
}

using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=50 device type=DISK

allocated channel: stby
channel stby: SID=138 device type=DISK

Starting Duplicate Db at Jan 22 2013 11:41:06

contents of Memory Script:
{
   backup as copy reuse
   targetfile  '/u01/app/oracle/product/11.2.0/db_2/dbs/orapwDG' auxiliary format
 '/u01/app/oracle/product/11.2.0/db_2/dbs/orapwDGS'   ;
}
executing Memory Script

Starting backup at Jan 22 2013 11:41:06
Finished backup at Jan 22 2013 11:41:07

contents of Memory Script:
{
   backup as copy current controlfile for standby auxiliary format  '/u01/oradata/DG/control01.ctl';
   restore clone controlfile to  '/u01/oradata/DG/FRA/DG/control02.ctl' from
 '/u01/oradata/DG/control01.ctl';
}
executing Memory Script

Starting backup at Jan 22 2013 11:41:07
channel prmy1: starting datafile copy
copying standby control file
output file name=/u01/app/oracle/product/11.2.0/db_2/dbs/snapcf_DG.f tag=TAG20130122T114107 RECID=16 STAMP=805376468
channel prmy1: datafile copy complete, elapsed time: 00:00:01
Finished backup at Jan 22 2013 11:41:09

Starting restore at Jan 22 2013 11:41:09

channel stby: copied control file copy
Finished restore at Jan 22 2013 11:41:10

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

sql statement: alter database mount standby database
released channel: prmy1
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/22/2013 11:41:15
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u01/oradata/DG/dg1_tbs01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/oradata/DG/users01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/oradata/DG/undotbs01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/oradata/DG/sysaux01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/oradata/DG/system01.dbf conflicts with a file used by the target database

RMAN> exit

#fixed by specifying NOFILENAMECHECK

orarac1poc:DG:/u01/app/oracle/product/11.2.0/db_2/network/admin> rman target sys/oracle123@DG auxiliary sys/oracle123@DGS

Recovery Manager: Release 11.2.0.2.0 - Production on Tue Jan 22 11:42:44 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: DG (DBID=1716975309)
connected to auxiliary database: DG (not mounted)

run {
allocate channel prmy1 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database NOFILENAMECHECK;
release channel prmy1 ;
release channel stby ;
}

using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=52 device type=DISK

allocated channel: stby
channel stby: SID=138 device type=DISK

Starting Duplicate Db at Jan 22 2013 11:42:48

contents of Memory Script:
{
   backup as copy reuse
   targetfile  '/u01/app/oracle/product/11.2.0/db_2/dbs/orapwDG' auxiliary format
 '/u01/app/oracle/product/11.2.0/db_2/dbs/orapwDGS'   ;
}
executing Memory Script

Starting backup at Jan 22 2013 11:42:48
Finished backup at Jan 22 2013 11:42:49

contents of Memory Script:
{
   backup as copy current controlfile for standby auxiliary format  '/u01/oradata/DG/control01.ctl';
   restore clone controlfile to  '/u01/oradata/DG/FRA/DG/control02.ctl' from
 '/u01/oradata/DG/control01.ctl';
}
executing Memory Script

Starting backup at Jan 22 2013 11:42:49
channel prmy1: starting datafile copy
copying standby control file
output file name=/u01/app/oracle/product/11.2.0/db_2/dbs/snapcf_DG.f tag=TAG20130122T114249 RECID=17 STAMP=805376570
channel prmy1: datafile copy complete, elapsed time: 00:00:01
Finished backup at Jan 22 2013 11:42:51

Starting restore at Jan 22 2013 11:42:51

channel stby: copied control file copy
Finished restore at Jan 22 2013 11:42:52

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

sql statement: alter database mount standby database

contents of Memory Script:
{
   set newname for tempfile  1 to
 "/u01/oradata/DG/temp01.dbf";
   switch clone tempfile all;
   set newname for datafile  1 to
 "/u01/oradata/DG/system01.dbf";
   set newname for datafile  2 to
 "/u01/oradata/DG/sysaux01.dbf";
   set newname for datafile  3 to
 "/u01/oradata/DG/undotbs01.dbf";
   set newname for datafile  4 to
 "/u01/oradata/DG/users01.dbf";
   set newname for datafile  5 to
 "/u01/oradata/DG/dg1_tbs01.dbf";
   backup as copy reuse
   datafile  1 auxiliary format
 "/u01/oradata/DG/system01.dbf"   datafile
 2 auxiliary format
 "/u01/oradata/DG/sysaux01.dbf"   datafile
 3 auxiliary format
 "/u01/oradata/DG/undotbs01.dbf"   datafile
 4 auxiliary format
 "/u01/oradata/DG/users01.dbf"   datafile
 5 auxiliary format
 "/u01/oradata/DG/dg1_tbs01.dbf"   ;
   sql 'alter system archive log current';
}
executing Memory Script

executing command: SET NEWNAME

renamed tempfile 1 to /u01/oradata/DG/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

Starting backup at Jan 22 2013 11:42:58
channel prmy1: starting datafile copy
input datafile file number=00001 name=/u01/oradata/DG/system01.dbf
output file name=/u01/oradata/DG/system01.dbf tag=TAG20130122T114258
channel prmy1: datafile copy complete, elapsed time: 00:00:35
channel prmy1: starting datafile copy
input datafile file number=00002 name=/u01/oradata/DG/sysaux01.dbf
output file name=/u01/oradata/DG/sysaux01.dbf tag=TAG20130122T114258
channel prmy1: datafile copy complete, elapsed time: 00:00:25
channel prmy1: starting datafile copy
input datafile file number=00003 name=/u01/oradata/DG/undotbs01.dbf
output file name=/u01/oradata/DG/undotbs01.dbf tag=TAG20130122T114258
channel prmy1: datafile copy complete, elapsed time: 00:00:15
channel prmy1: starting datafile copy
input datafile file number=00005 name=/u01/oradata/DG/dg1_tbs01.dbf
output file name=/u01/oradata/DG/dg1_tbs01.dbf tag=TAG20130122T114258
channel prmy1: datafile copy complete, elapsed time: 00:00:01
channel prmy1: starting datafile copy
input datafile file number=00004 name=/u01/oradata/DG/users01.dbf
output file name=/u01/oradata/DG/users01.dbf tag=TAG20130122T114258
channel prmy1: datafile copy complete, elapsed time: 00:00:01
Finished backup at Jan 22 2013 11:44:16

sql statement: alter system archive log current

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

datafile 1 switched to datafile copy
input datafile copy RECID=17 STAMP=805376657 file name=/u01/oradata/DG/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=18 STAMP=805376657 file name=/u01/oradata/DG/sysaux01.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=19 STAMP=805376657 file name=/u01/oradata/DG/undotbs01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=20 STAMP=805376657 file name=/u01/oradata/DG/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=21 STAMP=805376657 file name=/u01/oradata/DG/dg1_tbs01.dbf
Finished Duplicate Db at Jan 22 2013 11:44:20

released channel: prmy1

released channel: stby


3. verifying

#alert log in primary


Tue Jan 22 11:42:50 2013
Clearing standby activation ID 1718696101 (0x667138a5)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
WARNING: OMF is enabled on this database. Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.

NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames.
Tue Jan 22 11:42:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*';
Tue Jan 22 11:42:58 2013
Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Tue Jan 22 11:43:02 2013
Thread 1 advanced to log sequence 10 (LGWR switch)
  Current log# 1 seq# 10 mem# 0: /u01/oradata/DG/redo01.log
Tue Jan 22 11:43:04 2013
Archived Log entry 691 added for thread 1 sequence 9 ID 0x667138a5 dest 1:
Tue Jan 22 11:44:16 2013
ALTER SYSTEM ARCHIVE LOG
Tue Jan 22 11:44:16 2013
Thread 1 advanced to log sequence 11 (LGWR switch)
  Current log# 2 seq# 11 mem# 0: /u01/oradata/DG/redo02.log
Archived Log entry 692 added for thread 1 sequence 10 ID 0x667138a5 dest 1:



#alert log of standby


Tue Jan 22 11:41:49 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Private Interface 'eth2:1' configured from GPnP for use as a private interconnect.
  [name='eth2:1', type=1, ip=169.254.231.131, mac=00-50-56-9c-1d-68, net=169.254.0.0/16, mask=255.255.0.0, use                                               =haip:cluster_interconnect/62]
Public Interface 'eth0' configured from GPnP for use as a public interface.
  [name='eth0', type=1, ip=10.139.90.42, mac=00-50-56-9c-3d-c2, net=10.139.0.0/16, mask=255.255.0.0, use=publi                                               c/1]
Public Interface 'eth0:1' configured from GPnP for use as a public interface.
  [name='eth0:1', type=1, ip=10.139.92.42, mac=00-50-56-9c-3d-c2, net=10.139.0.0/16, mask=255.255.0.0, use=pub                                               lic/1]
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options.
Using parameter settings in server-side pfile /u01/app/oracle/product/11.2.0/db_2/dbs/initDGS.ora
System parameters with non-default values:
  processes                = 150
  sga_target               = 652M
  control_files            = "/u01/oradata/DG/control01.ctl"
  control_files            = "/u01/oradata/DG/FRA/DG/control02.ctl"
  log_file_name_convert    = "/u01/oradata/DG/"
  log_file_name_convert    = "/u01/oradata/DG/"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  log_archive_dest_1       = "LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_                                               NAME=DGS"
  log_archive_dest_2       = "service="dg""
  log_archive_dest_2       = "LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_conne                                               ctions=1 reopen=300 db_unique_name="dg" net_timeout=30"
  log_archive_dest_2       = "valid_for=(all_logfiles,primary_role)"
  log_archive_dest_state_1 = "ENABLE"
  log_archive_dest_state_2 = "ENABLE"
  log_archive_min_succeed_dest= 1
  fal_server               = "dg"
  log_archive_trace        = 0
  log_archive_config       = "DG_CONFIG=(DG,DGS)"
  log_archive_format       = "DG_%t_%s_%r.arc"
  log_archive_max_processes= 4
  archive_lag_target       = 0
  db_recovery_file_dest    = "/u01/oradata/DG/FRA"
  db_recovery_file_dest_size= 1000M
  standby_file_management  = "AUTO"
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=DGXDB)"
  audit_file_dest          = "/u01/app/oracle/admin/DGS/adump"
  audit_trail              = "DB"
  db_name                  = "DG"
  db_unique_name           = "DGS"
  open_cursors             = 300
  pga_aggregate_target     = 200M
  dg_broker_start          = TRUE
  diagnostic_dest          = "/u01/app/oracle"
Cluster communication is configured to use the following interface(s) for this instance
  169.254.231.131
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Tue Jan 22 11:41:55 2013
PMON started with pid=2, OS id=10145
Tue Jan 22 11:41:56 2013
PSP0 started with pid=3, OS id=10147
Tue Jan 22 11:41:56 2013
VKTM started with pid=4, OS id=10149 at elevated priority
Tue Jan 22 11:41:56 2013
GEN0 started with pid=5, OS id=10153
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Tue Jan 22 11:41:56 2013
DIAG started with pid=6, OS id=10155
Tue Jan 22 11:41:56 2013
DBRM started with pid=7, OS id=10157
Tue Jan 22 11:41:56 2013
PING started with pid=8, OS id=10159
Tue Jan 22 11:41:56 2013
ACMS started with pid=9, OS id=10161
Tue Jan 22 11:41:56 2013
DIA0 started with pid=10, OS id=10163
Tue Jan 22 11:41:56 2013
LMON started with pid=11, OS id=10165
Tue Jan 22 11:41:56 2013
LMD0 started with pid=12, OS id=10167
* Load Monitor used for high load check
* New Low - High Load Threshold Range = [1920 - 2560]
Tue Jan 22 11:41:56 2013
RMS0 started with pid=13, OS id=10169
Tue Jan 22 11:41:56 2013
LMHB started with pid=14, OS id=10171
Tue Jan 22 11:41:56 2013
MMAN started with pid=15, OS id=10173
Tue Jan 22 11:41:56 2013
DBW0 started with pid=16, OS id=10175
Tue Jan 22 11:41:56 2013
LGWR started with pid=17, OS id=10177
Tue Jan 22 11:41:56 2013
CKPT started with pid=18, OS id=10179
Tue Jan 22 11:41:56 2013
SMON started with pid=19, OS id=10181
Tue Jan 22 11:41:56 2013
RECO started with pid=20, OS id=10183
Tue Jan 22 11:41:56 2013
MMON started with pid=21, OS id=10185
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Jan 22 11:41:56 2013
MMNL started with pid=22, OS id=10187
starting up 1 shared server(s) ...
lmon registered with NM - instance number 1 (internal mem no 0)
Reconfiguration started (old inc 0, new inc 2)
List of instances:
 1 (myinst: 1)
 Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
 Set master node info
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
 Post SMON to start 1st pass IR
 Submitted all GCS remote-cache requests
 Post SMON to start 1st pass IR
Reconfiguration complete
ORACLE_BASE from environment = /u01/app/oracle
Tue Jan 22 11:41:56 2013
DMON started with pid=25, OS id=10193
Tue Jan 22 11:42:52 2013
RFS connections have been disallowed
alter database mount standby database
Set as converted control file due to db_unique_name mismatch
Changing di2dbun from DG to DGS
ARCH: STARTING ARCH PROCESSES
Tue Jan 22 11:42:56 2013
ARC0 started with pid=30, OS id=10304
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Jan 22 11:42:57 2013
ARC1 started with pid=31, OS id=10306
Tue Jan 22 11:42:57 2013
ARC2 started with pid=32, OS id=10308
ARC1: Archival started
ARC2: Archival started
Tue Jan 22 11:42:57 2013
ARC3 started with pid=33, OS id=10310
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
ARC2: Becoming the heartbeat ARCH
ARC2: Thread not mounted
Tue Jan 22 11:42:57 2013
Successful mount of redo thread 1, with mount id 1718707580
Physical Standby Database mounted.
Lost write protection disabled
ARC2: Becoming the active heartbeat ARCH
Completed: alter database mount standby database
Tue Jan 22 11:42:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/oradata/DG/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/oradata/DG/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/oradata/DG/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/oradata/DG/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/oradata/DG/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/oradata/DG/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/u01/oradata/DG/stbredo04.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/u01/oradata/DG/stbredo04.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: '/u01/oradata/DG/stbredo05.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: '/u01/oradata/DG/stbredo05.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 6 of thread 0
ORA-00312: online log 6 thread 0: '/u01/oradata/DG/stbredo06.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 6 of thread 0
ORA-00312: online log 6 thread 0: '/u01/oradata/DG/stbredo06.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 7 of thread 0
ORA-00312: online log 7 thread 0: '/u01/oradata/DG/stbredo07.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_lgwr_10177.trc:
ORA-00313: open failed for members of log group 7 of thread 0
ORA-00312: online log 7 thread 0: '/u01/oradata/DG/stbredo07.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Tue Jan 22 11:42:59 2013
Starting Data Guard Broker (DMON)
Tue Jan 22 11:42:59 2013
INSV started with pid=35, OS id=10320
Tue Jan 22 11:44:17 2013
Switch of datafile 1 complete to datafile copy
  checkpoint is 3642688
Switch of datafile 2 complete to datafile copy
  checkpoint is 3642726
Switch of datafile 3 complete to datafile copy
  checkpoint is 3642756
Switch of datafile 4 complete to datafile copy
  checkpoint is 3642772
Switch of datafile 5 complete to datafile copy
  checkpoint is 3642770
alter database clear logfile group 1
Clearing online log 1 of thread 1 sequence number 7
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/oradata/DG/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/oradata/DG/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 1
alter database clear logfile group 2
Clearing online log 2 of thread 1 sequence number 8
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/oradata/DG/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/oradata/DG/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 2
alter database clear logfile group 3
Clearing online log 3 of thread 1 sequence number 9
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/oradata/DG/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/oradata/DG/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 3
alter database clear logfile group 4
Clearing online log 4 of thread 1 sequence number 0
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/u01/oradata/DG/stbredo04.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: '/u01/oradata/DG/stbredo04.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 4
alter database clear logfile group 5
Clearing online log 5 of thread 1 sequence number 0
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: '/u01/oradata/DG/stbredo05.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: '/u01/oradata/DG/stbredo05.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 5
alter database clear logfile group 6
Clearing online log 6 of thread 0 sequence number 0
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 6 of thread 0
ORA-00312: online log 6 thread 0: '/u01/oradata/DG/stbredo06.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 6 of thread 0
ORA-00312: online log 6 thread 0: '/u01/oradata/DG/stbredo06.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 6
alter database clear logfile group 7
Clearing online log 7 of thread 0 sequence number 0
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 7 of thread 0
ORA-00312: online log 7 thread 0: '/u01/oradata/DG/stbredo07.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/dgs/DGS/trace/DGS_ora_10282.trc:
ORA-00313: open failed for members of log group 7 of thread 0
ORA-00312: online log 7 thread 0: '/u01/oradata/DG/stbredo07.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Completed: alter database clear logfile group 7
RFS connections are allowed


4.   Start LOG APPLY
#in standby db

SYS@DGS> alter database recover managed standby database using current logfile disconnect from session;

#in primary db

SYS@DG> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES  BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------
NEXT_TIME
---------
         1          1         10   52428800        512          1 YES INACTIVE               3642692 22-JAN-13      3642778
22-JAN-13

         2          1         11   52428800        512          1 YES ACTIVE                 3642778 22-JAN-13      3643170
22-JAN-13

         3          1         12   52428800        512          1 NO  CURRENT                3643170 22-JAN-13   2.8147E+14



SYS@DG> alter system switch logfile;

System altered.

SYS@DG> alter system switch logfile;

System altered.

SYS@DG> alter system switch logfile;

System altered.



SYS@DG> select error from  v$archive_dest;

ERROR
-----------------------------------------------------------------



...



31 rows selected.

SYS@DG> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES  BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------
NEXT_TIME
---------
         1          1         13   52428800        512          1 YES INACTIVE               3643262 22-JAN-13      3643311
22-JAN-13

         2          1         14   52428800        512          1 YES ACTIVE                 3643311 22-JAN-13      3643447
22-JAN-13

         3          1         15   52428800        512          1 NO  CURRENT                3643447 22-JAN-13   2.8147E+14


#in standby database

SYS@DGS> select sequence#, applied from v$archived_log order by first_time;

 SEQUENCE# APPLIED
---------- ---------
         9 YES
        10 YES
        11 YES
        12 YES
        13 YES
        14 IN-MEMORY

6 rows selected.


Reference:

11gR2 :Create Physical standby from Active database using RMAN