RMAN之恢复控制文件

本文介绍了使用 Oracle RMAN 工具进行数据库全库备份、控制文件删除与恢复、数据库恢复及数据库打开的过程。通过具体步骤展示了如何在删除控制文件后利用备份文件恢复数据库。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

1.首先全库备份

RMAN> startup mount

connected to target database (not started)
Oracle instance started
database mounted

Total System Global Area    1653518336 bytes

Fixed Size                     2253784 bytes
Variable Size               1006636072 bytes
Database Buffers             637534208 bytes
Redo Buffers                   7094272 bytes

RMAN> backup database plus archivelog;


Starting backup at 15-MAR-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=24 RECID=1 STAMP=906583293
input archived log thread=1 sequence=25 RECID=2 STAMP=906583374
input archived log thread=1 sequence=26 RECID=3 STAMP=906587333
input archived log thread=1 sequence=27 RECID=4 STAMP=906587432
channel ORA_DISK_1: starting piece 1 at 15-MAR-16
channel ORA_DISK_1: finished piece 1 at 15-MAR-16
piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2016_03_15/o1_mf_annnn_TAG20160315T215123_cgj4tvdj_.bkp tag=TAG20160315T215123 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 15-MAR-16

Starting backup at 15-MAR-16
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/orcl/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: starting piece 1 at 15-MAR-16
channel ORA_DISK_1: finished piece 1 at 15-MAR-16
piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2016_03_15/o1_mf_nnndf_TAG20160315T215124_cgj4twt1_.bkp tag=TAG20160315T215124 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:26
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 15-MAR-16
channel ORA_DISK_1: finished piece 1 at 15-MAR-16
piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2016_03_15/o1_mf_ncsnf_TAG20160315T215124_cgj4xonx_.bkp tag=TAG20160315T215124 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 15-MAR-16

Starting backup at 15-MAR-16
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 15-MAR-16

RMAN> shutdown immediate

database dismounted
Oracle instance shut down

2.删除控制文件

[oracle@BD02 ~]$ cd /u01/app/oracle/fast_recovery_area/
[oracle@BD02 fast_recovery_area]$ ll
total 8
drwxr-x---. 2 oracle oinstall 4096 Mar 15 21:06 orcl
drwxr-x---. 5 oracle oinstall 4096 Mar 15 21:06 ORCL
[oracle@BD02 fast_recovery_area]$ cd orcl
[oracle@BD02 orcl]$ ls
control02.ctl
[oracle@BD02 orcl]$ mv control02.ctl control02.ctl.bak
[oracle@BD02 orcl]$ cd /u01/app/oracle/oradata/orcl/
[oracle@BD02 orcl]$ mv control01.ctl control01.ctl.bak

3.恢复控制文件

RMAN> restore controlfile from '/u01/app/oracle/fast_recovery_area/ORCL/backupset/2016_03_15/o1_mf_ncsnf_TAG20160315T215124_cgj4xonx_.bkp';

Starting restore at 15-MAR-16
using channel ORA_DISK_1

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/orcl/control01.ctl
output file name=/u01/app/oracle/fast_recovery_area/orcl/control02.ctl
Finished restore at 15-MAR-16

4.恢复数据库

RMAN> recover database;

Starting recover at 15-MAR-16
Starting implicit crosscheck backup at 15-MAR-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Crosschecked 2 objects
Finished implicit crosscheck backup at 15-MAR-16

Starting implicit crosscheck copy at 15-MAR-16
using channel ORA_DISK_1
Finished implicit crosscheck copy at 15-MAR-16

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2016_03_15/c-1434005102-20160315-01

using channel ORA_DISK_1

starting media recovery

archived log for thread 1 with sequence 1 is already on disk as file /u01/app/oracle/oradata/orcl/redo01.log
archived log file name=/u01/app/oracle/oradata/orcl/redo01.log thread=1 sequence=1
media recovery complete, elapsed time: 00:00:00
Finished recover at 15-MAR-16

5.打开数据库

这里得用resetlogs打开,不过通过重建控制文件就可以不用resetlogs了。

RMAN> alter database open resetlogs;

database opened

<think>嗯,用户需要查找在Oracle 11g RAC环境下使用RMAN恢复控制文件的方法或教程。让我先理清楚RMAN恢复控制文件的基本步骤,然后考虑RAC环境的特殊性。 首先,RMAN恢复控制文件通常需要从自动备份中恢复控制文件在RAC中可能存储在每个节点的共享存储上。记得在RAC中,控制文件是共享的,所以恢复时需要注意所有节点都能访问到恢复后的控制文件。 接下来,用户提供的引用中有提到从备份文件恢复控制文件的命令,例如`restore controlfile from '/rmanbackup/orcl_full_19ra5tlf_1_1'`。这说明用户可能已经有备份文件的位置,但需要具体步骤。在RAC环境中,可能需要先关闭所有实例,或者启动到nomount状态。因为RAC涉及多个实例,恢复控制文件时要确保只有一个节点执行恢复操作,其他节点可能处于关闭状态。 另外,引用[2]提到将initorcl.ora文件复制到单机环境,可能涉及到参数文件的配置。在RAC中,参数文件可能需要指向共享存储,或者需要调整初始化参数以适应集群环境。恢复控制文件后,可能需要重建控制文件的多个副本,确保每个节点都能访问到正确的控制文件。 用户还提到了权限问题,如`chmod u+x`给脚本执行权限,这可能意味着在恢复过程中需要执行某些脚本,或者在执行RMAN命令时需要注意权限设置。此外,RMAN资料库的元数据(引用[4])是关键,恢复控制文件后可能需要同步这些信息。 需要验证的步骤包括:确认备份文件的存在和可访问性,启动实例到nomount状态,执行restore命令,然后挂载数据库并进行恢复。在RAC中,可能需要使用srvctl命令来管理实例的状态,比如停止所有节点上的资源,再在其中一个节点执行恢复。 还有可能遇到的问题是,如果控制文件备份是在RAC环境下进行的,恢复时是否需要特别注意备份的位置和节点的配置?比如备份文件是否存放在共享存储上,所有节点都能访问到。此外,恢复后的控制文件是否需要复制到所有节点的正确路径下,或者因为使用的是共享存储,自动完成同步? 最后,根据用户提供的引用,可能需要将参数文件控制文件等正确配置到单机或RAC环境中,确保路径和权限正确。因此,在回答中需要分步骤说明,并强调RAC环境下的注意事项,如共享存储、多实例协调等。</think>在Oracle 11g RAC环境下使用RMAN恢复控制文件的步骤如下: ### 一、准备工作 1. **确认备份有效性** 检查RMAN备份文件路径是否有效,例如: ```bash ls -l /rmanbackup/orcl_full_19ra5tlf_1_1 ``` 确保文件权限正确(参考`chmod u+x`命令设置权限[^3])。 2. **关闭所有实例** 在RAC环境中需先停止所有节点实例: ```bash srvctl stop database -d <db_name> ``` --- ### 二、恢复控制文件 1. **启动到NOMOUNT状态** 在**一个节点**上执行: ```sql SQL> startup nomount; ``` 2. **执行RMAN恢复命令** 使用备份文件恢复控制文件: ```sql RMAN> restore controlfile from '/rmanbackup/orcl_full_19ra5tlf_1_1'; ``` 成功后提示`Control File restored`[^1]。 3. **挂载数据库** ```sql SQL> alter database mount; ``` --- ### 三、后续操作 1. **恢复数据库并应用日志** ```sql RMAN> recover database; RMAN> alter database open resetlogs; ``` 2. **同步RAC环境** 确保控制文件在共享存储中,重启所有节点: ```bash srvctl start database -d <db_name> ``` --- ### 注意事项 - **参数文件配置**:检查`initorcl.ora`等参数文件路径是否指向共享存储[^2]。 - **RMAN资料库**:恢复后验证元数据一致性[^4]。 - **备份位置**:在RAC中需确保所有节点可访问备份文件路径。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值