处理 Dataguard 与 rman RMAN-05501

Dataguard 备库恢复时报rman-05501

RMAN>  duplicate target database for standby;

Starting Duplicate Db at 09-JUN-15

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=345 device type=DISK

contents of Memory Script:

{

restore clone standby controlfile;

}

executing Memory Script

Starting restore at 09-JUN-15

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: restoring control file

channel ORA_AUX_DISK_1: copied control file copy

input file name=/u01/oradata_backup/full_backup/db.ctl

output file name=/opt/oracle/database/oradata/db/control01.ctl

output file name=/opt/oracle/database/fast_recovery_area/db/control02.ctl

Finished restore at 09-JUN-15

contents of Memory Script:

{

sql clone ‘alter database mount standby database‘;

}

executing Memory Script

sql statement: alter database mount standby database

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 06/09/2015 16:54:16

RMAN-05501: aborting duplication of target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f18.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f17.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f16.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f15.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f14.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f13.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f12.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f11.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f10.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f09.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f08.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f07.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f06.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f05.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f04.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/warehouse_f05.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/warehouse_f04.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/warehouse_f03.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/warehouse_f02.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/warehouse_f01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f03.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f02.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/adv_ts_main_f01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/users01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/undotbs01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/sysaux01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name /opt/oracle/database/oradata/db/system01.dbf conflicts with a file used by the target database

原因：

主库和备库的datafile目录一样，且在初始化参数中没有添加 *.db_file_name_convert和*.log_file_name_convert两个参数。所以在这里duplicate 时需要加上 nofilenamecheck;

SQL> shutdown immediate;

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

SQL> startup pfile=‘/u01/oradata_backup/standby.pfile‘ nomount;

ORACLE instance started.

Total System Global Area 3.1935E+10 bytes

Fixed Size                  2268992 bytes

Variable Size            2.8119E+10 bytes

Database Buffers         3758096384 bytes

Redo Buffers               55840768 bytes

SQL> create spfile=‘/opt/oracle/database/product/11.2.0/db_1/dbs/initdkhlstd.ora‘ from pfile=‘/u01/oradata_backup/standby.pfile‘;

File created.

[[email protected] ~]$ rman target sys/[email protected]  auxiliary /

Recovery Manager: Release 11.2.0.4.0 - Production on Tue Jun 9 17:03:10 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: db (DBID=4232991297)

connected to auxiliary database: db (not mounted)

RMAN>  duplicate target database for standby nofilenamecheck;

Starting Duplicate Db at 09-JUN-15

using target database control file instead of recovery catalog

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=296 device type=DISK

contents of Memory Script:

{

restore clone standby controlfile;

}

executing Memory Script

Starting restore at 09-JUN-15

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: restoring control file

channel ORA_AUX_DISK_1: copied control file copy

input file name=/u01/oradata_backup/full_backup/db.ctl

output file name=/opt/oracle/database/oradata/db/control01.ctl

output file name=/opt/oracle/database/fast_recovery_area/db/control02.ctl

Finished restore at 09-JUN-15

contents of Memory Script:

{

sql clone ‘alter database mount standby database‘;

}

executing Memory Script

sql statement: alter database mount standby database

contents of Memory Script:

{

set newname for tempfile  1 to

"/opt/oracle/database/oradata/db/temp01.dbf";

switch clone tempfile all;

set newname for datafile  1 to

"/opt/oracle/database/oradata/db/system01.dbf";

set newname for datafile  2 to

"/opt/oracle/database/oradata/db/sysaux01.dbf";

set newname for datafile  3 to

"/opt/oracle/database/oradata/db/undotbs01.dbf";

set newname for datafile  4 to

"/opt/oracle/database/oradata/db/users01.dbf";

set newname for datafile  5 to

"/opt/oracle/database/oradata/db/adv_ts_main_f01.dbf";

set newname for datafile  6 to

"/opt/oracle/database/oradata/db/adv_ts_main_f02.dbf";

set newname for datafile  7 to

"/opt/oracle/database/oradata/db/adv_ts_main_f03.dbf";

set newname for datafile  8 to

"/opt/oracle/database/oradata/db/warehouse_f01.dbf";

set newname for datafile  9 to

"/opt/oracle/database/oradata/db/warehouse_f02.dbf";

set newname for datafile  10 to

"/opt/oracle/database/oradata/db/warehouse_f03.dbf";

set newname for datafile  11 to

"/opt/oracle/database/oradata/db/warehouse_f04.dbf";

set newname for datafile  12 to

"/opt/oracle/database/oradata/db/warehouse_f05.dbf";

set newname for datafile  13 to

"/opt/oracle/database/oradata/db/adv_ts_main_f04.dbf";

set newname for datafile  14 to

"/opt/oracle/database/oradata/db/adv_ts_main_f05.dbf";

set newname for datafile  15 to

"/opt/oracle/database/oradata/db/adv_ts_main_f06.dbf";

set newname for datafile  16 to

"/opt/oracle/database/oradata/db/adv_ts_main_f07.dbf";

set newname for datafile  17 to

"/opt/oracle/database/oradata/db/adv_ts_main_f08.dbf";

set newname for datafile  18 to

"/opt/oracle/database/oradata/db/adv_ts_main_f09.dbf";

set newname for datafile  19 to

"/opt/oracle/database/oradata/db/adv_ts_main_f10.dbf";

set newname for datafile  20 to

"/opt/oracle/database/oradata/db/adv_ts_main_f11.dbf";

set newname for datafile  21 to

"/opt/oracle/database/oradata/db/adv_ts_main_f12.dbf";

set newname for datafile  22 to

"/opt/oracle/database/oradata/db/adv_ts_main_f13.dbf";

set newname for datafile  23 to

"/opt/oracle/database/oradata/db/adv_ts_main_f14.dbf";

set newname for datafile  24 to

"/opt/oracle/database/oradata/db/adv_ts_main_f15.dbf";

set newname for datafile  25 to

"/opt/oracle/database/oradata/db/adv_ts_main_f16.dbf";

set newname for datafile  26 to

"/opt/oracle/database/oradata/db/adv_ts_main_f17.dbf";

set newname for datafile  27 to

"/opt/oracle/database/oradata/db/adv_ts_main_f18.dbf";

restore

clone database

;

}

executing Memory Script

......

RMAN>

RMAN> exit

Recovery Manager complete.

时间： 2024-08-02 10:55:30

处理 Dataguard 与 rman RMAN-05501的相关文章

搭建Dataguard，使用RMAN还原数据时无法连接ASM实例

报错如下: RMAN> restore standby controlfile from '/tmp/rman_backup/standby_0dss6ds7_1_1.ctl'; Starting restore at 2018/02/26 14:18:35 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=21

通过RMAN创建dataguard(原创)

通过RMAN创建dataguard(原创) 环境介绍:数据库版本10G,两个节点分别是rednum1(192.168.212.128)和rednum2(192.168.212.130)主库主机名称是rednum1,从库主机名称是rednum2配置步骤如下:1.在主库和从库配置tnsnames如下:standbydb1 =(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = rednum1)(PORT = 1521))(CONNECT_DATA =(SE

Oracle 11g R2 rac通过rman 恢复到单实例数据库

生产环境是2个节点的rac + dataguard(物理备库也是两个节点的rac),通过rman每天进行备份,现在需要定期对生产库进行恢复操作 恢复步骤如下: 1.      把生产库的备份拷贝到目标端 建立存放备份的目录修改目录属主属组 mkdir /oracle/backup chown oracle:oinstall /oracle/backup 2.      拷贝备份到目标端 scp -P 22 incremental_level*  [email protected]:/oracle

rman还原数据库数据库报错问题处理

报错1.数据库开启block change tracking ,恢复完成后打开因文件不存在报错. RMAN> alter database open resetlogs; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ========

RMAN备份各种物理文件

RMAN运行脚本的方式:RMAN TARGET / @backup_db.rmanRMAN TARGET / cmdfile=backup_db.rman在RMAN中执行操作系统中保存的脚本:RMAN> @backup_db.rman运行存储在catalog中的脚本(需要首先为RMAN创建恢复目录)RMAN> RUN{EXCUTE SCRIPT backup_file_whole_db} 只要数据库处于加载状态,无论数据库能否打开工,都可以在RMAN中对表空间进行备份.=========RMA

Oracle 10.2.0.5 RMAN迁移并升级11.2.0.4一例

一.环境介绍 1. 源数据库环境 操作系统版本: OEL 5.4 x64数据库版本  : 10.2.0.5 x64数据库sid名 : orcl Oracle 10g 10.2.0.5(64bit)安装目录如下: 数据库软件:/u01/app/oracle/product/10.2.0/db_1数据库文件:/u01/app/oracle/oradata/orcl 归档目录:/u01/archivelog RMAN目录:/backup/dbbak/orabak 背景:一个老oracle10g数据库,

创建RMAN备份 恢复目录数据库

这是前段时间给客户做的RMAN备份策略,今天有时间整理出来,希望对大家有些帮助,如有不对的地方欢迎大家给予指点,谢谢!   创建成恢复目录数据库 如果不是在本地配置RMAN 恢复目录, 在一台WINDOW2000电脑上安装ORACLE数据库,最好保证数据库版本与目标数据库的版本想同. 建立RMAN 数据库用户及表空间: RECOVER CATALOG 表空间(cattbs):1G系统表空间:       100MUNDO表空间:     100M临时表空间(TEMP):        100M 

【RMAN】利用备份片还原数据库（中）

[RMAN]利用备份片还原数据库 [RMAN]利用备份片还原数据库(上): http://blog.itpub.net/26736162/viewspace-1621581/ 在上一篇blog中我们介绍了采用dbms_backup_restore来找回控制文件并恢复整个数据库的方法,本篇blog我们介绍采用创建临时库来找回控制文件的方法. 1.1.1  方法二:尝试采用创建临时库来找回控制文件 由于RMAN必须工作在MOUNT模式,所有的数据文件都丢失,无法通过只重建控制文件将其启动到MOUNT

RMAN恢复测试

今天做RMAN恢复的测试,做恢复测试,必须在数据库有备份的前提下进行,样例中采用的是完全备份,模拟以下几种情况下的恢复: 1)数据库运行过程中数据文件全部丢失: 2)数据库运行过程中非关键数据文件丢失: 3)数据库运行过程中关键数据文件丢失: 4)联机重做日志文件/归档重做日志文件丢失(未测试): 5)增量备份下归档日志文件丢失(未测试): 在每个模拟中,都要做一次完全备份,上一个的完全备份可以给下一个模拟使用. 一.测试环境描述 系统版本:Red Hat Enterprise Linux Se