最近為了不影響開發庫的使用，打算復制創建一個備庫，定時更新，防止開發庫不能使用的情況下，可以臨時使用備庫，不影響進度。
環境：
11.2.0.4的單實例庫。
庫1是源庫(target)，庫2是備庫(auxiliary)
操作過程：
1.庫1執行全庫備份
[oracle@testvm002 duplicate]$ rman target /
Recovery Manager: Release 11.2.0.4.0 - Production on Mon Feb 1 16:57:06 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: DEP (DBID=1501218369)
RMAN> run{
2> allocate channel dup type disk;
3> backup format '/home/oracle/duplicate/df_t%t_s%s_p%p' database;
4> sql 'alter system archive log current';
5> backup format '/home/oracle/duplicate/al_t%t_s%s_p%p' archivelog all delete input;
6> release channel dup;
7> }
using target database control file instead of recovery catalog
allocated channel: dup
channel dup: SID=24 device type=DISK
Starting backup at 01-FEB-16
channel dup: starting full datafile backup set
channel dup: specifying datafile(s) in backup set
input datafile file number=00002 name=/u01/app/oracle/11.2.0.4/oradata/dep/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/11.2.0.4/oradata/dep/dep_tbs01.dbf
input datafile file number=00001 name=/u01/app/oracle/11.2.0.4/oradata/dep/system01.dbf
input datafile file number=00003 name=/u01/app/oracle/11.2.0.4/oradata/dep/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/11.2.0.4/oradata/dep/users01.dbf
channel dup: starting piece 1 at 01-FEB-16
channel dup: finished piece 1 at 01-FEB-16
piece handle=/home/oracle/duplicate/df_t902681834_s10_p1 tag=TAG20160201T165714 comment=NONE
channel dup: backup set complete, elapsed time: 00:00:36
channel dup: starting full datafile backup set
channel dup: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel dup: starting piece 1 at 01-FEB-16
channel dup: finished piece 1 at 01-FEB-16
piece handle=/home/oracle/duplicate/df_t902681870_s11_p1 tag=TAG20160201T165714 comment=NONE
channel dup: backup set complete, elapsed time: 00:00:01
Finished backup at 01-FEB-16
sql statement: alter system archive log current
Starting backup at 01-FEB-16
current log archived
channel dup: starting archived log backup set
channel dup: specifying archived log(s) in backup set
input archived log thread=1 sequence=743 RECID=13 STAMP=902681873
input archived log thread=1 sequence=744 RECID=14 STAMP=902681874
channel dup: starting piece 1 at 01-FEB-16
channel dup: finished piece 1 at 01-FEB-16
piece handle=/home/oracle/duplicate/al_t902681874_s12_p1 tag=TAG20160201T165754 comment=NONE
channel dup: backup set complete, elapsed time: 00:00:01
channel dup: deleting archived log(s)
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_743_cby7jklq_.arc RECID=13 STAMP=902681873
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_744_cby7jl4s_.arc RECID=14 STAMP=902681874
Finished backup at 01-FEB-16
released channel: dup
2.庫1備份控制文件
SQL> alter database backup controlfile to '/home/oracle/duplicate/control.ctl';
Database altered.
3.將備份集(1)拷貝到庫2相同路徑下，即/home/oracle/duplicate，此時產生了三個文件：
al_t902681874_s12_p1
df_t902681834_s10_p1
df_t902681870_s11_p1
4.將庫1的inittest.ora參數文件拷貝到庫2，並按照其中配置的控制文件路徑，將庫1的控制文件(2)可以直接copy到庫2對應路徑下，包括文件名需要保持和參數文件總定義一致：
*.control_files='/u01/app/oracle/11.2.0.4/oradata/test/control01.ctl','/u01/app/oracle/11.2.0.4/fast_recovery_area/test/control02.ctl'
創建文件夾：
/u01/app/oracle/11.2.0.4/oradata/test
/u01/app/oracle/11.2.0.4/fast_recovery_area/test
/u01/app/oracle/11.2.0.4/admin/adump(/bdump/cdump/dpdump/udump)
5.庫2啟動nomount狀態
SQL> startup nomount pfile='/u01/app/oracle/11.2.0.4/dbhome_1/dbs/initdep.ora';
ORACLE instance started.
Total System Global Area 1620115456 bytes
Fixed Size 2253704 bytes
Variable Size 922750072 bytes
Database Buffers 687865856 bytes
Redo Buffers 7245824 bytes
6.庫2執行恢復
[oracle@testvm001 dbs]$ rman target /
Recovery Manager: Release 11.2.0.4.0 - Production on Mon Feb 1 17:10:21 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: DEP (not mounted)
RMAN> restore database;
Starting restore at 01-FEB-16
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=10 device type=DISK
RMAN-00571: ==================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ======
RMAN-00571: ==================================================
RMAN-03002: failure of restore command at 02/01/2016 17:10:28
ORA-01507: database not mounted
報錯提示數據庫需要置為mount狀態。
7.庫2置為mount狀態
SQL> alter database mount;
Database altered.
8.庫2執行恢復
RMAN> restore database;
Starting restore at 01-FEB-16
released channel: ORA_DISK_1
Starting implicit crosscheck backup at 01-FEB-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=10 device type=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 01-FEB-16
Starting implicit crosscheck copy at 01-FEB-16
using channel ORA_DISK_1
Crosschecked 6 objects
Finished implicit crosscheck copy at 01-FEB-16
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/11.2.0.4/oradata/dep/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/11.2.0.4/oradata/dep/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/11.2.0.4/oradata/dep/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/11.2.0.4/oradata/dep/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/11.2.0.4/oradata/dep/dep_tbs01.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/duplicate/df_t902681834_s10_p1
channel ORA_DISK_1: piece handle=/home/oracle/duplicate/df_t902681834_s10_p1 tag=TAG20160201T165714
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
Finished restore at 01-FEB-16
9.庫2執行打開
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
報錯提示需要使用RESETLOGS或NORESETLOGS。
10.庫2執行打開
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/11.2.0.4/oradata/dep/system01.dbf'
依舊報錯，提示：
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: ‘/u01/app/oracle/11.2.0.4/oradata/dep/system01.dbf’
查看這兩個報錯：
[oracle@testvm001 dbs]$ oerr ora 1152 01152, 00000, “file %s was
not restored from a sufficiently old backup ”
*Cause: An incomplete recovery session was started, but an
insufficient number of logs were applied to make the database
consistent. This file is still in the future of the last log applied.
The most likely cause of this error is forgetting to restore the file
from a backup before doing incomplete recovery.
*Action: Either apply more logs until the database is consistent or > restore the database file from an older backup and repeat
recovery.
[oracle@testvm001 dbs]$ oerr ora 1110 01110, 00000, “data file %s: ‘%s’”
*Cause: Reporting file name for details of another error.
The reported name can be of the old file if a data file
move operation is in progress.
*Action: See associated error message.
11.庫2執行recover
RMAN> recover database;
Starting recover at 01-FEB-16
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=743
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=744
channel ORA_DISK_1: reading from backup piece /home/oracle/duplicate/al_t902681874_s12_p1
channel ORA_DISK_1: piece handle=/home/oracle/duplicate/al_t902681874_s12_p1 tag=TAG20160201T165754
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_743_cby8pbbf_.arc thread=1 sequence=743
channel default: deleting archived log(s)
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_743_cby8pbbf_.arc RECID=16 STAMP=902683082
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_744_cby8pbc5_.arc thread=1 sequence=744
channel default: deleting archived log(s)
archived log file name=/u01/app/oracle/11.2.0.4/fast_recovery_area/DEP/archivelog/2016_02_01/o1_mf_1_744_cby8pbc5_.arc RECID=15 STAMP=902683082
unable to find archived log
archived log thread=1 sequence=745
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/01/2016 17:18:03
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 745 and starting SCN of 14019269
提示需要sequence=745號的archivelog
12.查看備份集中歸檔文件al_t902681874_s12_p1的sequence是12。
13.再次執行恢復
RMAN> run{
2> allocate channel ch00 type disk;
3> set until sequence 13 thread 1;
4> recover database;
5> release channel ch00;
6> }
released channel: ORA_DISK_1
allocated channel: ch00
channel ch00: SID=10 device type=DISK
executing command: SET until clause
Starting recover at 01-FEB-16
starting media recovery
media recovery complete, elapsed time: 00:00:00
Finished recover at 01-FEB-16
released channel: ch00
對應alert日志：
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Starting background process QMNC
Mon Feb 01 17:22:33 2016
QMNC started with pid=27, OS id=4154
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
14.開啟庫2
SQL> alter database open resetlogs;
Database altered.
對應alert日志：
Completed: alter database open resetlogs
Mon Feb 01 17:22:35 2016
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Feb 01 17:22:35 2016
Starting background process CJQ0
Mon Feb 01 17:22:35 2016
CJQ0 started with pid=28, OS id=4168
15.登錄庫2，用戶、對象等信息和庫1完全一致。
總結：
?1.RMAN執行restore需要數據庫置於mount狀態。
2.可以先將target的control控制文件拷貝到auxiliary庫相同路徑下，需要注意參數文件中定義的控制文件路徑以及其他文件夾均需要提前在auxiliary庫中創建，如果提前將控制文件拷貝到auxiliary庫對應路徑下，則無需restore control，相當於已經做了這不操作。
?3.resetlogs提示ORA1152錯誤，需要進行相應歸檔日志的恢復，根據拷貝過來的歸檔日志文件名推算seq號。
