合 Oracle rac数据库备份集恢复到单机环境

• 前言部分
• 导读
• 实验环境介绍
• 实验部分
• 实验目标
• 源rac库执行
• 查看rac环境及创建测试表
• 生成pfile文件
• 执行备份操作
• 将备份传递到target库
• target库上执行
• 修改pfile文件生成spfile文件、生成pfile中的文件路径
• 启动到nomount状态并还原控制文件
• 启动到mount状态并还原和恢复整个数据库
• restore 数据库
• recover数据库
• RESETLOGS打开数据库并验证数据
• 后续收尾操作
• 清除未使用的redo
• 清除多余的 undo 文件
• 实验总结
• 总结
• How To Restore RMAN Disk backups of RAC Database to Single Instance On Another Node (文档 ID 415579.1)
• APPLIES TO:
• GOAL
• SOLUTION
• REFERENCES

15> SQL "ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_3.281.877470929'' to ''/u01/app/oracle/oradata/jmrac/redo03_1.log'' ";

16> SQL "ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_3.282.877470931'' to ''/u01/app/oracle/oradata/jmrac/redo03_2.log'' ";

17> SQL "ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_4.283.877470937'' to ''/u01/app/oracle/oradata/jmrac/redo04_1.log'' ";

18> SQL "ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_4.284.877470943'' to ''/u01/app/oracle/oradata/jmrac/redo04_2.log'' ";

19>

20> RESTORE DATABASE;

21> SWITCH DATAFILE ALL;

22> SWITCH TEMPFILE ALL;

23> }

allocated channel: c1

channel c1: SID=1137 device type=DISK

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_2.276.877470349'' to ''/u01/app/oracle/oradata/jmrac/redo02_1.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_2.277.877470349'' to ''/u01/app/oracle/oradata/jmrac/redo02_2.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_1.274.877470345'' to ''/u01/app/oracle/oradata/jmrac/redo01_1.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_1.275.877470345'' to ''/u01/app/oracle/oradata/jmrac/redo01_2.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_3.281.877470929'' to ''/u01/app/oracle/oradata/jmrac/redo03_1.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_3.282.877470931'' to ''/u01/app/oracle/oradata/jmrac/redo03_2.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_4.283.877470937'' to ''/u01/app/oracle/oradata/jmrac/redo04_1.log''

sql statement: ALTER DATABASE RENAME FILE ''+DATA/jmrac/onlinelog/group_4.284.877470943'' to ''/u01/app/oracle/oradata/jmrac/redo04_2.log''

Starting restore at 2015-05-29 15:16:46

channel c1: starting datafile backup set restore

channel c1: specifying datafile(s) to restore from backup set

channel c1: restoring datafile 00002 to /u01/app/oracle/oradata/jmrac/sysaux01.dbf

channel c1: restoring datafile 00003 to /u01/app/oracle/oradata/jmrac/undotbs01.dbf

channel c1: restoring datafile 00005 to /u01/app/oracle/oradata/jmrac/example01.dbf

channel c1: reading from backup piece /home/oracle/rman_back/full_JMRACxxx_20150529_880974780_6_1.bak

channel c1: piece handle=/home/oracle/rman_back/full_JMRACxxx_20150529_880974780_6_1.bak tag=TAG20150529T111259

channel c1: restored backup piece 1

channel c1: restore complete, elapsed time: 00:00:35

channel c1: starting datafile backup set restore

channel c1: specifying datafile(s) to restore from backup set

channel c1: restoring datafile 00001 to /u01/app/oracle/oradata/jmrac/system01.dbf

channel c1: restoring datafile 00004 to /u01/app/oracle/oradata/jmrac/users01.dbf

channel c1: restoring datafile 00006 to /u01/app/oracle/oradata/jmrac/undotbs02.dbf

channel c1: reading from backup piece /home/oracle/rman_back/full_JMRACxxx_20150529_880974780_5_1.bak

channel c1: piece handle=/home/oracle/rman_back/full_JMRACxxx_20150529_880974780_5_1.bak tag=TAG20150529T111259

channel c1: restored backup piece 1

channel c1: restore complete, elapsed time: 00:00:35

Finished restore at 2015-05-29 15:17:57

datafile 1 switched to datafile copy

input datafile copy RECID=8 STAMP=880989478 file name=/u01/app/oracle/oradata/jmrac/system01.dbf

datafile 2 switched to datafile copy

input datafile copy RECID=9 STAMP=880989478 file name=/u01/app/oracle/oradata/jmrac/sysaux01.dbf

datafile 3 switched to datafile copy

input datafile copy RECID=10 STAMP=880989478 file name=/u01/app/oracle/oradata/jmrac/undotbs01.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=11 STAMP=880989478 file name=/u01/app/oracle/oradata/jmrac/users01.dbf

datafile 5 switched to datafile copy

input datafile copy RECID=12 STAMP=880989478 file name=/u01/app/oracle/oradata/jmrac/example01.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=13 STAMP=880989479 file name=/u01/app/oracle/oradata/jmrac/undotbs02.dbf

renamed tempfile 1 to /u01/app/oracle/oradata/jmrac/temp01.dbf in control file

released channel: c1

RMAN>

告警日志：

Fri May 29 15:16:45 2015

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_2.276.877470349' to '/u01/app/oracle/oradata/jmrac/redo02_1.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_2.276.877470349

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_2.276.877470349' to '/u01/app/oracle/oradata/jmrac/redo02_1.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_2.277.877470349' to '/u01/app/oracle/oradata/jmrac/redo02_2.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_2.277.877470349

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_2.277.877470349' to '/u01/app/oracle/oradata/jmrac/redo02_2.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_1.274.877470345' to '/u01/app/oracle/oradata/jmrac/redo01_1.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_1.274.877470345

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_1.274.877470345' to '/u01/app/oracle/oradata/jmrac/redo01_1.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_1.275.877470345' to '/u01/app/oracle/oradata/jmrac/redo01_2.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_1.275.877470345

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_1.275.877470345' to '/u01/app/oracle/oradata/jmrac/redo01_2.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_3.281.877470929' to '/u01/app/oracle/oradata/jmrac/redo03_1.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_3.281.877470929

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_3.281.877470929' to '/u01/app/oracle/oradata/jmrac/redo03_1.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_3.282.877470931' to '/u01/app/oracle/oradata/jmrac/redo03_2.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_3.282.877470931

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_3.282.877470931' to '/u01/app/oracle/oradata/jmrac/redo03_2.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_4.283.877470937' to '/u01/app/oracle/oradata/jmrac/redo04_1.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_4.283.877470937

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_4.283.877470937' to '/u01/app/oracle/oradata/jmrac/redo04_1.log'

ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_4.284.877470943' to '/u01/app/oracle/oradata/jmrac/redo04_2.log'

Deleted Oracle managed file +DATA/jmrac/onlinelog/group_4.284.877470943

Completed: ALTER DATABASE RENAME FILE '+DATA/jmrac/onlinelog/group_4.284.877470943' to '/u01/app/oracle/oradata/jmrac/redo04_2.log'

Fri May 29 15:16:51 2015

Full restore complete of datafile 3 to datafile copy /u01/app/oracle/oradata/jmrac/undotbs01.dbf. Elapsed time: 0:00:02

checkpoint is 1624119

last deallocation scn is 1529290

Undo Optimization current scn is 1542977

Full restore complete of datafile 5 to datafile copy /u01/app/oracle/oradata/jmrac/example01.dbf. Elapsed time: 0:00:09

checkpoint is 1624119

last deallocation scn is 1379034

Fri May 29 15:17:18 2015

Full restore complete of datafile 2 to datafile copy /u01/app/oracle/oradata/jmrac/sysaux01.dbf. Elapsed time: 0:00:30

checkpoint is 1624119

last deallocation scn is 1348692

Full restore complete of datafile 6 to datafile copy /u01/app/oracle/oradata/jmrac/undotbs02.dbf. Elapsed time: 0:00:00

checkpoint is 1624083

last deallocation scn is 1549684

Undo Optimization current scn is 1542977

Full restore complete of datafile 4 to datafile copy /u01/app/oracle/oradata/jmrac/users01.dbf. Elapsed time: 0:00:01

checkpoint is 1624083

Fri May 29 15:17:52 2015

Full restore complete of datafile 1 to datafile copy /u01/app/oracle/oradata/jmrac/system01.dbf. Elapsed time: 0:00:29

checkpoint is 1624083

last deallocation scn is 1547365

Undo Optimization current scn is 1542977

Fri May 29 15:18:00 2015

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/system.268.877470209

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/system.268.877470209

ORA-15012: ASM file '+DATA/jmrac/datafile/system.268.877470209' does not exist

Switch of datafile 1 complete to datafile copy

checkpoint is 1624083

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/sysaux.269.877470211

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/sysaux.269.877470211

ORA-15012: ASM file '+DATA/jmrac/datafile/sysaux.269.877470211' does not exist

Switch of datafile 2 complete to datafile copy

checkpoint is 1624119

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/undotbs1.270.877470213

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/undotbs1.270.877470213

ORA-15012: ASM file '+DATA/jmrac/datafile/undotbs1.270.877470213' does not exist

Switch of datafile 3 complete to datafile copy

checkpoint is 1624119

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/users.271.877470213

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/users.271.877470213

ORA-15012: ASM file '+DATA/jmrac/datafile/users.271.877470213' does not exist

Switch of datafile 4 complete to datafile copy

checkpoint is 1624083

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/example.279.877470401

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/example.279.877470401

ORA-15012: ASM file '+DATA/jmrac/datafile/example.279.877470401' does not exist

Switch of datafile 5 complete to datafile copy

checkpoint is 1624119

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14335.trc:

ORA-19625: error identifying file +DATA/jmrac/datafile/undotbs2.280.877470779

ORA-17503: ksfdopn:2 Failed to open file +DATA/jmrac/datafile/undotbs2.280.877470779

ORA-15012: ASM file '+DATA/jmrac/datafile/undotbs2.280.877470779' does not exist

Fri May 29 15:18:01 2015

Signalling error 1152 for datafile 5!

Switch of datafile 6 complete to datafile copy

checkpoint is 1624083

Signalling error 1152 for datafile 6!

Checker run found 2 new persistent data failures

查看数据文件是否已经还原：

[oracle@orcltest jmrac]$ ll -h

total 1.5G

-rw-r----- 1 oracle asmadmin 18M May 29 15:18 control01.ctl

-rw-r----- 1 oracle asmadmin 18M May 29 15:18 control02.ctl

-rw-r----- 1 oracle asmadmin 101M May 29 15:16 example01.dbf

-rw-r----- 1 oracle asmadmin 541M May 29 15:17 sysaux01.dbf

-rw-r----- 1 oracle asmadmin 691M May 29 15:17 system01.dbf

-rw-r----- 1 oracle asmadmin 91M May 29 15:16 undotbs01.dbf

-rw-r----- 1 oracle asmadmin 26M May 29 15:17 undotbs02.dbf

-rw-r----- 1 oracle asmadmin 27M May 29 15:17 users01.dbf

[oracle@orcltest jmrac]$

recover数据库

由前边的备份集中可以看出，备份集中的thread 1的最大日志号为33，thread 2的最大日志号为43，所以不完全恢复如下：

RMAN> RUN

2> {

3> set until sequence 33 thread 1;

set until sequence 43 thread 2;

recover database;

}

4> 5> 6>

executing command: SET until clause

executing command: SET until clause

Starting recover at 2015-05-29 15:28:05

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=1146 device type=DISK

starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination

channel ORA_DISK_1: restoring archived log

archived log thread=2 sequence=42

channel ORA_DISK_1: restoring archived log

archived log thread=1 sequence=32

channel ORA_DISK_1: restoring archived log

archived log thread=1 sequence=33

channel ORA_DISK_1: reading from backup piece /home/oracle/rman_back/arch_JMRAC_20150529_11_1.bak

channel ORA_DISK_1: piece handle=/home/oracle/rman_back/arch_JMRAC_20150529_11_1.bak tag=TAG20150529T111603

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/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_2_42bpj5896k.arc thread=2 sequence=42

archived log file name=/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_32bpj5897f.arc thread=1 sequence=32

channel default: deleting archived log(s)

archived log file name=/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_32bpj5897f.arc RECID=74 STAMP=880990089

archived log file name=/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_33bpj5897n.arc thread=1 sequence=33

channel default: deleting archived log(s)

archived log file name=/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_2_42bpj5896k.arc RECID=75 STAMP=880990089

channel default: deleting archived log(s)

archived log file name=/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_33bpj5897n.arc RECID=73 STAMP=880990089

media recovery complete, elapsed time: 00:00:02

Finished recover at 2015-05-29 15:28:12

RMAN>

告警日志：

Fri May 29 15:28:06 2015

alter database recover datafile list clear

Completed: alter database recover datafile list clear

alter database recover datafile list

1 , 2 , 3 , 4 , 5 , 6

Completed: alter database recover datafile list

1 , 2 , 3 , 4 , 5 , 6

alter database recover if needed

start until cancel using backup controlfile

Media Recovery Start

started logmerger process

Parallel Media Recovery started with 2 slaves

ORA-279 signalled during: alter database recover if needed

start until cancel using backup controlfile

...

alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_2_42bpj5896k.arc'

Media Recovery Log /u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_2_42bpj5896k.arc

ORA-279 signalled during: alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_2_42bpj5896k.arc'...

alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_32bpj5897f.arc'

Media Recovery Log /u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_32bpj5897f.arc

ORA-279 signalled during: alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_32bpj5897f.arc'...

alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_33bpj5897n.arc'

Media Recovery Log /u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_33bpj5897n.arc

ORA-279 signalled during: alter database recover logfile '/u01/app/oracle/flash_recovery_area/JMRAC/archivelog/2015_05_29/o1_mf_1_33bpj5897n.arc'...

alter database recover cancel

Media Recovery Canceled

Completed: alter database recover cancel

RESETLOGS打开数据库并验证数据

RMAN> alter database open resetlogs;

database opened

RMAN>

告警日志：

Fri May 29 15:30:56 2015

alter database open

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

ORA-1589 signalled during: alter database open...

alter database open resetlogs

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 3 of thread 2

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 3 of thread 2

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 4 of thread 2

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 4 of thread 2

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

RESETLOGS after incomplete recovery UNTIL CHANGE 1625245

Resetting resetlogs activation ID 1916751680 (0x723f4f40)

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 1 of thread 1

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/jmrac/redo01_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 2 of thread 1

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/jmrac/redo02_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 3 of thread 2

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 3 of thread 2

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 3 thread 2: '/u01/app/oracle/oradata/jmrac/redo03_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 4 of thread 2

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_ora_14414.trc:

ORA-00313: open failed for members of log group 4 of thread 2

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_2.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00312: online log 4 thread 2: '/u01/app/oracle/oradata/jmrac/redo04_1.log'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Fri May 29 15:31:08 2015

Setting recovery target incarnation to 3

Fri May 29 15:31:08 2015

Assigning activation ID 1920208641 (0x72740f01)

LGWR: STARTING ARCH PROCESSES

Fri May 29 15:31:09 2015

ARC0 started with pid=22, OS id=14444

ARC0: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC0: STARTING ARCH PROCESSES

Fri May 29 15:31:10 2015

ARC1 started with pid=26, OS id=14446

Fri May 29 15:31:10 2015

ARC2 started with pid=27, OS id=14448

ARC1: Archival started

Fri May 29 15:31:10 2015

ARC3 started with pid=28, OS id=14450

ARC2: Archival started

ARC1: Becoming the 'no FAL' ARCH

ARC1: Becoming the 'no SRL' ARCH

ARC2: Becoming the heartbeat ARCH

Thread 1 opened at log sequence 1

Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/jmrac/redo01_1.log

Current log# 1 seq# 1 mem# 1: /u01/app/oracle/oradata/jmrac/redo01_2.log

Successful open of redo thread 1

Fri May 29 15:31:10 2015

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Fri May 29 15:31:10 2015

SMON: enabling cache recovery

Redo thread 2 internally disabled at seq 1 (CKPT)

ARC3: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

ARC1: Archiving disabled thread 2 sequence 1

Archived Log entry 76 added for thread 2 sequence 1 ID 0x0 dest 1:

Successfully onlined Undo Tablespace 2.

Dictionary check beginning

Fri May 29 15:31:14 2015

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_dbw0_14084.trc:

ORA-01157: cannot identify/lock data file 201 - see DBWR trace file

ORA-01110: data file 201: '/u01/app/oracle/oradata/jmrac/temp01.dbf'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Errors in file /u01/app/oracle/diag/rdbms/jmrac/jmrac/trace/jmrac_dbw0_14084.trc:

ORA-01186: file 201 failed verification tests

ORA-01157: cannot identify/lock data file 201 - see DBWR trace file

ORA-01110: data file 201: '/u01/app/oracle/oradata/jmrac/temp01.dbf'

File 201 not verified due to error ORA-01157

Dictionary check complete

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Re-creating tempfile /u01/app/oracle/oradata/jmrac/temp01.dbf

Database Characterset is ZHS16GBK

No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Fri May 29 15:31:22 2015

Starting background process QMNC

Fri May 29 15:31:22 2015

QMNC started with pid=29, OS id=14454

LOGSTDBY: Validating controlfile with logical metadata

LOGSTDBY: Validation complete

Completed: alter database open resetlogs

Fri May 29 15:31:33 2015

Starting background process CJQ0

Fri May 29 15:31:33 2015

CJQ0 started with pid=35, OS id=14472

验证数据：

[oracle@orcltest dbs]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Fri May 29 15:33:02 2015

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

SQL> show parameter name

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

db_file_name_convert string

db_name string jmrac

db_unique_name string jmrac

global_names boolean FALSE

instance_name string jmrac

lock_name_space string

log_file_name_convert string

service_names string jmrac

SQL> archive log list;

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 1

Next log sequence to archive 1

Current log sequence 1

SQL> set line 9999 pagesize 9999

SQL> col FILE_NAME format a60

SQL> select 'datafile' file_type, file#,name FILE_NAME,status,enabled from v$datafile

2 union all

3 select 'tempfile',file#,name FILE_NAME,status,enabled from v$tempfile

4 union all

5 select 'logfile',group# file#,member FILE_NAME,status,'' from v$logfile

6 union all

7 select 'controlfile', to_number('') ,name FILE_NAME,status,'' from v$controlfile

8 ;

FILE_TYPE FILE# FILE_NAME STATUS ENABLED

----------- ---------- ------------------------------------------------------------ ------- ----------

datafile 1 /u01/app/oracle/oradata/jmrac/system01.dbf SYSTEM READ WRITE

datafile 2 /u01/app/oracle/oradata/jmrac/sysaux01.dbf ONLINE READ WRITE

datafile 3 /u01/app/oracle/oradata/jmrac/undotbs01.dbf ONLINE READ WRITE

datafile 4 /u01/app/oracle/oradata/jmrac/users01.dbf ONLINE READ WRITE

datafile 5 /u01/app/oracle/oradata/jmrac/example01.dbf ONLINE READ WRITE

datafile 6 /u01/app/oracle/oradata/jmrac/undotbs02.dbf ONLINE READ WRITE

tempfile 1 /u01/app/oracle/oradata/jmrac/temp01.dbf ONLINE READ WRITE

logfile 2 /u01/app/oracle/oradata/jmrac/redo02_1.log

logfile 2 /u01/app/oracle/oradata/jmrac/redo02_2.log

logfile 1 /u01/app/oracle/oradata/jmrac/redo01_1.log

logfile 1 /u01/app/oracle/oradata/jmrac/redo01_2.log

logfile 3 /u01/app/oracle/oradata/jmrac/redo03_1.log

logfile 3 /u01/app/oracle/oradata/jmrac/redo03_2.log

logfile 4 /u01/app/oracle/oradata/jmrac/redo04_1.log

logfile 4 /u01/app/oracle/oradata/jmrac/redo04_2.log

controlfile /u01/app/oracle/oradata/jmrac/control01.ctl

controlfile /u01/app/oracle/oradata/jmrac/control02.ctl

17 rows selected.

SQL> select count(1) from lhr.rac_to_single_test ;

COUNT(1)

----------

72510

SQL>

可以看到数据已经恢复。

后续收尾操作

做到这步，都还没有完啊，只是说目的基本达成，最后还需要收尾的工作。清除未使用线程的 redo 日志组，操作如下：

清除未使用的redo

SQL> col instance format a8

SQL> select thread#,instance,status,enabled from v$thread;

THREAD# INSTANCE STATUS ENABLED

---------- -------- ------ --------

1 jmrac OPEN PUBLIC

2 jmrac2 CLOSED PUBLIC

SQL> select group#,thread#,archived,status from v$log;

GROUP# THREAD# ARC STATUS

---------- ---------- --- ----------------

1 1 NO CURRENT

2 1 YES UNUSED

3 2 YES ACTIVE

4 2 YES UNUSED

SQL> alter database disable thread 2 ;

Database altered.

SQL> alter database drop logfile group 3 ;

Database altered.

SQL> alter database drop logfile group 4 ;

Database altered.

SQL>

SQL> select thread#,instance,status,enabled from v$thread;

THREAD# INSTANCE STATUS ENABLED

---------- -------- ------ --------

1 jmrac OPEN PUBLIC

SQL>

SQL> select group#,thread#,archived,status from v$log;

GROUP# THREAD# ARC STATUS

---------- ---------- --- ----------------

1 1 NO CURRENT

2 1 YES UNUSED

SQL>

生产环境可以再增加一些日志组。

清除多余的 undo 文件

我们知道rac中每个节点使用的都是自己的undo，所以有2个undo文件，这里可以清除，也可以不用清除，因为有的时候undo坏了可以很迅速的切换到另外的undo空间，清理过程如下：

SQL> select name from v$tablespace where name like 'UNDO%';

NAME

------------------------------

UNDOTBS1

UNDOTBS2

SQL> show parameter undo_tablespace;

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

undo_tablespace string UNDOTBS1

SQL> drop tablespace undotbs2 including contents and datafiles;

Tablespace dropped.

SQL>

实验总结

rac数据库迁移到单实例环境下的步骤和单实例的数据库迁移到单实例环境基本是一样的，只是在最后还原的时候需要设置2个thread即可。

总结

至此，rac数据库迁移到单实例环境下的操作步骤基本完毕，至于配置监听和tns等工作都是基本的，大家自己完成即可，这里就不再演示了，另外实验中需要关注的几个地方，我都特别做了说明。

How To Restore RMAN Disk backups of RAC Database to Single Instance On Another Node (文档 ID 415579.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 9.2.0.1 and later
Information in this document applies to any platform.
Checked for relevance on 15-Apr-2014

GOAL

- You have a RAC database backed up by RMAN to disk location
- You need to restore this backup as Single Instance on another node

SOLUTION

\1) Take appropriate RMAN backup of the production RAC database. Note that you should turn on the CONTROLFILE AUTOBACKUP configuration so that we have the controlfile backed up after the database backup. When we restore the controlfile on new host from this autobackup piece, it will have the information of the latest backup.

RMAN> run{
2> allocate channel c1 type disk format '/oracle/10g/backup/%U';
3> backup database;
4> backup archivelog all;
5> }

allocated channel: c1
channel c1: sid=133 instance=racdb1 devtype=DISK

Starting backup at 12-FEB-07
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00001 name=/ocfs2/oradata/racdb/system01.dbf
input datafile fno=00002 name=/ocfs2/oradata/racdb/undotbs01.dbf
input datafile fno=00005 name=/ocfs2/oradata/racdb/undotbs02.dbf
input datafile fno=00003 name=/ocfs2/oradata/racdb/sysaux01.dbf
input datafile fno=00004 name=/ocfs2/oradata/racdb/users01.dbf
channel c1: starting piece 1 at 12-FEB-07
channel c1: finished piece 1 at 12-FEB-07
piece handle=/oracle/10g/backup/09i9sruq_1_1 tag=TAG20070212T162458 comment=NONE
channel c1: backup set complete, elapsed time: 00:01:05
Finished backup at 12-FEB-07

Starting backup at 12-FEB-07
current log archived
channel c1: starting archive log backupset
channel c1: specifying archive log(s) in backup set
input archive log thread=1 sequence=56 recid=3 stamp=613417105
input archive log thread=1 sequence=57 recid=4 stamp=613417106
input archive log thread=1 sequence=58 recid=5 stamp=614363168
input archive log thread=2 sequence=1 recid=1 stamp=613417090
input archive log thread=2 sequence=2 recid=2 stamp=613417093
input archive log thread=2 sequence=3 recid=6 stamp=614363170
channel c1: starting piece 1 at 12-FEB-07
channel c1: finished piece 1 at 12-FEB-07
piece handle=/oracle/10g/backup/0ai9ss14_1_1 tag=TAG20070212T162610 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:04
Finished backup at 12-FEB-07

Starting Control File and SPFILE Autobackup at 12-FEB-07
piece handle=/oracle/10g/backup/c-610677177-20070212-00 comment=NONE
Finished Control File and SPFILE Autobackup at 12-FEB-07
released channel: c1

\2) Create a PFILE for the single instance database using the production RAC parameter file
a) don't forget to modify the following parameters depending on the directory structure of the new host: audit_file_dest, background_dump_dest, control_files, core_dump_dest, log_archive_dest_1, user_dump_dest etc
b) remove RAC specific parameters such as cluster_database_instances, cluster_database etc
c) for the parameter undo_tablespace, mention any one undo tablespace name

Known issue which may require an additional parameter to be set :
Note 334899.1 RMAN Duplicate from RAC backup fails ORA-38856

\3) Move the backup pieces and the modified INIT.ORA file to the new host. Starting from 10g it is NO longer compulsory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.

\4) Use the pfile created above to STARTUP NOMOUNT the database on the new host

oracle@test-br ractest]$ sqlplus "/ as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on Fri Feb 16 03:14:23 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup nomount;
ORACLE instance started.

Total System Global Area 167772160 bytes
Fixed Size 1218292 bytes
Variable Size 62916876 bytes
Database Buffers 96468992 bytes
Redo Buffers 7168000 bytes

\5) Now invoke RMAN and restore the controlfile specifying the location where the controlfile autobackup piece is restored on this new server. You can mount the database once the controlfile is restored successfully.

[oracle@test-br ractest]$ rman target / nocatalog

Recovery Manager: Release 10.2.0.1.0 - Production on Fri Feb 16 03:16:31 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: racdb (not mounted)
using target database control file instead of recovery catalog

RMAN> restore controlfile from '/u01/oracle/oradata/ractest/c-610677177-20070212-00';

Starting restore at 16-FEB-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output filename=/u01/oracle/oradata/ractest/control01.ctl
Finished restore at 16-FEB-07

RMAN> alter database mount;

database mounted
released channel: ORA_DISK_1

\6) You can skip this step if you have restored the RMAN backup pieces to exactly the same location they were backed up on production. If this is not the case then you need to catalog the RMAN backup pieces to make RMAN aware of thier new location on the new host. Note that CATALOG BACKUPPIECE command is available only starting from 10g.

RMAN> catalog backuppiece '/u01/oracle/oradata/ractest/09i9sruq_1_1';

cataloged backuppiece
backup piece handle=/u01/oracle/oradata/ractest/09i9sruq_1_1 recid=10 stamp=614661579

RMAN> catalog backuppiece '/u01/oracle/oradata/ractest/0ai9ss14_1_1';

cataloged backuppiece
backup piece handle=/u01/oracle/oradata/ractest/0ai9ss14_1_1 recid=11 stamp=614661599

\7) Now we'll determine the point upto which media recovery should run on the restored database.

RMAN> list backup of archivelog all;

List of Archived Logs in backup set 9
Thrd Seq Low SCN Low Time Next SCN Next Time

---

1 56 214541 01-FEB-07 226238 01-FEB-07
1 57 226238 01-FEB-07 226240 01-FEB-07
1 58 226240 01-FEB-07 233107 12-FEB-07
2 1 186185 28-JAN-07 225714 01-FEB-07
2 2 225714 01-FEB-07 226037 01-FEB-07
2 3 226037 01-FEB-07 233110 12-FEB-07

Check the last archive sequence for all redo threads and select the archive sequence having LEAST "Next SCN" among them. In our case sequence 58 of thread 1 has Next SCN of 233107 while sequence 3 of thread 2 has Next SCN of 233110. Since squence 58 of thread 1 has least Next SCN we will recover upto this point. (If you are keen to have recovery run until some specific time you can always give SET UNTIL TIME)

\8) Having determined the point upto which media recovery should run, start the restore/recovery using:
Please note in below example we choose Until sequence as 59(one more then the value selected in step 7 that is sequence 58) because When we specify a sequence number, it is considered as an UPPER limit , RMAN selects only
those files which are needed for the recovery and uses 59 as an upper log sequence number while recovering database and would recovery upt log sequence number upto 58 .

RMAN> run {
2> set until sequence 59 thread 1;
3> set newname for datafile 1 to '/u01/oracle/oradata/ractest/data/system01.dbf';
4> set newname for datafile 2 to '/u01/oracle/oradata/ractest/data/undotbs01.dbf';
5> set newname for datafile 3 to '/u01/oracle/oradata/ractest/data/sysaux01.dbf';
6> set newname for datafile 4 to '/u01/oracle/oradata/ractest/data/users01.dbf';
7> set newname for datafile 5 to '/u01/oracle/oradata/ractest/data/undotbs02.dbf';
8> restore database;
9> switch datafile all;
10> recover database;
11> }

In case you want to have the datafiles on a ASM diskgroup (+DATA for eg) for the clone/destination database, you may use SET NEWNAME as below:

set newname for datafile 1 to '+DATA';
set newname for datafile 2 to '+DATA';
....

Known issue in Oracle10g:
Note 1146703.1 Rman Restore From RAC ASM To Single Instance Non ASM Fails With ORA-00600 [kgeade_is_0]

CAUTION !!!!:

If Online Redolog's (ORL's) are Oracle Managed Files (OM), and the Clone is being done on any of Source RAC Node (where ORLs are accessible from), renaming ORL will try to remove Source ORL files!

Please review: http://docs.oracle.com/cd/E11882_01/server.112/e25494/omf.htm#ADMIN11517

The following statements are used to rename files:

ALTER DATABASE RENAME FILE

ALTER TABLESPACE ... RENAME DATAFILE

These statements do not actually rename the files on the operating system, but rather, the names in the control file are changed. If the old file is an Oracle managed file and it exists, then it is deleted. You must specify each filename using the conventions for filenames on your operating system when you issue this statement."

Instead of renaming, we can recreate the controlfile with desired name for ORLs:

SQL> alter database backup controlfile to trace as '/tmp/control.sql' resetlogs ;

Edit /tmp/control.sql and modify desired ORL names.

Since we determined previously that media recovery should run until sequence 58 hence we use SET UNTIL SEQUENCE 59 (+1) above. You also need to use SET NEWNAME clause to restore datafiles to a location on the new host which is different from the production path. Finally, SWITCH DATAFILE ALL clause updates these new datafile locations in the controlfile.

\9) Once RMAN restore/recovery finishes, you will want to rename the online redolog files before opening the database in case the production path of redo log files is not available on the new host. After renaming the redolog files, the database can be opened with RESETLOGS

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------
/ocfs2/oradata/racdb/redo01.log
/ocfs2/oradata/racdb/redo02.log
/ocfs2/oradata/racdb/redo03.log
/ocfs2/oradata/racdb/redo04.log
/ocfs2/oradata/racdb/redo05.log
/ocfs2/oradata/racdb/redo06.log

6 rows selected.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo01.log' to '/u01/oracle/oradata/ractest/log/redo01.log';

Database altered.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo02.log' to '/u01/oracle/oradata/ractest/log/redo02.log';

Database altered.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo03.log' to '/u01/oracle/oradata/ractest/log/redo03.log';

Database altered.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo04.log' to '/u01/oracle/oradata/ractest/log/redo04.log';

Database altered.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo05.log' to '/u01/oracle/oradata/ractest/log/redo05.log';

Database altered.

SQL> alter database rename file '/ocfs2/oradata/racdb/redo06.log' to '/u01/oracle/oradata/ractest/log/redo06.log';

Database altered.

SQL> alter database open resetlogs;

Database altered.

In case you want to create the online redo logs on a ASM diskgroup (+DATA for eg) for the clone/destination database, you may use below commands:

alter database rename file '/ocfs2/oradata/racdb/redo01.log' to '+DATA';
alter database rename file '/ocfs2/oradata/racdb/redo02.log' to '+DATA';
...

\10) Once the database is opened successfully, you may remove the redolog groups for redo threads of other instances

SQL> select THREAD#, STATUS, ENABLED
2 from v$thread;

THREAD# STATUS ENABLED

---

1 OPEN PUBLIC 2 CLOSED PRIVATE

1 2	1 OPEN  PUBLIC 2 CLOSED PRIVATE

SQL> select group# from v$log where THREAD#=2;

GROUP#
----------
4
5
6

SQL> alter database disable thread 2;

Database altered.

SQL> alter database drop logfile group 4;
alter database drop logfile group 4
*
ERROR at line 1:
ORA-00350: log 4 of instance racdb2 (thread 2) needs to be archived
ORA-00312: online log 4 thread 2: '/u01/oracle/oradata/ractest/log/redo04.log'

SQL> alter database clear unarchived logfile group 4;

Database altered.

SQL> alter database drop logfile group 4;

Database altered.

SQL> alter database drop logfile group 5;

Database altered.

SQL> alter database drop logfile group 6;

Database altered.

SQL> select THREAD#, STATUS, ENABLED from v$thread;

THREAD# STATUS ENABLED

---

1 OPEN PUBLIC

1	1 OPEN  PUBLIC

\11) Now you can remove the undo tablespaces of other instances and create a new temporary tablespace to complete the activity.

SQL> sho parameter undo;

NAME TYPE VALUE

---

undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
SQL>
SQL>
SQL> select tablespace_name from dba_tablespaces where contents='UNDO';

TABLESPACE_NAME
------------------------------
UNDOTBS1
UNDOTBS2

SQL> drop tablespace UNDOTBS2 including contents and datafiles;

Tablespace dropped.

SQL> select name from v$tempfile;

NAME
--------------------------------------------------------------------------------
/ocfs2/oradata/racdb/temp01.dbf

SQL> select tablespace_name from dba_tablespaces where contents='TEMPORARY';

TABLESPACE_NAME
------------------------------
TEMP

SQL> create temporary tablespace TEMP1
2 tempfile '/u01/oracle/oradata/ractest/data/temp01.dbf'
3 size 50M;

Tablespace created.

SQL> alter database default temporary tablespace TEMP1;

Database altered.

SQL> drop tablespace TEMP including contents and datafiles;

Tablespace dropped.

REFERENCES

NOTE:1146703.1 - Rman Restore From RAC ASM To Single Instance Non ASM Fails With ORA-00600 [kgeade_is_0]

相关文章

• Oracle rac数据库的备份和恢复
• 客户某套Oracle rac业务库出现严重的library cache等待排查
• Oracle 23ai介绍（含docker和单机安装）
• Oracle中的ora.oc4j、ora.qosmserver服务
• Oracle Database 23c免费开发者版单机安装
• Oracle RAC中remote_listener和local_listener的作用是什么？
• Oracle rac不能监听public ip
• Oracle rac 修改SCAN IP信息
• [FATAL] [INS-06006] Passwordless SSH connectivity not set up between the following node(s): [rac2]
• 在Oracle 12c中，在RMAN方面有哪些增强的新特性？
• 快速静默安装Oracle rac集群软件和rac数据库以及Restart ASM环境脚本集合
• 快速静默安装配置Oracle 12c、18c、19c、21c等单机环境脚本集合
• Oracle之dbms_backup_restore包的使用
• Oracle只读数据文件备份和恢复
• Oracle单实例备份集恢复到RAC集群
• Oracle rac安装报错 multiple user has uid 0
• AIX系统安装Oracle11gR2 RAC
• AIX系统静默安装Oracle 11gR2 RAC
• RAC环境下主库丢失归档，备库DG的恢复过程
• 一步一步在RHEL6.5+VMware Workstation上搭建 Oracle 12cR1的rac集群环境详细教程