rac不完全恢复

不完全恢复

rac修改归档模式
SQL> select log_mode from v$database;

LOG_MODE
------------
NOARCHIVELOG

[[email protected] ~]$ srvctl stop database -d zhaoja
[[email protected] ~]$ export ORACLE_SID=zhaoja1
[[email protected] ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Sat Dec 20 17:46:06 2014

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1610612736 bytes
Fixed Size 2280840 bytes
Variable Size 416100984 bytes
Database Buffers 1157627904 bytes
Redo Buffers 34603008 bytes
Database mounted.
SQL> alter database archivelog;

Database altered.

SQL> alter database open;

Database altered.

SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 2
Next log sequence to archive 3
Current log sequence 3
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
[[email protected] ~]$ srvctl start database -d zhaoja
在两个节点查看是否归档。
SQL> archive log list;

1、进行全备份
控制文件自动备份打开
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored

SQL> select name from v$archived_log;

[[email protected] ~]$ rman target /

Recovery Manager: Release 10.2.0.4.0 - Production on Sat Dec 20 18:26:52 2014

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

connected to target database: ZHAOJA (DBID=3729713493)

RMAN> backup database;

2、查看删除的文件列表,包括数据文件、联机日志、控制文件

SQL>
select name from v$controlfile
union
select name from v$datafile
union
select member name from v$logfile;

NAME
--------------------------------------------------------------------------------
+DATA/zhaoja/controlfile/current.283.866833499
+DATA/zhaoja/datafile/sysaux.296.866833451
+DATA/zhaoja/datafile/system.256.866833451
+DATA/zhaoja/datafile/undotbs1.301.866833451
+DATA/zhaoja/datafile/undotbs2.289.866833523
+DATA/zhaoja/datafile/users.303.866833451
+DATA/zhaoja/onlinelog/group_1.299.866833501
+DATA/zhaoja/onlinelog/group_2.300.866833501
+DATA/zhaoja/onlinelog/group_3.304.866833561
+DATA/zhaoja/onlinelog/group_4.305.866833561

10 rows selected.

3、关闭两个实例
SQL> shutdown abort;
ORACLE instance shut down.

4、删除数据文件、联机日志、控制文件
[[email protected] ~]$ export ORACLE_SID=+ASM2
[[email protected] ~]$ asmcmd -p
ASMCMD [+] > cd +DATA/
ASMCMD [+DATA] > ls
RAC/
TEST/
ZHAOJA/
ASMCMD [+DATA] > cd zhaoja
ASMCMD [+DATA/zhaoja] > ls
CONTROLFILE/
DATAFILE/
ONLINELOG/
PARAMETERFILE/
TEMPFILE/
spfilezhaoja.ora
ASMCMD [+DATA/zhaoja] > cd controlfile
ASMCMD [+DATA/zhaoja/controlfile] > ls
Current.283.866833499
ASMCMD [+DATA/zhaoja/controlfile] > rm Current.283.866833499
ASMCMD [+DATA/zhaoja/controlfile] > cd +DATA/zhaoja/datafile
ASMCMD [+DATA/zhaoja/datafile] > ls
SYSAUX.296.866833451
SYSTEM.256.866833451
UNDOTBS1.301.866833451
UNDOTBS2.289.866833523
USERS.303.866833451
ASMCMD [+DATA/zhaoja/datafile] > rm *
You may delete multiple files and/or directories.
Are you sure? (y/n) y
ASMCMD [+data/zhaoja] > cd onlinelog
ASMCMD [+data/zhaoja/onlinelog] > ls
group_1.303.866830489
group_2.301.866830489
group_3.296.866830551
group_4.256.866830551
ASMCMD [+data/zhaoja/onlinelog] > rm *
You may delete multiple files and/or directories.
Are you sure? (y/n) y

5、首先从自动备份中恢复控制文件,在某个实例上执行:
[[email protected] admin]$ sqlplus / as sysdba

SQL> startup nomount;
ORACLE instance started.

Total System Global Area 1610612736 bytes
Fixed Size 2280840 bytes
Variable Size 416100984 bytes
Database Buffers 1157627904 bytes
Redo Buffers 34603008 bytes

6、从rman备份中恢复控制文件
RMAN> set dbid=3729716506

executing command: SET DBID

RMAN> restore controlfile from autobackup;

Starting restore at 20-DEC-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 instance=zhaoja1 devtype=DISK

channel ORA_DISK_1: looking for autobackup on day: 20141220
channel ORA_DISK_1: autobackup found: c-3729716506-20141220-00
channel ORA_DISK_1: control file restore from autobackup complete
output filename=+DATA/zhaoja/controlfile/current.305.866835965
Finished restore at 20-DEC-14

7、挂载数据库
RMAN> sql ‘alter database mount‘;

sql statement: alter database mount
released channel: ORA_DISK_1

8、恢复数据文件
RMAN> restore database;

9、查看控制文件中的归档日志记录
SQL> select name from v$archived_log;

SQL> recover database using backup controlfile until cancel;

RMAN>
run {
set until scn 617834;
restore database;
recover database;
}

以resetlogs方式打开数据库
RMAN>
sql ‘alter database open resetlogs‘;

打开其他实例

srvctl start database -d zhaoja

srvctl status database -d zhaoja

时间: 2024-08-02 03:14:07

rac不完全恢复的相关文章

rac完全恢复学习

1.查看现有数据库文件 SQL> select name from v$datafile; NAME -------------------------------------------------------------------------------- +DATA/rac/datafile/system.259.866566403 +DATA/rac/datafile/undotbs1.260.866566407 +DATA/rac/datafile/sysaux.261.866566

RAC/single 异机完全恢复(RMAN)

注意:最好应用停止做以下操作环境:A库单实例或RAC 文档中为单实例B库安装软件.监听即可 1.Rman全备A数据库create pfile=''C:\Users\Administrator\Desktop\file\pfile.ora'' from spfileRMAN> backup database format='C:\Users\Administrator\Desktop\file\full_%U%T.bak'; 启动 backup 于 20-2月 -20使用通道 ORA_DISK_1

Oracle 11g单实例RMAN恢复到Oracle 11g RAC

一.环境说明 操作系统版本: RHEL 6.5 x64 1. 源数据库服务器 Oracle版本: Oracle 11g 11.2.0.4 64位(单机)Oracle_SID: orcl db_name   : orcl 背景:一台生产oracle10g(10.2.0.5)数据库计划迁移到Oracle 11.2.0.4.0 RAC.1) 先oracle10g(10.2.0.5)升级到Oracle 11.2.0.4(过程略)2)再Oracle 11.2.0.4单实例迁移到Oracle 11.2.0.

rac 11g_生产库日志组损坏处理

原创作品,出自 "深蓝的blog" 博客,转载时请务必注明出处,否则有权追究版权法律责任. 深蓝的blog:http://blog.csdn.net/huangyanlong/article/details/46863813 环境: 操作系统:CentOS 6.4 64bit 中间件:WAS 7 数据库:Oracle 11G RAC 11.2.0.3 问题: 生成库was无法连接数据库,报出数据库无法归档错误. 解决思路: 解决oracle无法归档问题. 操作记录: SQL> s

RAC 之 RMAN 恢复

RAC 下的RMAN 讲究的是备份和还原的策略要一致.备份策略的不同,会导致备份结果的分步不同,进而影响恢复的策略和步骤.一般情况下,恢复策略和备份策略必须是对应的.如果备份策略进行了修改,那么恢复也应该采用相同的策略.之前我们的RMAN 备份参考: RAC 之 RMAN 备份 http://blog.csdn.net/tianlesoftware/archive/2010/09/22/5901053.aspx 这里面有2个注意事项: 1.       执行恢复的节点要能看到所有节点的归档文件.

RAC之RMAN恢复

之前整理的RMAN 有关还原的文章: RMAN 系列(五) ---- RMAN 还原 与 恢复 http://blog.csdn.net/tianlesoftware/archive/2010/07/11/5700474.aspx RMAN 备份与恢复 实例 http://blog.csdn.net/tianlesoftware/archive/2009/10/20/4699320.aspx Oracle Rman跨resetlogs版本恢复 http://blog.csdn.net/tianl

[翻译自mos文章]不完全恢复之后,open resetlogs之前,怎么快速的检查数据库是否处于一致性的状态?

不完全恢复之后,open resetlogs之前,怎么快速的检查数据库是否处于一致性的状态? 翻译自: How to quickly check that Database is consistent after incomplete recovery (Point in Time Recovery) before OPEN RESETLOGS (Doc ID 1354256.1) 适用于: Oracle Database - Enterprise Edition - Version 9.0.1

Oracle RAC学习笔记:基本概念及入门

2010年04月19日 10:39 来源:书童的博客 作者:书童 编辑:晓熊 [技术开发 技术文章]    oracle 10g real application clusters introduction     1.什么是cluster     一个cluster是由两个或是多个独立的.通过网络连接的servers组成的.几个硬件供应商多年以来提供了Cluster性能的各种需求.一些Clusters仅仅为了提供高可用性的,在当前活动的node发生故障时转移到次节点node.另一些是为了提供分

大话RAC介质恢复---只有备份文件的恢复

场景:Oracle 10g RAC:数据文件.控制文件.联机日志.参数文件都使用ASM,归档到ASM.完整备份后,删除所有控制文件.联机日志.数据文件:最后利用备份进行不完全恢复. 1.模拟灾难场景(略) 2.恢复步骤 1.将数据库启动到nomount状态 SQL>startup nomount 2.用RMAN从自动备份中恢复控制文件,在某个实例中执行 RMAN>restore controfile from '存储备份文件的备份集'; 3.挂载数据库 RMAN>sql'alter da