Rman配置DataGuard 使用主库未配置时备份 with filesystem
2016-08-21 12:19
423 查看
一、 环境
| 主机名 | 数据库版本 | dbname | db_unique_name | IP地址 | 系统版本 |
| Jason1(主) | oracle11204 | Jason | jason1 | 192.168.1.99 | rhel6.6_x86_64 |
| jason2(备) | jason2 | 192.168.1.100 |
二、 主库配置
1. 确定主数据库开启强制LOGGING模式
[oracle@jason1 ~]$ sqlplus /nolog SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 20:45:33 2016 Copyright (c) 1982, 2013, Oracle. All rights reserved. SQL> conn /as sysdbaConnected. SQL> ALTER DATABASE FORCE LOGGING; Database altered. SQL> select force_logging from v$database; FOR---YES2. 开启归档
SQL> archive log list;Database log mode Archive ModeAutomatic archival EnabledArchive destination USE_DB_RECOVERY_FILE_DESTOldest online log sequence 3Next log sequence to archive 5Current log sequence 5SQL> select group#,bytes/1024/1024 from v$log; GROUP# BYTES/1024/1024---------- --------------- 1 50 3 50 2 503. 备份主库
创建备份存放目录，使用如下脚本备份主库。mkdir /data
chown oracle:oinstall /data
run
{
backup database include current controlfile
format '/data/fulldb_%U.bak'
plus archivelog
format '/data/arch_%U.bak';
}
备份结束后手工切换产生归档日志，模拟一天的归档量然后开始配置主库DG参数。
4. 创建standby日志组
1).standby redo log的文件大小与primary 数据库online redo log 文件大小相同2).standby redo log日志文件组的个数依照下面的原则进行计算 Standby redo log组数公式>=(每个instance日志组个数+1)*instance个数 例如在我的环境中，只有一个节点，这个节点有三组redo，所以 Standby redo log组数公式>=(3+1)*1 == 4 所以需要创建4组Standby redo log3).每一日志组为了安全起见，可以包含多个成员文件。查看主数据库的日志组个数与大小，创建standy日志组,大小不能小于在线日志大小。SQL> select member from v$logfile; MEMBER--------------------------------------------------------------------------------/u01/app/oracle/oradata/JASON/redo03.log/u01/app/oracle/oradata/JASON/redo02.log/u01/app/oracle/oradata/JASON/redo01.log 在主数据库创建standby日志组，位置与原日志组相同的路径。SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby01.log') SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/u01/app/oracle/oradata/JASON/standby02.log')SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby03.log') SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/u01/app/oracle/oradata/JASON/standby04.log')SIZE 50M; Database altered.SQL> select group#,status,type,member from v$logfile; GROUP# STATUS TYPE MEMBER------------------------------------------------------------------------------------------------------------------------------ 3 ONLINE /u01/app/oracle/oradata/JASON/redo03.log 2 ONLINE /u01/app/oracle/oradata/JASON/redo02.log 1 ONLINE /u01/app/oracle/oradata/JASON/redo01.log 4 STANDBY /u01/app/oracle/oradata/JASON/standby01.log 5 STANDBY/u01/app/oracle/oradata/JASON/standby02.log 6 STANDBY/u01/app/oracle/oradata/JASON/standby03.log 7 STANDBY/u01/app/oracle/oradata/JASON/standby04.log7 rows selected.5. 主库参数文件配置
在主库上修改dataguard配置相关的各个参数，各参数的具体含义可以参考oracle在线文档。SQL> alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(JASON1,JASON2)'SCOPE=SPFILE; System altered. SQL> alter system set DB_UNIQUE_NAME='JASON1' SCOPE=SPFILE; System altered. SQL> alter system set STANDBY_FILE_MANAGEMENT='AUTO' SCOPE=SPFILE; System altered. SQL> alter system setLOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/archivelog/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=JASON1' scope=spfile; System altered. SQL> alter system set LOG_ARCHIVE_DEST_2='SERVICE=JASON2 ASYNCVALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=JASON2' scope=spfile; System altered. SQL> alter system set LOG_ARCHIVE_DEST_STATE_1='ENABLE' scope=spfile; System altered. SQL> alter system set LOG_ARCHIVE_DEST_STATE_2='ENABLE' scope=spfile; System altered.SQL> alter system setLOG_FILE_NAME_CONVERT= '/u01/app/oracle/oradata/JASON','/u01/app/oracle/oradata/JASON' scope=spfile; System altered.SQL> alter system set FAL_SERVER='JASON2' scope=spfile; System altered. SQL> shutdown immediateDatabase closed.Database dismounted.ORACLE instance shut down.SQL> startupORACLE instance started. Total System Global Area 409194496 bytesFixed Size 2253744 bytesVariable Size 310381648 bytesDatabase Buffers 92274688 bytesRedo Buffers 4284416 bytesDatabase mounted.Database opened.6. 配置监听及tnsname
创建监听及tnsname.ora，监听必须使用静态监听，如下：[oracle@jason1 admin]$ cat listener.ora # listener.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora# Generated by Oracle configuration tools. SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = JASON1) (ORACLE_HOME =/u01/app/oracle/product/11.2.0/dbhome_1) (SID_NAME = JASON) ) ) LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.99)(PORT = 1521)) ) ADR_BASE_LISTENER = /u01/app/oracle [oracle@jason1 admin]$ cat tnsnames.ora # tnsnames.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora# Generated by Oracle configuration tools. JASON1 = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.99)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = JASON1) ) )JASON2 = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.100)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = JASON2) ) )[oracle@jason1 admin]$lsnrctl status LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 20-JUL-201623:06:17 Copyright (c) 1991, 2013, Oracle. All rights reserved. Connecting to(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=jason1)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNRfor Linux: Version 11.2.0.4.0 - ProductionStart Date 20-JUL-2016 22:50:04Uptime 0 days 0hr. 16 min. 13 secTrace Level offSecurity ON:Local OS AuthenticationSNMP OFFListener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.oraListener Log File /u01/app/oracle/diag/tnslsnr/jason1/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=jason1)(PORT=1521)))Services Summary...Service "JASON1" has 2 instance(s). Instance "JASON",status UNKNOWN, has 1 handler(s) for this service... Instance "JASON",status READY, has 1 handler(s) for this service...Service "JASONXDB" has 1 instance(s). Instance "JASON",status READY, has 1 handler(s) for this service...The command completed successfully[oracle@jason1 admin]$7. 生成pfile文件，同步相应文件至备库
在主数据库生成pfile文件。SQL> create pfile from spfile;File created.把dbs下的内容同步到standby主机上面，[oracle@jason1 dbs]$ pwd/u01/app/oracle/product/11.2.0/dbhome_1/dbs[oracle@jason1 dbs]$ scp initJASON.ora orapwJASON192.168.1.100:/u01/app/oracle/product/11.2.0/dbhome_1/dbs/The authenticity of host '192.168.1.100 (192.168.1.100)' can't beestablished.RSA key fingerprint is 25:ca:65:90:d3:30:fa:68:ed:11:64:b2:0e:b0:39:a7.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added '192.168.1.100' (RSA) to the list of knownhosts.oracle@192.168.1.100's password: initJASON.ora 100% 1415 1.4KB/s 00:00 orapwJASON 100% 1536 1.5KB/s 00:00 [oracle@jason1 dbs]三、 备库配置
8. 创建对应目录
备库上创建相关目录[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/admin/JASON/adump[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/admin/JASON/dpdump[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/admin/JASON/pfile[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/archivelog[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/oradata/JASON[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/fast_recovery_area[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/cfgtoollogs/catbundle[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/cfgtoollogs/dbca/JASON[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/cfgtoollogs/emca[oracle@jason2 oracle]$ mkdir -p /u01/app/oracle/cfgtoollogs/netca[oracle@jason2 oracle]$ lltotal 32drwxr-xr-x 3 oracle oinstall 4096Jul 14 22:27 admindrwxr-xr-x 2 oracle oinstall 4096Jul 14 22:28 archivelogdrwxr-xr-x 6 oracle oinstall 4096Jul 14 22:32 cfgtoollogsdrwxr-xr-x 2 oracle oinstall 4096Jul 13 23:32 checkpointsdrwxrwxr-x 11 oracle oinstall 4096 Jul 13 23:06 diagdrwxr-xr-x 2 oracle oinstall 4096Jul 14 22:30 fast_recovery_areadrwxr-xr-x 3 oracle oinstall 4096Jul 14 22:28 oradatadrwxr-xr-x 3 oracle oinstall 4096Jul 13 21:37 product[oracle@jason2 oracle]$9. 拷贝数据库备份
[oracle@jason2 oracle]#mkdir /data[oracle@jason2 oracle]#chownoracle:oinstall /data
在节点jason1上拷贝数据库备份至备机。
[oracle@jason1 data]$ scp * 192.168.1.100:/dataoracle@192.168.1.100's password: arch_01rbevvh_1_1.bak 100% 96MB 23.9MB/s 00:04 arch_04rbf01l_1_1.bak 100% 31KB 31.0KB/s 00:00 fulldb_02rbevvp_1_1.bak 100% 1035MB 16.4MB/s 01:03 fulldb_03rbf01i_1_1.bak 100%9600KB 9.4MB/s 00:00 [oracle@jason1 data]$
10.备库参数文件配置
备库上修改初始参数文件，配置DG所需参数如下。JASON.__db_cache_size=75497472JASON.__java_pool_size=4194304JASON.__large_pool_size=71303168JASON.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environmentJASON.__pga_aggregate_target=155189248JASON.__sga_target=255852544JASON.__shared_io_pool_size=0JASON.__shared_pool_size=96468992JASON.__streams_pool_size=0*.audit_file_dest='/u01/app/oracle/admin/JASON/adump'*.audit_trail='db'*.compatible='11.2.0.4.0'*.control_files='/u01/app/oracle/oradata/JASON/control01.ctl','/u01/app/oracle/oradata/JASON/control02.ctl','/u01/app/oracle/oradata/JASON/control03.ctl'*.db_block_size=8192*.db_domain=''*.db_name='JASON'*.db_recovery_file_dest_size=4385144832*.db_recovery_file_dest='/u01/app/oracle/fast_recovery_area'*.log_file_name_convert='/u01/app/oracle/oradata/JASON','/u01/app/oracle/oradata/JASON'*.db_unique_name='JASON2'*.diagnostic_dest='/u01/app/oracle'*.dispatchers='(PROTOCOL=TCP) (SERVICE=JASONXDB)'*.fal_server='JASON1'*.log_archive_config='DG_CONFIG=(JASON1,JASON2)'*.log_archive_dest_1='LOCATION=/u01/app/oracle/archivelog/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=JASON2'*.log_archive_dest_2='SERVICE=JASON1 ASYNCVALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=JASON1'*.log_archive_dest_state_1='ENABLE'*.log_archive_dest_state_2='ENABLE'*.log_archive_format='%t_%s_%r.dbf'*.memory_target=411041792*.open_cursors=300*.processes=150*.remote_login_passwordfile='EXCLUSIVE'*.standby_file_management='AUTO'*.undo_tablespace='UNDOTBS111.配置监听
备库监听必须设置为静态监听[oracle@jason2 admin]$ cat listener.ora # listener.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora# Generated by Oracle configuration tools. SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = JASON2) (ORACLE_HOME =/u01/app/oracle/product/11.2.0/dbhome_1) (SID_NAME = JASON) ) ) LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.100)(PORT = 1521)) ) ADR_BASE_LISTENER = /u01/app/oracle [oracle@jason2 admin]$ cat tnsnames.ora # tnsnames.ora Network Configuration File:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora# Generated by Oracle configuration tools. JASON1 = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.99)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = JASON1) ) )JASON2 = (DESCRIPTION = (ADDRESS = (PROTOCOL =TCP)(HOST = 192.168.1.100)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = JASON2) ) )
12.创建spfile文件
[oracle@jason2 dbs]$ sqlplus /nolog SQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 23:07:22 2016 Copyright (c) 1982, 2013, Oracle. All rights reserved. SQL> conn /as sysdbaConnected to an idle instance. SQL> startup nomountORACLE instance started. Total System Global Area 409194496 bytesFixed Size 2253744 bytesVariable Size 310381648 bytesDatabase Buffers 92274688bytesRedo Buffers 4284416 bytesSQL> create spfile from pfile; File created.13.创建备库
将备库启动到nomount状态，然后在备机连接主库进行duplicate操作。SQL> shutdown immediateORA-01507: database not mountedORACLE instance shut down.SQL> startup nomount;ORACLE instance started. Total System Global Area 409194496 bytesFixed Size 2253744 bytesVariable Size 310381648 bytesDatabase Buffers 92274688 bytesRedo Buffers 4284416 bytesSQL> exitDisconnected from Oracle Database 11g Enterprise Edition Release11.2.0.4.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testingoptions[oracle@jason2 ~]$lsnrctl status LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 20-JUL-2016 23:04:56 Copyright (c) 1991, 2013, Oracle. All rights reserved. Connecting to(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=jason2)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNRfor Linux: Version 11.2.0.4.0 - ProductionStart Date 20-JUL-2016 22:50:42Uptime 0 days 0hr. 14 min. 14 secTrace Level offSecurity ON:Local OS AuthenticationSNMP OFFListener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.oraListener Log File /u01/app/oracle/diag/tnslsnr/jason2/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=jason2)(PORT=1521)))Services Summary...Service "JASON2" has 2 instance(s). Instance "JASON",status UNKNOWN, has 1 handler(s) for this service... Instance "JASON",status BLOCKED, has 1 handler(s) for this service...The command completed successfully[oracle@jason2 ~]$ rman target sys/system@JASON1 auxiliarysys/system@JASON2 Recovery Manager: Release 11.2.0.4.0 - Production on Sat Jul 23 23:13:192016 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: JASON (DBID=2141348976)connected to auxiliary database: JASON (not mounted) RMAN> duplicate target database for standby nofilenamecheck; Starting Duplicate Db at 23-JUL-16using target database control file instead of recovery catalogallocated channel: ORA_AUX_DISK_1channel ORA_AUX_DISK_1: SID=18 device type=DISK contents of Memory Script:{ restore clone standbycontrolfile;}executing Memory Script Starting restore at 23-JUL-16using channel ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: starting datafile backup set restorechannel ORA_AUX_DISK_1: restoring control filechannel ORA_AUX_DISK_1: reading from backup piece/data/fulldb_03rbf01i_1_1.bakchannel ORA_AUX_DISK_1: piece handle=/data/fulldb_03rbf01i_1_1.baktag=TAG20160723T224513channel ORA_AUX_DISK_1: restored backup piece 1channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03output file name=/u01/app/oracle/oradata/JASON/control01.ctloutput file name=/u01/app/oracle/oradata/JASON/control02.ctloutput file name=/u01/app/oracle/oradata/JASON/control03.ctlFinished restore at 23-JUL-16 contents of Memory Script:{ sql clone 'alter database mountstandby database';}executing Memory Script sql statement: alter database mount standby database contents of Memory Script:{ set newname for tempfile 1 to "/u01/app/oracle/oradata/JASON/temp01.dbf"; switch clone tempfile all; set newname for datafile 1 to "/u01/app/oracle/oradata/JASON/system01.dbf"; set newname for datafile 2 to "/u01/app/oracle/oradata/JASON/sysaux01.dbf"; set newname for datafile 3 to "/u01/app/oracle/oradata/JASON/undotbs01.dbf"; set newname for datafile 4 to "/u01/app/oracle/oradata/JASON/users01.dbf"; restore clone database ;}executing Memory Script executing command: SET NEWNAME renamed tempfile 1 to /u01/app/oracle/oradata/JASON/temp01.dbf incontrol file executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME Starting restore at 23-JUL-16using channel ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: starting datafile backup set restorechannel ORA_AUX_DISK_1: specifying datafile(s) to restore from backupsetchannel ORA_AUX_DISK_1: restoring datafile 00001 to/u01/app/oracle/oradata/JASON/system01.dbfchannel ORA_AUX_DISK_1: restoring datafile 00002 to/u01/app/oracle/oradata/JASON/sysaux01.dbfchannel ORA_AUX_DISK_1: restoring datafile 00003 to/u01/app/oracle/oradata/JASON/undotbs01.dbfchannel ORA_AUX_DISK_1: restoring datafile 00004 to/u01/app/oracle/oradata/JASON/users01.dbfchannel ORA_AUX_DISK_1: reading from backup piece/data/fulldb_02rbevvp_1_1.bakchannel ORA_AUX_DISK_1: piece handle=/data/fulldb_02rbevvp_1_1.baktag=TAG20160723T224513channel ORA_AUX_DISK_1: restored backup piece 1channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:58Finished restore at 23-JUL-16 contents of Memory Script:{ switch clone datafile all;}executing Memory Script datafile 1 switched to datafile copyinput datafile copy RECID=1 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/system01.dbfdatafile 2 switched to datafile copyinput datafile copy RECID=2 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/sysaux01.dbfdatafile 3 switched to datafile copyinput datafile copy RECID=3 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/undotbs01.dbfdatafile 4 switched to datafile copyinput datafile copy RECID=4 STAMP=917998157 filename=/u01/app/oracle/oradata/JASON/users01.dbfFinished Duplicate Db at 23-JUL-16RMAN> exitRecovery Manager complete.[oracle@jason2 ~]$14.创建standby日志组
查看主数据库的日志组个数与大小，创建standy日志组,大小不能小于在线日志大小。SQL> select member from v$logfile; MEMBER--------------------------------------------------------------------------------/u01/app/oracle/oradata/JASON/redo03.log/u01/app/oracle/oradata/JASON/redo02.log/u01/app/oracle/oradata/JASON/redo01.log 在备数据库创建standby日志组，位置与原日志组相同的路径。SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby01.log') SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby02.log') SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby03.log') SIZE 50M; Database altered. SQL> ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby04.log') SIZE 50M; Database altered.SQL>备注：创建备库后，数据库处于mount状态，因使用未配置的主库创建备库，需创建standby日志组后，打开数据库。打开时将会初始化临时表空间、在线日志、standby日志,接收未传送的日志。15.开启ADG
将备库置于active dataguard模式下，数据库open时将会传送所有自备份后产生的归档日志至备机。[oracle@jason2 ~]$ sqlplus /nologSQL*Plus: Release 11.2.0.4.0 Production on Thu Jul 14 23:42:40 2016 Copyright (c) 1982, 2013, Oracle. All rights reserved. SQL> conn /as sysdbaConnected.SQL> alter database open; Database altered. SQL> alter database recover managed standby database using currentlogfile disconnect from session; Database altered. SQL> select open_mode,database_role,db_unique_name from v$database; OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME-------------------- ---------------- ------------------------------READ ONLY WITH APPLY PHYSICAL STANDBY JASON2 SQL> select protection_mode,protection_level from v$database; PROTECTION_MODE PROTECTION_LEVEL-------------------- --------------------MAXIMUM PERFORMANCE MAXIMUMPERFORMANCESQL> select status from v$standby_log; STATUS----------ACTIVEUNASSIGNEDUNASSIGNEDUNASSIGNEDSQL> select group#,status,type,member from v$logfile; GROUP# STATUS TYPE MEMBER------------------------------------------------------------------------------- 3 ONLINE /u01/app/oracle/oradata/JASON/redo03.log 2 ONLINE /u01/app/oracle/oradata/JASON/redo02.log 1 ONLINE /u01/app/oracle/oradata/JASON/redo01.log 4 STANDBY/u01/app/oracle/oradata/JASON/standby01.log 5 STANDBY/u01/app/oracle/oradata/JASON/standby02.log 6 STANDBY /u01/app/oracle/oradata/JASON/standby03.log 7 STANDBY/u01/app/oracle/oradata/JASON/standby04.log 7 rows selected.SQL>查看备库数据文件，如下：[root@jason2 JASON]# lltotal 1744852-rw-r----- 1 oracle oinstall 9748480 Jul 21 00:11 control01.ctl-rw-r----- 1 oracle oinstall 9748480 Jul 21 00:11 control02.ctl-rw-r----- 1 oracle oinstall 9748480 Jul 21 00:11 control03.ctl-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:06 redo01.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:06 redo02.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:06 redo03.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:11 standby01.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:09 standby02.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:07 standby03.log-rw-r----- 1 oracle oinstall 52429312 Jul 21 00:07 standby04.log-rw-r----- 1 oracle oinstall 534781952 Jul 21 00:09 sysaux01.dbf-rw-r----- 1 oracle oinstall 775954432 Jul 21 00:09 system01.dbf-rw-r----- 1 oracle oinstall 30416896 Jul 21 00:09 temp01.dbf-rw-r----- 1 oracle oinstall 73408512 Jul 21 00:09 undotbs01.dbf-rw-r----- 1 oracle oinstall 5251072 Jul 21 00:09 users01.dbf[root@jason2 JASON]#主库查看数据库状态SQL> select open_mode,database_role,db_unique_name from v$database; OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME-------------------- ---------------- ------------------------------READ WRITE PRIMARY JASON1 SQL> select protection_mode,protection_level from v$database; PROTECTION_MODE PROTECTION_LEVEL-------------------- --------------------MAXIMUM PERFORMANCE MAXIMUMPERFORMANCE四、 测试
16.switch_over测试
主库切换SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
--------------------
TO STANDBY
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBYWITH SESSION SHUTDOWN;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SELECT SWITCHOVER_STATUS FROM V$DATABASE
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 2849
Session ID: 44 Serial number: 27
SQL> startup
ORACLE instance started.
Total System Global Area 409194496 bytes
Fixed Size 2253744 bytes
Variable Size 322964560 bytes
Database Buffers 79691776 bytes
Redo Buffers 4284416 bytes
Database mounted.
Database opened.
SQL> select open_mode,database_role,db_unique_name fromv$database;
OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME
-------------------- ----------------------------------------------
READ ONLY PHYSICAL STANDBY JASON1
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USINGCURRENT LOGFILE DISCONNECT FROM SESSION;
Database altered.
SQL>
备库切换
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
--------------------
TO PRIMARY
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITHSESSION SHUTDOWN;
Database altered.
SQL> select open_mode,database_role,db_unique_name fromv$database;
OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME
-------------------- ---------------- ------------------------------
MOUNTED PRIMARY JASON2
SQL> alter database open;
Database altered.
SQL> select open_mode,database_role,db_unique_name fromv$database;
OPEN_MODE DATABASE_ROLE DB_UNIQUE_NAME
-------------------- ----------------------------------------------
READ WRITE PRIMARY JASON2
SQL>
五、 报错处理
17. 报错
在备库服务器, 添加静态注册信息到 $GRID_HOME/network/listener.ora文件，这主要是由于AUXILIARY实例启动到nomount状态时，listener无法注册AUXILIARY实例，listener会标志Auxiliary实例为'blocked'状态，因此duplicate命令就无法通过TNS的方式连接到Auxiliary实例，为了解决这个问题，需要先手动静态注册数据库实例到listener上。当Data Guard配置完成后，就可以删除静态注册的配置信息[oracle@jason2 dbs]$ rman target sys/system@JASON_PD auxiliarysys/system@JASON_SD Recovery Manager: Release 11.2.0.4.0 - Production on Thu Jul 14 23:15:312016 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: JASON (DBID=2141348976)RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-00554: initialization of internal recovery manager package failedRMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: allappropriate instances are blocking new connections设置静态监听后状态[oracle@jason2 dbs]$ lsnrctl status LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 14-JUL-201623:15:50 Copyright (c) 1991, 2013, Oracle. All rights reserved. Connecting to(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.100)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNRfor Linux: Version 11.2.0.4.0 - ProductionStart Date 14-JUL-2016 22:41:05Uptime 0 days 0hr. 34 min. 44 secTrace Level offSecurity ON:Local OS AuthenticationSNMP OFFListener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.oraListener Log File /u01/app/oracle/diag/tnslsnr/jason2/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.100)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))Services Summary...Service "JASON2" has 1 instance(s). Instance "JASON",status BLOCKED, has 1 handler(s) for this service...The command completed successfully[oracle@jason2 dbs]$六、 创建备库时主备库变化
本次实验中使用主库未配置前的rman备份进行创建DG。模拟备份为前一天的备份。数据库备份结束日志序号为17.然后通过手工切换模拟备份后一天产生的归档日志，最终日志序号为54。以下为主库日志查询结果。SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BYSEQUENCE#;SEQUENCE# APPLIED
---------- ---------
7 NO
8 NO
9 NO
10 NO
11 NO
12 NO
13 NO
14 NO
15 NO
16 NO
17 NO
SEQUENCE# APPLIED
---------- ---------
18 NO
19 NO
20 NO
21 NO
22 NO
23 NO
24 NO
25 NO
26 NO
27 NO
28 NO
SEQUENCE# APPLIED
---------- ---------
29 NO
30 NO
31 NO
32 NO
33 NO
34 NO
35 NO
36 NO
37 NO
38 NO
39 NO
SEQUENCE# APPLIED
---------- ---------
40 NO
41 NO
42 NO
43 NO
44 NO
45 NO
46 NO
47 NO
48 NO
49 NO
50 NO
SEQUENCE# APPLIED
---------- ---------
51 NO
52 NO
53 NO
54 NO
48 rows selected.
SQL>
在主库传送rman备份至备库中，备份位置必须与主库相同。然后在备库进行恢复数据库。恢复结束后，在备库创建standby日志组，创建结束后执行alter database open命令打开备库。这时从备库日志中可以发现在备库打开时，自备份结束后产生的所有归档日志文件(归档日志必须保证存在)自动传送到备库中。这时再主库再次查看日志会发现日志中显示归档日志已传送，但未应用。如下为日志变化过程：
SQL> /
SEQUENCE# APPLIED
---------- ---------
7 NO
8 NO
9 NO
10 NO
11 NO
12 NO
13 NO
14 NO
15 NO
16 NO
17 NO
SEQUENCE# APPLIED
---------- ---------
17 NO
18 NO
18 NO
19 NO
19 NO
20 NO
20 NO
21 NO
21 NO
22 NO
22 NO
SEQUENCE# APPLIED
---------- ---------
23 NO
23 NO
24 NO
24 NO
25 NO
25 NO
26 NO
26 NO
27 NO
27 NO
28 NO
SEQUENCE# APPLIED
---------- ---------
28 NO
29 NO
29 NO
30 NO
30 NO
31 NO
31 NO
32 NO
32 NO
33 NO
33 NO
SEQUENCE# APPLIED
---------- ---------
34 NO
34 NO
35 NO
35 NO
36 NO
36 NO
37 NO
37 NO
38 NO
38 NO
39 NO
SEQUENCE# APPLIED
---------- ---------
39 NO
40 NO
40 NO
41 NO
41 NO
42 NO
42 NO
43 NO
43 NO
44 NO
44 NO
SEQUENCE# APPLIED
---------- ---------
45 NO
45 NO
46 NO
46 NO
47 NO
47 NO
48 NO
48 NO
49 NO
49 NO
50 NO
SEQUENCE# APPLIED
---------- ---------
50 NO
51 NO
51 NO
52 NO
52 NO
53 NO
53 NO
54 NO
54 NO
55 NO
55 NO
SEQUENCE# APPLIED
---------- ---------
56 NO
56 NO
90 rows selected.
SQL>
接着在备库开启日志实时应用，执行alter database recover managed standby database using current logfiledisconnect from session;该命令执行时，在备库日志中可以发现MRP0开始应用所有归档日志进行数据恢复，直到最新日志。具体变化可以查看如下主库与备库的日志。
备注：也可以在数据库处于挂载状态下执行日志恢复，追平并应用日志之后再打开数据库。
ALTERDATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROMSESSION;alterdatabase recover managed standby database cancel;alterdatabase openALTERDATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROMSESSION;
主库日志[root@jason1 trace]# tail -f alert_JASON.log Sat Jul 23 23:27:56 2016PING[ARC2]: Heartbeat failed to connect to standby 'JASON2'. Error is16058.Sat Jul 23 23:28:31 2016Using STANDBY_ARCHIVE_DEST parameter default value as/u01/app/oracle/archivelog/ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*';Sat Jul 23 23:28:31 2016PING[ARC2]: Heartbeat failed to connect to standby 'JASON2'. Error is16058.Sat Jul 23 23:28:36 2016Thread 1 advanced to log sequence 56 (LGWR switch) Current log# 2 seq# 56 mem# 0:/u01/app/oracle/oradata/JASON/redo02.logSat Jul 23 23:28:36 2016Archived Log entry 52 added for thread 1 sequence 55 ID 0x7fa28a70 dest1:Sat Jul 23 23:31:57 2016ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*';Sat Jul 23 23:31:58 2016ARC3: Archive log rejected (thread 1 sequence 17) at host 'JASON2'FAL[server, ARC3]: FAL archive failed, see trace file.ARCH: FAL archive failed. Archiver continuingORACLE Instance JASON - Archival Error. Archiver continuing.Sat Jul 23 23:32:00 2016Thread 1 advanced to log sequence 57 (LGWR switch) Current log# 3 seq# 57 mem# 0:/u01/app/oracle/oradata/JASON/redo03.logSat Jul 23 23:32:00 2016******************************************************************LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2******************************************************************LNS: Standby redo logfile selected for thread 1 sequence 57 fordestination LOG_ARCHIVE_DEST_2Sat Jul 23 23:32:01 2016Expanded controlfile section 11 from 66 to 153 recordsRequested to grow by 87 records; added 3 blocks of recordsSat Jul 23 23:32:01 2016Archived Log entry 73 added for thread 1 sequence 56 ID 0x7fa28a70 dest1:备库日志[root@jason2 trace]# tail -f alert_JASON.log Sat Jul 23 23:11:43 2016Using STANDBY_ARCHIVE_DEST parameter default value as /u01/app/oracle/archivelog/Sat Jul 23 23:27:44 2016destination database instance is 'started' not 'mounted'Sat Jul 23 23:28:08 2016Conversion to standby controlfile pending for restored fileNo controlfile conversionSat Jul 23 23:28:11 2016RFS connections have been disallowedalter database mount standby databaseConverting controlfile to standbyIf db_file_name_convert or log_file_name_convert parametersare not used, then RMAN intervention is required to fix thefile names in the converted control file. Refer to RMANdocumentation for how to fix all file names.Clearing standby activation ID 2141358704 (0x7fa28a70)The primary database controlfile was created using the'MAXLOGFILES 16' clause.There is space for up to 13 standby redo logfilesUse the following SQL commands on the standby database to createstandby 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;Set as converted control file due to db_unique_name mismatchChanging di2dbun from JASON1 to JASON2ARCH: STARTING ARCH PROCESSESSat Jul 23 23:28:16 2016ARC0 started with pid=22, OS id=2774 ARC0: Archival startedARCH: STARTING ARCH PROCESSES COMPLETEARC0: STARTING ARCH PROCESSESSat Jul 23 23:28:17 2016Successful mount of redo thread 1, with mount id 2142218252Physical Standby Database mounted.Lost write protection disabledSat Jul 23 23:28:17 2016ARC1 started with pid=23, OS id=2776 Sat Jul 23 23:28:17 2016ARC2 started with pid=24, OS id=2778 ARC1: Archival startedARC2: Archival startedARC1: Becoming the 'no FAL' ARCHARC2: Becoming the heartbeat ARCHARC2: Becoming the active heartbeat ARCHSat Jul 23 23:28:17 2016ARC3 started with pid=25, OS id=2780 Completed: alter database mount standby databaseARC3: Archival startedARC0: STARTING ARCH PROCESSES COMPLETESat Jul 23 23:28:19 2016Full restore complete of datafile 4/u01/app/oracle/oradata/JASON/users01.dbf. Elapsed time: 0:00:00 checkpoint is 1024819 last deallocation scn is 3Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_lgwr_2557.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/JASON/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Sat Jul 23 23:28:24 2016Warning: VKTM detected a time drift.Time drifts can result in an unexpected behavior such as time-outs.Please check trace file for more details.Full restore complete of datafile 3/u01/app/oracle/oradata/JASON/undotbs01.dbf. Elapsed time: 0:00:02 checkpoint is 1024819 last deallocation scn is 968786 Undo Optimization current scn is967371Sat Jul 23 23:28:59 2016Full restore complete of datafile 2/u01/app/oracle/oradata/JASON/sysaux01.dbf. Elapsed time: 0:00:38 checkpoint is 1024819 last deallocation scn is 964749Sat Jul 23 23:29:11 2016Full restore complete of datafile 1/u01/app/oracle/oradata/JASON/system01.dbf. Elapsed time: 0:00:49 checkpoint is 1024819 last deallocation scn is 963928 Undo Optimization current scn is967371Sat Jul 23 23:29:17 2016Switch of datafile 1 complete to datafile copy checkpoint is 1024819Switch of datafile 2 complete to datafile copy checkpoint is 1024819Switch of datafile 3 complete to datafile copy checkpoint is 1024819Switch of datafile 4 complete to datafile copy checkpoint is 1024819alter database clear logfile group 1Clearing online log 1 of thread 1 sequence number 16Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 1 of thread 1ORA-00312: online log 1 thread 1:'/u01/app/oracle/oradata/JASON/redo01.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Completed: alter database clear logfile group 1alter database clear logfile group 2Clearing online log 2 of thread 1 sequence number 17Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 2 of thread 1ORA-00312: online log 2 thread 1:'/u01/app/oracle/oradata/JASON/redo02.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Completed: alter database clear logfile group 2alter database clear logfile group 3Clearing online log 3 of thread 1 sequence number 15Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1:'/u01/app/oracle/oradata/JASON/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/jason2/JASON/trace/JASON_ora_2710.trc:ORA-00313: open failed for members of log group 3 of thread 1ORA-00312: online log 3 thread 1:'/u01/app/oracle/oradata/JASON/redo03.log'ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directoryAdditional information: 3Completed: alter database clear logfile group 3RFS connections are allowedSat Jul 23 23:30:29 2016ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby01.log') SIZE 50MCompleted: ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby01.log') SIZE 50MSat Jul 23 23:30:48 2016ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby02.log') SIZE 50MCompleted: ALTER DATABASE ADD STANDBY LOGFILE ('/u01/app/oracle/oradata/JASON/standby02.log')SIZE 50MSat Jul 23 23:31:02 2016ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby03.log') SIZE 50MCompleted: ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby03.log') SIZE 50MSat Jul 23 23:31:17 2016ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby04.log') SIZE 50MCompleted: ALTER DATABASE ADD STANDBY LOGFILE('/u01/app/oracle/oradata/JASON/standby04.log') SIZE 50MSat Jul 23 23:31:45 2016alter database openAUDIT_TRAIL initialization parameter is changed to OS, as DB is NOTcompatible for database opened with read-only accessSignalling error 1152 for datafile 1!Beginning Standby Crash Recovery.Serial Media Recovery startedManaged Standby Recovery starting Real Time ApplyMedia Recovery Waiting for thread 1 sequence 17Sat Jul 23 23:31:45 2016RFS[1]: Assigned to RFS process 2810RFS[1]: Opened log for thread 1 sequence 17 dbid 2141348976 branch917134706Archived Log entry 1 added for thread 1 sequence 17 rlc 917134706 ID0x7fa28a70 dest 2:Media Recovery Log /u01/app/oracle/archivelog/1_17_917134706.dbfIncomplete Recovery applied until change 1024865 time 07/23/201622:46:10Completed Standby Crash Recovery.Sat Jul 23 23:31:46 2016SMON: enabling cache recoverySat Jul 23 23:31:47 2016RFS[2]: Assigned to RFS process 2808RFS[2]: Opened log for thread 1 sequence 19 dbid 2141348976 branch917134706RFS[1]: Opened log for thread 1 sequence 20 dbid 2141348976 branch917134706Archived Log entry 2 added for thread 1 sequence 19 rlc 917134706 ID0x7fa28a70 dest 2:Sat Jul 23 23:31:47 2016RFS[3]: Assigned to RFS process 2812RFS[3]: Opened log for thread 1 sequence 18 dbid 2141348976 branch917134706Archived Log entry 3 added for thread 1 sequence 20 rlc 917134706 ID0x7fa28a70 dest 2:RFS[2]: Opened log for thread 1 sequence 21 dbid 2141348976 branch917134706RFS[1]: Opened log for thread 1 sequence 22 dbid 2141348976 branch917134706Archived Log entry 4 added for thread 1 sequence 22 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 5 added for thread 1 sequence 21 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 6 added for thread 1 sequence 18 rlc 917134706 ID0x7fa28a70 dest 2:RFS[1]: Opened log for thread 1 sequence 23 dbid 2141348976 branch917134706RFS[2]: Opened log for thread 1 sequence 25 dbid 2141348976 branch917134706Archived Log entry 7 added for thread 1 sequence 23 rlc 917134706 ID0x7fa28a70 dest 2:RFS[3]: Opened log for thread 1 sequence 24 dbid 2141348976 branch917134706Archived Log entry 8 added for thread 1 sequence 25 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 9 added for thread 1 sequence 24 rlc 917134706 ID0x7fa28a70 dest 2:RFS[1]: Opened log for thread 1 sequence 26 dbid 2141348976 branch917134706RFS[3]: Opened log for thread 1 sequence 27 dbid 2141348976 branch917134706Archived Log entry 10 added for thread 1 sequence 26 rlc 917134706 ID0x7fa28a70 dest 2:RFS[2]: Opened log for thread 1 sequence 28 dbid 2141348976 branch917134706Archived Log entry 11 added for thread 1 sequence 27 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 12 added for thread 1 sequence 28 rlc 917134706 ID0x7fa28a70 dest 2:RFS[1]: Opened log for thread 1 sequence 29 dbid 2141348976 branch917134706RFS[3]: Opened log for thread 1 sequence 30 dbid 2141348976 branch917134706Archived Log entry 13 added for thread 1 sequence 29 rlc 917134706 ID0x7fa28a70 dest 2:RFS[2]: Opened log for thread 1 sequence 31 dbid 2141348976 branch917134706Archived Log entry 14 added for thread 1 sequence 30 rlc 917134706 ID0x7fa28a70 dest 2:RFS[1]: Opened log for thread 1 sequence 32 dbid 2141348976 branch917134706Archived Log entry 15 added for thread 1 sequence 31 rlc 917134706 ID0x7fa28a70 dest 2:RFS[3]: Opened log for thread 1 sequence 33 dbid 2141348976 branch917134706Archived Log entry 16 added for thread 1 sequence 32 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 17 added for thread 1 sequence 33 rlc 917134706 ID0x7fa28a70 dest 2:RFS[2]: Opened log for thread 1 sequence 34 dbid 2141348976 branch917134706RFS[1]: Opened log for thread 1 sequence 35 dbid 2141348976 branch917134706Archived Log entry 18 added for thread 1 sequence 34 rlc 917134706 ID0x7fa28a70 dest 2:RFS[3]: Opened log for thread 1 sequence 36 dbid 2141348976 branch917134706Archived Log entry 19 added for thread 1 sequence 35 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 20 added for thread 1 sequence 36 rlc 917134706 ID0x7fa28a70 dest 2:Sat Jul 23 23:31:48 2016Primary database is in MAXIMUM PERFORMANCE modeRFS[4]: Assigned to RFS process 2814RFS[4]: Selected log 4 for thread 1 sequence 57 dbid 2141348976 branch917134706Sat Jul 23 23:31:50 2016RFS[5]: Assigned to RFS process 2816RFS[5]: Opened log for thread 1 sequence 38 dbid 2141348976 branch917134706Sat Jul 23 23:31:50 2016RFS[6]: Assigned to RFS process 2820RFS[6]: Opened log for thread 1 sequence 39 dbid 2141348976 branch917134706Archived Log entry 21 added for thread 1 sequence 38 rlc 917134706 ID0x7fa28a70 dest 2:Sat Jul 23 23:31:50 2016RFS[7]: Assigned to RFS process 2818RFS[7]: Opened log for thread 1 sequence 37 dbid 2141348976 branch917134706Archived Log entry 22 added for thread 1 sequence 39 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 23 added for thread 1 sequence 37 rlc 917134706 ID0x7fa28a70 dest 2:RFS[5]: Opened log for thread 1 sequence 40 dbid 2141348976 branch917134706Dictionary check beginningRFS[6]: Opened log for thread 1 sequence 41 dbid 2141348976 branch917134706Archived Log entry 24 added for thread 1 sequence 40 rlc 917134706 ID0x7fa28a70 dest 2:RFS[7]: Opened log for thread 1 sequence 42 dbid 2141348976 branch917134706Archived Log entry 25 added for thread 1 sequence 41 rlc 917134706 ID0x7fa28a70 dest 2:RFS[5]: Opened log for thread 1 sequence 43 dbid 2141348976 branch917134706Archived Log entry 26 added for thread 1 sequence 42 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 27 added for thread 1 sequence 43 rlc 917134706 ID0x7fa28a70 dest 2:RFS[6]: Opened log for thread 1 sequence 44 dbid 2141348976 branch917134706RFS[7]: Opened log for thread 1 sequence 45 dbid 2141348976 branch917134706RFS[5]: Opened log for thread 1 sequence 46 dbid 2141348976 branch917134706Archived Log entry 28 added for thread 1 sequence 44 rlc 917134706 ID0x7fa28a70 dest 2:Expanded controlfile section 11 from 28 to 280 recordsRequested to grow by 252 records; added 9 blocks of recordsArchived Log entry 29 added for thread 1 sequence 45 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 30 added for thread 1 sequence 46 rlc 917134706 ID0x7fa28a70 dest 2:RFS[6]: Opened log for thread 1 sequence 47 dbid 2141348976 branch917134706RFS[7]: Opened log for thread 1 sequence 48 dbid 2141348976 branch917134706Archived Log entry 31 added for thread 1 sequence 47 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 32 added for thread 1 sequence 48 rlc 917134706 ID0x7fa28a70 dest 2:RFS[5]: Opened log for thread 1 sequence 49 dbid 2141348976 branch917134706Sat Jul 23 23:31:52 2016Errors in file/u01/app/oracle/diag/rdbms/jason2/JASON/trace/JASON_dbw0_2555.trc:ORA-01157: cannot identify/lock data file 201 - see DBWR trace fileORA-01110: data file 201: '/u01/app/oracle/oradata/JASON/temp01.dbf'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/jason2/JASON/trace/JASON_dbw0_2555.trc:ORA-01186: file 201 failed verification testsORA-01157: cannot identify/lock data file 201 - see DBWR trace fileORA-01110: data file 201: '/u01/app/oracle/oradata/JASON/temp01.dbf'File 201 not verified due to error ORA-01157Archived Log entry 33 added for thread 1 sequence 49 rlc 917134706 ID0x7fa28a70 dest 2:Dictionary check completeRe-creating tempfile /u01/app/oracle/oradata/JASON/temp01.dbfRFS[6]: Opened log for thread 1 sequence 50 dbid 2141348976 branch917134706Archived Log entry 34 added for thread 1 sequence 50 rlc 917134706 ID0x7fa28a70 dest 2:Database Characterset is ZHS16GBKRFS[6]: Opened log for thread 1 sequence 53 dbid 2141348976 branch917134706Archived Log entry 35 added for thread 1 sequence 53 rlc 917134706 ID0x7fa28a70 dest 2:RFS[7]: Opened log for thread 1 sequence 51 dbid 2141348976 branch917134706Archived Log entry 36 added for thread 1 sequence 51 rlc 917134706 ID0x7fa28a70 dest 2:RFS[6]: Opened log for thread 1 sequence 54 dbid 2141348976 branch917134706RFS[5]: Opened log for thread 1 sequence 52 dbid 2141348976 branch917134706Archived Log entry 37 added for thread 1 sequence 54 rlc 917134706 ID0x7fa28a70 dest 2:RFS[7]: Opened log for thread 1 sequence 55 dbid 2141348976 branch917134706Archived Log entry 38 added for thread 1 sequence 52 rlc 917134706 ID0x7fa28a70 dest 2:Archived Log entry 39 added for thread 1 sequence 55 rlc 917134706 ID0x7fa28a70 dest 2:RFS[6]: Opened log for thread 1 sequence 56 dbid 2141348976 branch917134706Archived Log entry 40 added for thread 1 sequence 56 rlc 917134706 ID0x7fa28a70 dest 2:Sat Jul 23 23:31:56 2016No Resource Manager plan active**********************************************************WARNING: Files may exists in db_recovery_file_destthat are not known to the database. Use the RMAN commandCATALOG RECOVERY AREA to re-catalog any such files.If files cannot be cataloged, then manually delete themusing OS command.One of the following events caused this:1. A backup controlfile was restored.2. A standby controlfile was restored.3. The controlfile was re-created.4. db_recovery_file_dest had previously been enabled and then disabled.**********************************************************replication_dependency_tracking turned off (no async multimasterreplication found)Physical standby database opened for read only access.Sat Jul 23 23:32:01 2016db_recovery_file_dest_size of 4182 MB is 0.00% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.Completed: alter database openSat Jul 23 23:32:25 2016alter database recover managed standby database using current logfiledisconnect from sessionAttempt to start background Managed Standby Recovery process (JASON)Sat Jul 23 23:32:25 2016MRP0 started with pid=28, OS id=2824 MRP0: Background Managed Standby Recovery process started (JASON)Serial Media Recovery startedManaged Standby Recovery starting Real Time ApplyWaiting for all non-current ORLs to be archived...All non-current ORLs have been archived.Media Recovery Log /u01/app/oracle/archivelog/1_17_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_18_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_19_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_20_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_21_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_22_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_23_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_24_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_25_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_26_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_27_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_28_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_29_917134706.dbfCompleted: alter database recover managed standby database using currentlogfile disconnect from sessionMedia Recovery Log /u01/app/oracle/archivelog/1_30_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_31_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_32_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_33_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_34_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_35_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_36_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_37_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_38_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_39_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_40_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_41_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_42_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_43_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_44_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_45_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_46_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_47_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_48_917134706.dbfSat Jul 23 23:32:35 2016Media Recovery Log /u01/app/oracle/archivelog/1_49_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_50_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_51_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_52_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_53_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_54_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_55_917134706.dbfMedia Recovery Log /u01/app/oracle/archivelog/1_56_917134706.dbfMedia Recovery Waiting for thread 1 sequence 57 (in transit)Recovery of Online Redo Log: Thread 1 Group 4 Seq 57 Reading mem 0 Mem# 0:/u01/app/oracle/oradata/JASON/standby01.log 备注：11g数据库如果不开启ADG，那么备库mount状态时，开启日志实时应用alter database recovermanaged standby database using current logfile disconnect from session时。未传送的归档日志在开启日志实时应用时，开始传送，传送结束后开始应用日志。
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- 使用RMAN备份System Parameter File
- rman在nfs文件系统上备份报错（NFS file system where the file is created or resides is not mounted with correct ）
- Rman配置DataGuard using Backup-based duplication with a target connection with filesystem
- linux下dataguard使用rman备份
- oracle11g dataguard主库备份恢复到测试环境单库报错：ORA-19502: write error on file
- 使用rman nocatalog方式备份Oracle - NetBackup配置方法
- 本文介绍使用RMAN备份创建备库(dataguard)（摘自http://database.ctocio.com.cn/77/9061577.shtml）
- NFS（Network File System）服务配置和使用
- 将Oracle数据库改为归档模式并启用RMAN备份 如下Linux环境下对Oracle单节点数据库采用文件系统情况的配置归档模式过程。首先查看数据库归档模式和磁盘使用情况，确定归档文件放到什么位置。
- 使用RMAN备份控制文件(control file)和系统参数文件(spfile)
- 无法读取 System Overview 日志或警报配置的 Log File Folder 数值。 将使用默认数值
- 使用rman nocatalog方式备份Oracle - NetBackup配置方法
- 使用Rman配置自动增量备份
- 使用FileSystemWatcher时应注意的两个小问题
- ORACLE RMAN备份的脚本配置
- Accessing the Local File System with Flex
- [realsy原创]如何配置和使用Remote Debugging with Visual Studio 2005
- rman的配置，使用catalog
- Working With The File System & Streams (4)
- (原創) 如何在Nios II使用Zip File System? (IC Design) (Nios II) (DE2)