Linux环境下oracle数据库Rman备份异机恢复

原创

wuhui66 2018-01-08 11:39:38 博主文章分类：oracle数据迁移 ©著作权

文章标签 oracle rman 备份恢复 文章分类 Oracle 数据库

©著作权归作者所有：来自51CTO博客作者wuhui66的原创作品，请联系作者获取转载授权，否则将追究法律责任

备份的数据库和要恢复的数据库OS和数据库的版本均一致，恢复的目录也均一致！备份数据库： RMAN> backup format ‘/home/oracle/scripts/full_prod.%U’ database plus archivelog; 备份控制文件： RMAN> backup current CONTROLFILE format '/home/oracle/scripts/control.%U'; 确认所有文件夹路径，备库最好要创建和源库一样的路径，否则需要指定路径。 SYS@PROD> select name from v$datafile; SYS@PROD> select member from v$logfile; SYS@PROD> select name from v$controlfile; 传输spfile到要恢复的服务器 [oracle@wangxx1 dbs]$ scp spfilePROD.ora 172.16.12.117:/u01/app/oracle/product/11.2.0/dbhome_1/dbs SYS@PROD> create pfile from spfile; 根据pfile文件位置创建相应的目录 [oracle@wangxx2 ~]$ mkdir -p /u01/app/oracle/oradata/PROD/ [oracle@wangxx2 dbs]$ mkdir -p /u01/app/oracle/admin/PROD/adump 传输备份文件到相同位置 [oracle@wangxx1 scripts]$ scp full* 172.16.12.117:/home/oracle/scripts [oracle@wangxx1 scripts]$ scp control* 172.16.12.117:/home/oracle/scripts 从指定备份集恢复控制文件 [oracle@wangxx2 scripts]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Mon Jan 8 10:14:24 2018 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: PROD (not mounted) RMAN> set DBID=358601116 RMAN> restore CONTROLFILE from '/home/oracle/scripts/control.07so5c0l_1_1'; Starting restore at 08-JAN-18 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=10 device type=DISK

channel ORA_DISK_1: restoring control file channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 output file name=/u01/app/oracle/oradata/PROD/control01.ctl output file name=/u01/app/oracle/oradata/PROD/control02.ctl Finished restore at 08-JAN-18 RMAN> restore database; RMAN> recover database; Starting recover at 08-JAN-18 using channel ORA_DISK_1 using channel ORA_DISK_2

starting media recovery

RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 01/08/2018 11:23:34 RMAN-06053: unable to perform media recovery because of missing log RMAN-06025: no backup of archived log for thread 1 with sequence 49 and starting SCN of 2002997 found to restore 报错属于正常，因为联机日志没有拷贝过来！ RMAN> alter database open resetlogs; database opened SYS@PROD> select status from v$instance;