Oracle 10G RAC - SYSAUX进行完全恢复的问题

在进行10G RAC做完全恢复时,需要注意一下

a,当需要恢复的文件是system或sysaux时,需要在mount状态下完成,与一般的数据文件也可在offline下不同;
b,当恢复时可以在一个节点完成,前提是该节点可以访问到所有的备份集文件与归档日志;
c,当在vmrac1中进行恢复时,如果vmrac2没有开启,且此时本地归档日志不全时,恢复会报错,提示找不到需要的日志,即使通过OS拷贝也无法识别,因为控制文件不知道这些文件存在vmrac1上;此时需要开启vmrac2节点至mount状态,因为2个节点定义的归档路径完全相同,并且缺失的日志是由vmrac2产生的,所以此时当2节点同时开启时,控制文件就能识别完整的所有归档日志,最后才能进行恢复.
d,不清楚单个节点是否可以注册缺失的归档日志,从而仅在单节点上完成该恢复,譬如vmrac1注册vmrac2上生成的归档,就算vmrac2不开启实例至mount也能恢复?

如下报错:以恢复sysaux数据文件为例

RMAN> startup nomount
RMAN> alter database mount;

database mounted
released channel: ORA_DISK_1

RMAN> restore datafile 3;

Starting restore at 05-JAN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=148 instance=JTODS1 devtype=DISK

channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00003 to +DATA/jtods/sysaux01.dbf
channel ORA_DISK_1: reading from backup piece +RECOVERY/jtods/backupset/2012_01_04/nnndf0_tag20120104t221941_0.265.771718783
channel ORA_DISK_1: restored backup piece 1
piece handle=+RECOVERY/jtods/backupset/2012_01_04/nnndf0_tag20120104t221941_0.265.771718783 tag=TAG20120104T221941
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
RMAN> recover database;

Starting recover at 05-JAN-12
using channel ORA_DISK_1

starting media recovery

archive log thread 1 sequence 4 is already on disk as file /arch/JTODS1_arch/1_4_771704921.dbf
archive log thread 1 sequence 6 is already on disk as file /arch/JTODS1_arch/1_6_771704921.dbf
archive log thread 1 sequence 7 is already on disk as file /arch/JTODS1_arch/1_7_771704921.dbf
archive log thread 1 sequence 8 is already on disk as file /arch/JTODS1_arch/1_8_771704921.dbf
archive log thread 1 sequence 11 is already on disk as file /arch/JTODS1_arch/1_11_771704921.dbf
archive log thread 1 sequence 12 is already on disk as file /arch/JTODS1_arch/1_12_771704921.dbf
archive log thread 1 sequence 15 is already on disk as file /arch/JTODS1_arch/1_15_771704921.dbf
archive log thread 1 sequence 16 is already on disk as file /arch/JTODS1_arch/1_16_771704921.dbf
archive log thread 2 sequence 5 is already on disk as file /arch/JTODS2_arch/2_5_771704921.dbf
archive log thread 2 sequence 6 is already on disk as file /arch/JTODS1_arch/2_6_771704921.dbf
archive log thread 2 sequence 7 is already on disk as file /arch/JTODS1_arch/2_7_771704921.dbf
archive log thread 2 sequence 8 is already on disk as file /arch/JTODS1_arch/2_8_771704921.dbf
archive log thread 2 sequence 11 is already on disk as file /arch/JTODS1_arch/2_11_771704921.dbf
archive log thread 2 sequence 12 is already on disk as file /arch/JTODS1_arch/2_12_771704921.dbf
archive log thread 2 sequence 13 is already on disk as file /arch/JTODS1_arch/2_13_771704921.dbf
archive log thread 2 sequence 14 is already on disk as file /arch/JTODS1_arch/2_14_771704921.dbf
archive log thread 2 sequence 15 is already on disk as file /arch/JTODS2_arch/2_15_771704921.dbf
archive log thread 2 sequence 16 is already on disk as file /arch/JTODS1_arch/2_16_771704921.dbf
archive log thread 2 sequence 17 is already on disk as file /arch/JTODS1_arch/2_17_771704921.dbf
archive log thread 2 sequence 18 is already on disk as file /arch/JTODS1_arch/2_18_771704921.dbf
archive log thread 2 sequence 19 is already on disk as file /arch/JTODS1_arch/2_19_771704921.dbf
archive log thread 2 sequence 20 is already on disk as file /arch/JTODS2_arch/2_20_771704921.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/05/2012 22:53:41
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 10 lowscn 472828 found to restore
RMAN-06025: no backup of log thread 2 seq 9 lowscn 472689 found to restore
RMAN-06025: no backup of log thread 1 seq 14 lowscn 545153 found to restore
RMAN-06025: no backup of log thread 1 seq 13 lowscn 523043 found to restore
RMAN-06025: no backup of log thread 1 seq 10 lowscn 496247 found to restore
RMAN-06025: no backup of log thread 1 seq 9 lowscn 472830 found to restore
RMAN-06025: no backup of log thread 1 seq 5 lowscn 417667 found to restore
在vmrac2还没有开启时,拷贝这些日志到节点1 vmrac1也无法识别,是否有其他方式注册这些归档日志?使得即使不开启vmrac2也能够识别日志.

vmrac2上
SQL> startup mount;

拷贝上述缺失的日志到vmrac1,再次recover database.
RMAN> recover database;

Starting recover at 05-JAN-12
using channel ORA_DISK_1

starting media recovery
archive log thread 1 sequence 4 is already on disk as file /arch/JTODS1_arch/1_4_771704921.dbf
archive log thread 1 sequence 5 is already on disk as file /arch/JTODS2_arch/1_5_771704921.dbf
archive log thread 1 sequence 6 is already on disk as file /arch/JTODS1_arch/1_6_771704921.dbf
archive log thread 1 sequence 7 is already on disk as file /arch/JTODS1_arch/1_7_771704921.dbf
archive log thread 1 sequence 8 is already on disk as file /arch/JTODS1_arch/1_8_771704921.dbf
archive log thread 1 sequence 9 is already on disk as file /arch/JTODS2_arch/1_9_771704921.dbf
archive log thread 1 sequence 10 is already on disk as file /arch/JTODS2_arch/1_10_771704921.dbf
archive log thread 1 sequence 11 is already on disk as file /arch/JTODS1_arch/1_11_771704921.dbf
archive log thread 1 sequence 12 is already on disk as file /arch/JTODS1_arch/1_12_771704921.dbf
archive log thread 1 sequence 13 is already on disk as file /arch/JTODS2_arch/1_13_771704921.dbf
archive log thread 1 sequence 14 is already on disk as file /arch/JTODS2_arch/1_14_771704921.dbf
archive log thread 1 sequence 15 is already on disk as file /arch/JTODS1_arch/1_15_771704921.dbf
archive log thread 1 sequence 16 is already on disk as file /arch/JTODS1_arch/1_16_771704921.dbf
archive log thread 2 sequence 5 is already on disk as file /arch/JTODS2_arch/2_5_771704921.dbf
archive log thread 2 sequence 6 is already on disk as file /arch/JTODS1_arch/2_6_771704921.dbf
archive log thread 2 sequence 7 is already on disk as file /arch/JTODS1_arch/2_7_771704921.dbf
archive log thread 2 sequence 8 is already on disk as file /arch/JTODS1_arch/2_8_771704921.dbf
archive log thread 2 sequence 9 is already on disk as file /arch/JTODS2_arch/2_9_771704921.dbf
archive log thread 2 sequence 10 is already on disk as file /arch/JTODS2_arch/2_10_771704921.dbf
archive log thread 2 sequence 11 is already on disk as file /arch/JTODS1_arch/2_11_771704921.dbf
archive log thread 2 sequence 12 is already on disk as file /arch/JTODS1_arch/2_12_771704921.dbf
archive log thread 2 sequence 13 is already on disk as file /arch/JTODS1_arch/2_13_771704921.dbf
archive log thread 2 sequence 14 is already on disk as file /arch/JTODS1_arch/2_14_771704921.dbf
archive log thread 2 sequence 15 is already on disk as file /arch/JTODS2_arch/2_15_771704921.dbf
archive log thread 2 sequence 16 is already on disk as file /arch/JTODS1_arch/2_16_771704921.dbf
archive log thread 2 sequence 17 is already on disk as file /arch/JTODS1_arch/2_17_771704921.dbf
archive log thread 2 sequence 18 is already on disk as file /arch/JTODS1_arch/2_18_771704921.dbf
archive log thread 2 sequence 19 is already on disk as file /arch/JTODS1_arch/2_19_771704921.dbf
archive log thread 2 sequence 20 is already on disk as file /arch/JTODS2_arch/2_20_771704921.dbf
archive log filename=/arch/JTODS1_arch/1_4_771704921.dbf thread=1 sequence=4
archive log filename=/arch/JTODS2_arch/2_5_771704921.dbf thread=2 sequence=5
archive log filename=/arch/JTODS2_arch/1_5_771704921.dbf thread=1 sequence=5
archive log filename=/arch/JTODS1_arch/2_6_771704921.dbf thread=2 sequence=6
archive log filename=/arch/JTODS1_arch/2_7_771704921.dbf thread=2 sequence=7
archive log filename=/arch/JTODS1_arch/1_6_771704921.dbf thread=1 sequence=6
archive log filename=/arch/JTODS1_arch/2_8_771704921.dbf thread=2 sequence=8
archive log filename=/arch/JTODS1_arch/1_7_771704921.dbf thread=1 sequence=7
archive log filename=/arch/JTODS1_arch/1_8_771704921.dbf thread=1 sequence=8
archive log filename=/arch/JTODS2_arch/2_9_771704921.dbf thread=2 sequence=9
archive log filename=/arch/JTODS2_arch/2_10_771704921.dbf thread=2 sequence=10
archive log filename=/arch/JTODS2_arch/1_9_771704921.dbf thread=1 sequence=9
archive log filename=/arch/JTODS2_arch/1_10_771704921.dbf thread=1 sequence=10
archive log filename=/arch/JTODS1_arch/2_11_771704921.dbf thread=2 sequence=11
archive log filename=/arch/JTODS1_arch/2_12_771704921.dbf thread=2 sequence=12
archive log filename=/arch/JTODS1_arch/2_13_771704921.dbf thread=2 sequence=13
archive log filename=/arch/JTODS1_arch/1_11_771704921.dbf thread=1 sequence=11
archive log filename=/arch/JTODS1_arch/2_14_771704921.dbf thread=2 sequence=14
archive log filename=/arch/JTODS1_arch/1_12_771704921.dbf thread=1 sequence=12
archive log filename=/arch/JTODS2_arch/2_15_771704921.dbf thread=2 sequence=15
archive log filename=/arch/JTODS2_arch/1_13_771704921.dbf thread=1 sequence=13
archive log filename=/arch/JTODS1_arch/2_16_771704921.dbf thread=2 sequence=16
archive log filename=/arch/JTODS2_arch/1_14_771704921.dbf thread=1 sequence=14
archive log filename=/arch/JTODS1_arch/2_17_771704921.dbf thread=2 sequence=17
archive log filename=/arch/JTODS1_arch/2_18_771704921.dbf thread=2 sequence=18
archive log filename=/arch/JTODS1_arch/1_15_771704921.dbf thread=1 sequence=15
archive log filename=/arch/JTODS1_arch/2_19_771704921.dbf thread=2 sequence=19
Finished recover at 05-JAN-12

RMAN> alter database open;

database opened

节点2上
SQL> alter database open;