-- Oracle 12c Data Guard-- 12c DG 特点及搭建注意点- 特点;Oracle 12c 的DataGuard 是在CDB级别实现的.但在有pdb的情况下与12c之前的版本有些区别.在Oracle 12c的架构里，online redo log 和控制文件是保存在CDB中的，PDB中只有自己的数据文件，所以我们这里加standby redo log，也是在CDB中加。- 注意点;备库在 rman restore数据文件时,需要注意创建pdb(还有pdbseed数据库)的目录.-- 规划- cat /etc/hosts192.168.128.228 wh -- PRimary192.168.128.229 sh -- standby 用主库上的PDB：POC_PDB 做我们的主库。- 实例名：DG Role --- DB_UNIQUE_NAME --- Oracle Net Service NamePrimary poc_shpoc_shstandby poc_whpoc_wh- 归档路径;/u01/fra -- FRA-- 环境SQL> select * from v$version;BANNER CON_ID-------------------------------------------------------------------------------- ----------Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production 0PL/SQL Release 12.1.0.2.0 - Production 0CORE 12.1.0.2.0 Production 0TNS for linux: Version 12.1.0.2.0 - Production 0NLSRTL Version 12.1.0.2.0 - Production 0SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 POC_PDB READ WRITE NOSQL> SELECT SYS_CONTEXT ('USERENV', 'CON_NAME') FROM DUAL;SYS_CONTEXT('USERENV','CON_NAME')----------------------------------------------------------------------------------------------------CDB$ROOT--- DG 搭建 主库端- 主库启动FORCE LOGGINGSQL> select name,open_mode from v$pdbs;NAME OPEN_MODE------------------------------ ----------PDB$SEED READ ONLYPOC_PDB READ WRITESQL> alter database force logging;SQL> select force_logging from v$database;-- 归档直接放在FRA, pcb到open状态SQL> show parameter recoverySQL> alter system set db_recovery_file_dest_size=1G;SQL> alter system set db_recovery_file_dest='/u01/fra';SQL> show parameter db_recoverNAME TYPE VALUE------------------------------------ ----------- ------------------------------db_recovery_file_dest string /u01/fradb_recovery_file_dest_size big integer 1GSQL> select name,open_mode from v$pdbs;NAME OPEN_MODE------------------------------ ----------PDB$SEED READ ONLYPOC_PDB MOUNTEDSQL> alter pluggable database POC_PDB open;SQL> select name,open_mode from v$pdbs;NAME OPEN_MODE------------------------------ ----------PDB$SEED READ ONLYPOC_PDB READ WRITE-- 启动归档模式SQL> show con_name --确认在cdb下.CON_NAME------------------------------CDB$ROOTSQL> archive log list;SQL> shutdown immediateSQL> startup mountSQL> alter database archivelog;-- 在主库添加 standby redo logfile查看 Primary 库的 REDO 相关信息： SQL> show con_nameselect group#, members, bytes/1024/1024 m from v$log;select member from v$logfile;alter database add standby logfile thread 1group 10 ('/u01/oradata/poc/sbredo10.log')size 50M,group 11 ('/u01/oradata/poc/sbredo11.log')size 50M,group 12 ('/u01/oradata/poc/sbredo12.log')size 50M,group 13 ('/u01/oradata/poc/sbredo13.log')size 50M;SQL> select GROUP#,THREAD#,BYTES/1024/1024 from v$standby_log; GROUP# THREAD# BYTES/1024/1024---------- ---------- --------------- 10 1 50 11 1 50 12 1 50 13 1 50-- 主备库配置静态监听- 使用netmgr工具生成,或手工编辑[oracle@wh ~]$ vi /u01/app/oracle/product/12.1/db_1/network/admin/listener.ora# listener.ora Network Configuration File: /u01/app/oracle/product/12.1/db_1/network/admin/listener.ora# Generated by Oracle configuration tools.SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = POC) (ORACLE_HOME = /u01/app/oracle/product/12.1/db_1) (SID_NAME = POC) --注意; 是cdb ) )LISTENER = (DESCRipTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = wh)(PORT = 1521)) ) (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) )ADR_BASE_LISTENER = /u01/app/oraclelsnrctl reloadlsnrctl status (看到1个 UNKNOW状态的Service )[oracle@wh ~]$ lsnrctl statusLSNRCTL for Linux: Version 12.1.0.2.0 - Production on 07-FEB-2017 09:56:07Copyright (c) 1991, 2014, Oracle. All rights reserved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=wh)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux: Version 12.1.0.2.0 - ProductionStart Date 06-FEB-2017 14:52:45Uptime 0 days 19 hr. 3 min. 22 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File /u01/app/oracle/product/12.1/db_1/network/admin/listener.oraListener Log File /u01/app/oracle/diag/tnslsnr/wh/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=wh)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))Services Summary...Service "POC" has 1 instance(s). Instance "POC", status UNKNOWN, has 1 handler(s) for this service... -- 静态监听Service "pocXDB" has 1 instance(s). Instance "poc", status READY, has 1 handler(s) for this service...Service "poc_pdb" has 1 instance(s). Instance "poc", status READY, has 1 handler(s) for this service...Service "poc_wh" has 1 instance(s). Instance "poc", status READY, has 1 handler(s) for this service...The command completed successfully-- 分别在主备库配置tnsnames.ora$ORACLE_HOME/network/admin/tnsnames.ora-添加如下;poc_wh = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = wh)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = POC) -- 与listener.ora中的 unknow状态的静态监听一致. ) )poc_sh = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = sh)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = POC) ) ) - 测试 sqlplus sys/oracle@poc_sh as sysdbasqlplus sys/oracle@poc_wh as sysdba -- 在备库创建必要的目录su - oraclemkdir -p /u01/framkdir -p /u01/oradata/poc/poc_pdbmkdir -p /u01/oradata/poc/pdbseedmkdir -p /u01/app/oracle/admin/poc/adump-- 主库修改参数alter system set db_unique_name='poc_wh' scope=spfile;alter system set log_archive_config='dg_config=(poc_wh,poc_sh)';alter system set log_archive_dest_1='location=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) db_unique_name=poc_wh' scope=spfile;alter system set log_archive_dest_2='service=poc_sh reopen=120 lgwr async valid_for=(online_logfiles,primary_role) db_unique_name=poc_sh';alter system set log_archive_dest_state_1=enable;alter system set log_archive_dest_state_2=enable;alter system set standby_file_management='auto';- alter system set DB_FILE_NAME_CONVERT='/u01/oradata/poc','/u01/oradata/poc' scope=spfile;alter system set LOG_FILE_NAME_CONVERT='/u01/oradata/poc','/u01/oradata/poc' scope=spfile;- 重启数据库,使得新参数生效SQL> shutdown immediatestartup- 创建pfileSQL>create pfile='/home/oracle/pfile' from spfile;-- 9 主库口令文件到备库-- 10 主库参数文件到备库,并修改-- 11 备库使用pfile创建spfile并启动到nomount状态.SQL>startup nomount pfile='/home/oracle/pfile';create spfile from pfile='/home/oracle/pfile';shutdown immediatestartup nomount;show parameter spfile;-- 12 创建备库- Primary端,创建备份rman target /run{ALLOCATE CHANNEL c1 TYPE disk;BACKUP AS COMPRESSED BACKUPSET FULL DATABASE FILESPERSET 10 FORMAT '/u01/rman_bak/dbfull_%M%D_%U.bus';RELEASE CHANNEL c1;}[oracle@wh ~]$ rman target /run{ALLOCATE CHANNEL c1 TYPE disk;BACKUP AS COMPRESSED BACKUPSET FULL DATABASE FILESPERSET 10 FORMAT '/u01/rman_bak/dbfull_%M%D_%U.bus';RELEASE CHANNEL c1;}Recovery Manager: Release 12.1.0.2.0 - Production on Mon Feb 6 15:16:55 2017Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.connected to target database: POC (DBID=1572033017)RMAN> 2> 3> 4> 5> using target database control file instead of recovery catalogallocated channel: c1channel c1: SID=367 device type=DISKStarting backup at 06-FEB-17channel c1: starting compressed full datafile backup setchannel c1: specifying datafile(s) in backup setinput datafile file number=00005 name=/u01/oradata/poc/undotbs01.dbfinput datafile file number=00003 name=/u01/oradata/poc/sysaux01.dbfinput datafile file number=00001 name=/u01/oradata/poc/system01.dbfinput datafile file number=00006 name=/u01/oradata/poc/users01.dbfchannel c1: starting piece 1 at 06-FEB-17channel c1: finished piece 1 at 06-FEB-17piece handle=/u01/rman_bak/dbfull_0206_02rrtgn9_1_1.bus tag=TAG20170206T151657 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:55channel c1: starting compressed full datafile backup setchannel c1: specifying datafile(s) in backup setinput datafile file number=00008 name=/u01/oradata/poc/poc_pdb/sysaux01.dbfinput datafile file number=00007 name=/u01/oradata/poc/poc_pdb/system01.dbfinput datafile file number=00009 name=/u01/oradata/poc/poc_pdb/poc_pdb_users01.dbfchannel c1: starting piece 1 at 06-FEB-17channel c1: finished piece 1 at 06-FEB-17piece handle=/u01/rman_bak/dbfull_0206_03rrtgp1_1_1.bus tag=TAG20170206T151657 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:25channel c1: starting compressed full datafile backup setchannel c1: specifying datafile(s) in backup setinput datafile file number=00004 name=/u01/oradata/poc/pdbseed/sysaux01.dbfinput datafile file number=00002 name=/u01/oradata/poc/pdbseed/system01.dbfchannel c1: starting piece 1 at 06-FEB-17channel c1: finished piece 1 at 06-FEB-17piece handle=/u01/rman_bak/dbfull_0206_04rrtgpq_1_1.bus tag=TAG20170206T151657 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:25Finished backup at 06-FEB-17Starting Control File and SPFILE Autobackup at 06-FEB-17piece handle=/u01/fra/POC_WH/autobackup/2017_02_06/o1_mf_s_935248723_d9j8tmgt_.bkp comment=NONEFinished Control File and SPFILE Autobackup at 06-FEB-17released channel: c1RMAN> exitRecovery Manager complete.[oracle@wh ~]$ - Primary,创建standby控制文件SQL> alter database create standby controlfile as '/u01/rman_bak/control01.ctl';- 把rman备份，crontfile 从主库传到备库- 启动standby数据库到mount状态$ mv /u01/rman_bak/control01.ctl /u01/oradata/poc/control01.ctl (将从Primary传来的带有rman备份信息的control，复制到pfile中的位置)$ cp /u01/oradata/poc/control01.ctl /u01/oradata/poc/control02.ctlsqlplus / as sysdbastartup mount - 使用RMAN restore数据文件RMAN target /RMAN> restore database; （由于需要把datafile 恢复到1T，非常缓慢）RMAN> restore database;Starting restore at 07-FEB-17using channel ORA_DISK_1datafile 1 is already restored to file /u01/oradata/poc/system01.dbfdatafile 3 is already restored to file /u01/oradata/poc/sysaux01.dbfdatafile 5 is already restored to file /u01/oradata/poc/undotbs01.dbfdatafile 6 is already restored to file /u01/oradata/poc/users01.dbfskipping datafile 7; already restored to file /u01/oradata/poc/poc_pdb/system01.dbfskipping datafile 8; already restored to file /u01/oradata/poc/poc_pdb/sysaux01.dbfskipping datafile 9; already restored to file /u01/oradata/poc/poc_pdb/poc_pdb_users01.dbfchannel ORA_DISK_1: starting datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setchannel ORA_DISK_1: restoring datafile 00002 to /u01/oradata/poc/pdbseed/system01.dbfchannel ORA_DISK_1: restoring datafile 00004 to /u01/oradata/poc/pdbseed/sysaux01.dbfchannel ORA_DISK_1: reading from backup piece /u01/rman_bak/dbfull_0206_04rrtgpq_1_1.buschannel ORA_DISK_1: piece handle=/u01/rman_bak/dbfull_0206_04rrtgpq_1_1.bus tag=TAG20170206T151657channel ORA_DISK_1: restored backup piece 1channel ORA_DISK_1: restore complete, elapsed time: 00:00:35Finished restore at 07-FEB-17RMAN> -- 13 启动备库并启动apply- restore后备库是mount状态;SQL> select open_mode from v$database; -- mount状态OPEN_MODE--------------------MOUNTEDSQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED---------- ------------------------------ ---------- ---------- 2 PDB$SEED MOUNTED 3 POC_PDB MOUNTEDSQL> alter database open; -- cdb(poc) 到open状态Database altered.SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO -- 变为 read only 3 POC_PDB MOUNTEDSQL> select open_mode from v$database;OPEN_MODE--------------------READ ONLY -- cdb 由 mount状态 变为 read only状态SQL> alter pluggable database poc_pdb open;Pluggable database altered.SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 POC_PDB READ ONLY NO -- 变为 read only- 主备库状态SQL> select log_mode,open_mode ,database_role from v$database;LOG_MODE OPEN_MODE DATABASE_ROLE------------ -------------------- ----------------ARCHIVELOG READ WRITE PRIMARY- 备库启动real-time applySQL> alter database recover managed standby database using current logfile disconnect from session;2017-02-07 15:15:27.419000 +08:00Archived Log entry 6 added for thread 1 sequence 202 ID 0x5db35af9 dest 1:2017-02-07 15:44:50.598000 +08:00Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated.Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated.alter database recover managed standby database using current logfile disconnect from sessionAttempt to start background Managed Standby Recovery process (poc)Starting background process MRP0MRP0 started with pid=43, OS id=11310 MRP0: Background Managed Standby Recovery process started (poc)2017-02-07 15:44:55.641000 +08:00 Started logmerger processManaged Standby Recovery starting Real Time ApplyParallel Media Recovery started with 4 slavesWaiting for all non-current ORLs to be archived...All non-current ORLs have been archived.Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 1 /u01/oradata/poc/redo01.logClearing online log 1 of thread 1 sequence number 196Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_m000_11322.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_m000_11322.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 1 completeErrors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 2 /u01/oradata/poc/redo02.logClearing online log 2 of thread 1 sequence number 197Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 32017-02-07 15:44:56.623000 +08:00Completed: alter database recover managed standby database using current logfile disconnect from sessionClearing online redo logfile 2 completeErrors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 3 /u01/oradata/poc/redo03.logClearing online log 3 of thread 1 sequence number 195Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 3 completeMedia Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_197_d9lv0gpq_.arc2017-02-07 15:44:59.192000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_198_d9lv0gpt_.arc2017-02-07 15:45:02.667000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_199_d9lv0gpm_.arcResize Operation completed for file# 3, old size 1075200K, new size 1085440K2017-02-07 15:45:04.810000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_200_d9lv0vwl_.arc2017-02-07 15:45:06.447000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_201_d9lv0wj9_.arcMedia Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_202_d9lx0h6c_.arc2017-02-07 15:45:08.310000 +08:00Media Recovery Waiting for thread 1 sequence 203 (in transit)Recovery of Online Redo Log: Thread 1 Group 13 Seq 203 Reading mem 0 Mem# 0: /u01/oradata/poc/sbredo13.logSQL> select open_mode from v$database;- 主库;SQL> alter system switch logfile;备库;2017-02-07 15:47:23.977000 +08:00RFS[1]: Selected log 11 for thread 1 sequence 205 dbid 1572033017 branch 934278201Archived Log entry 8 added for thread 1 sequence 204 ID 0x5db35af9 dest 1:Media Recovery Waiting for thread 1 sequence 205 (in transit)Recovery of Online Redo Log: Thread 1 Group 11 Seq 205 Reading mem 0 Mem# 0: /u01/oradata/poc/sbredo11.log-- 14 验证DG同步- 主库;SQL> SELECT SYS_CONTEXT ('USERENV', 'CON_NAME') FROM DUAL;-- 查看当前处在哪个容器中.alter session set Container=poc_pdb; -- 进入pdbcreate table cndba as select * from dba_users;SQL> alter system switch logfile; --提示 ora-65040 log在cdb级别,pdb不能切换alter system switch logfile *ERROR at line 1:ORA-16000: database or pluggable database open for read-only accessalter session set Container=CDB$ROOT; -- 切换到cdbalter system switch logfile;--- 问题;1. 在备库rman restore database完成后, alert日志报错如下;ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_lgwr_11161.trc:在dg同步开启后,主库切换几次日志,备库就会自动创建出 redo,standby redorestore 完成后,备库目录;[root@sh ~]# ll /u01/oradata/poc/total 3492180-rw-r----- 1 oracle oinstall 17973248 Feb 7 15:00 control01.ctl-rw-r----- 1 oracle oinstall 17973248 Feb 7 15:00 control02.ctldrwxr-xr-x 2 oracle oinstall 4096 Feb 7 14:54 pdbseeddrwxr-xr-x 2 oracle oinstall 4096 Feb 7 14:57 poc_pdb-rw-r----- 1 oracle oinstall 1101012992 Feb 7 14:54 sysaux01.dbf-rw-r----- 1 oracle oinstall 849354752 Feb 7 14:54 system01.dbf-rw-r----- 1 oracle oinstall 20979712 Feb 7 14:54 temp01.dbf-rw-r----- 1 oracle oinstall 1583357952 Feb 7 14:54 undotbs01.dbf-rw-r----- 1 oracle oinstall 5251072 Feb 7 14:54 users01.dbfdg同步,并切换数个日志后,[root@sh ~]# ll /u01/oradata/poc/total 3860848-rw-r----- 1 oracle oinstall 17973248 Feb 7 15:48 control01.ctl-rw-r----- 1 oracle oinstall 17973248 Feb 7 15:48 control02.ctldrwxr-xr-x 2 oracle oinstall 4096 Feb 7 14:54 pdbseeddrwxr-xr-x 2 oracle oinstall 4096 Feb 7 14:57 poc_pdb-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:44 redo01.log -- redo-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:44 redo02.log-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:44 redo03.log-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:48 sbredo10.log -- standby redo-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:48 sbredo11.log-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:15 sbredo12.log-rw-r----- 1 oracle oinstall 52429312 Feb 7 15:47 sbredo13.log-rw-r----- 1 oracle oinstall 1111498752 Feb 7 15:48 sysaux01.dbf-rw-r----- 1 oracle oinstall 849354752 Feb 7 15:48 system01.dbf-rw-r----- 1 oracle oinstall 20979712 Feb 7 14:54 temp01.dbf-rw-r----- 1 oracle oinstall 1583357952 Feb 7 15:48 undotbs01.dbf-rw-r----- 1 oracle oinstall 5251072 Feb 7 15:48 users01.dbf在备库开启恢复后,会开始 clear redo, 注意alert日志中的 "Clearing online redo logfile 3 complete".2017-02-07 15:44:50.598000 +08:00Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated.Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated.alter database recover managed standby database using current logfile disconnect from sessionAttempt to start background Managed Standby Recovery process (poc)Starting background process MRP0MRP0 started with pid=43, OS id=11310 MRP0: Background Managed Standby Recovery process started (poc)2017-02-07 15:44:55.641000 +08:00 Started logmerger processManaged Standby Recovery starting Real Time ApplyParallel Media Recovery started with 4 slavesWaiting for all non-current ORLs to be archived...All non-current ORLs have been archived.Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 1 /u01/oradata/poc/redo01.logClearing online log 1 of thread 1 sequence number 196Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/oradata/poc/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_m000_11322.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_m000_11322.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 1 completeErrors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 2 /u01/oradata/poc/redo02.logClearing online log 2 of thread 1 sequence number 197Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/oradata/poc/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 32017-02-07 15:44:56.623000 +08:00Completed: alter database recover managed standby database using current logfile disconnect from sessionClearing online redo logfile 2 completeErrors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 3 /u01/oradata/poc/redo03.logClearing online log 3 of thread 1 sequence number 195Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Errors in file /u01/app/oracle/diag/rdbms/poc_sh/poc/trace/poc_mrp0_11310.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/oradata/poc/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Clearing online redo logfile 3 completeMedia Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_197_d9lv0gpq_.arc2017-02-07 15:44:59.192000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_198_d9lv0gpt_.arc2017-02-07 15:45:02.667000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_199_d9lv0gpm_.arcResize operation completed for file# 3, old size 1075200K, new size 1085440K2017-02-07 15:45:04.810000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_200_d9lv0vwl_.arc2017-02-07 15:45:06.447000 +08:00Media Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_201_d9lv0wj9_.arcMedia Recovery Log /u01/fra/POC_SH/archivelog/2017_02_07/o1_mf_1_202_d9lx0h6c_.arc2017-02-07 15:45:08.310000 +08:00Media Recovery Waiting for thread 1 sequence 203 (in transit)Recovery of Online Redo Log: Thread 1 Group 13 Seq 203 Reading mem 0 Mem# 0: /u01/oradata/poc/sbredo13.log
