RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile canno

今天是2014-06-18。在复制数据的时候出现例如以下错误:

RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause

操作步骤例如以下:

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

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jun 18 13:24:33 2014

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

connected to target database: RHYS (DBID=2760870303)
connected to auxiliary database: DG2 (not mounted)

RMAN> 

RMAN> 

RMAN> 

RMAN> 

RMAN> run{
2>  allocate channel ch1 type disk;
3>  allocate channel ch2 type disk;
4>  allocate channel ch3 type disk;
5>  allocate channel ch4 type disk;
6>  allocate channel ch5 type disk;
7>  allocate channel ch6 type disk;
8>  allocate channel ch7 type disk;
9>  allocate auxiliary channel ch8 type disk;
10>  duplicate target database for standby from active database nofilenamecheck
11>  spfile
12>    parameter_value_convert ‘dg1‘,‘dg2‘
13>    set db_unique_name=‘dg2‘
14>    set db_recovery_file_dest=‘/u01/app/oracle/fast_recovery_area‘
15>    set DB_RECOVERY_FILE_DEST_SIZE=‘4G‘
16>    set control_files=‘/u01/app/oracle/oradata/dg/control01.ctl‘
17>    set db_create_file_dest=‘/u01/app/oracle/oradata/dg‘
18>    set db_create_online_log_dest_1=‘/u01/app/oracle/oradata/dg‘
19>    set log_archive_max_processes=‘5‘
20>    set fal_client=‘dg2‘
21>    set fal_server=‘dg1‘
22>    set standby_file_management=‘AUTO‘
23>    set log_archive_config=‘dg_config=(dg1,dg2)‘
24>    set log_archive_dest_1=‘location=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles)‘
25>    set log_archive_dest_2=‘service=dg1 lgwr sync valid_for=(online_logfiles,primary_role) db_unique_name=dg1‘;
26>     sql channel ch6 "alter system set log_archive_max_processes=5";
27>     sql channel ch7 "alter system set fal_client=dg1";
28>     sql channel ch7 "alter system set fal_server=dg2";
29>     sql channel ch5 "alter system set standby_file_management=AUTO";
30>     sql channel ch6 "alter system set log_archive_config=‘‘dg_config=(dg1,dg2)‘‘";
31>     sql channel ch7 "alter system set log_archive_dest_2=‘‘service=dg2 lgwr sync valid_for=(online_logfiles,primary_role) db_unique_name=dg2‘‘";
32>     sql channel ch6 "alter system set log_archive_dest_1=‘‘location=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles)‘‘";
33>     sql channel ch1 "alter system archive log current";
34>     sql channel ch8 "alter database recover managed standby database using current logfile disconnect from session";
35>  release channel ch1;
36>  release channel ch2;
37>  release channel ch3;
38>  release channel ch4;
39>  release channel ch5;
40>  release channel ch6;
41>  release channel ch7;
42>  release channel ch8;
43> }

using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=35 device type=DISK

allocated channel: ch2
channel ch2: SID=42 device type=DISK

allocated channel: ch3
channel ch3: SID=44 device type=DISK

allocated channel: ch4
channel ch4: SID=38 device type=DISK

allocated channel: ch5
channel ch5: SID=36 device type=DISK

allocated channel: ch6
channel ch6: SID=41 device type=DISK

allocated channel: ch7
channel ch7: SID=37 device type=DISK

allocated channel: ch8
channel ch8: SID=1 device type=DISK

Starting Duplicate Db at 18-JUN-14
released channel: ch1
released channel: ch2
released channel: ch3
released channel: ch4
released channel: ch5
released channel: ch6
released channel: ch7
released channel: ch8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/18/2014 13:24:43
RMAN-05501: aborting duplication of target database
RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause

RMAN> exit

问题处理。

将备库创建pfile文件,然后从pfile启动就可以。

[[email protected] dbs]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Wed Jun 18 13:25:03 2014

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

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> shutdown immediate;
ORA-01507: database not mounted

ORACLE instance shut down.
SQL>
SQL> create pfile=‘/home/oracle/pfile.ora‘ from spfile;

File created.

SQL> startup nomount pfile=‘/home/oracle/pfile.ora‘;
ORACLE instance started.

Total System Global Area  839282688 bytes
Fixed Size                  2257880 bytes
Variable Size             545262632 bytes
Database Buffers          289406976 bytes
Redo Buffers                2355200 bytes
SQL>
SQL> 
时间: 2024-10-27 13:17:42

RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile canno的相关文章

No Nios II target connection paths were located

NIOS II 运行应用程序Run as ->Nios II Hardware时出现错误: No Nios II target connection paths were located. Check connections and that a Nios II .sof is downloaded. 尝试点击Refresh Connections然后Apply可能会解决问题,如图:

Rman配置DataGuard using Backup-based duplication with a target connection with filesystem

一.  环境 主机名 数据库版本 dbname db_unique_name IP地址 系统版本 Jason1(主) oracle11204 Jason jason1 192.168.1.99 rhel6.6_x86_64 jason2(备) jason2 192.168.1.100 二.  主库配置 1.  确定主数据库开启强制LOGGING模式 [[email protected] ~]$ sqlplus /nolog SQL*Plus: Release 11.2.0.4.0 Product

HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node

In this Document APPLIES TO: Oracle Database - Enterprise Edition - Version 9.2.0.1 and laterInformation 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 loca

使用RMAN DUPLICATE...FROM ACTIVE DATABASE创建物理standby database

Applies to: Oracle Server - Enterprise Edition - Version 11.1.0.6 to 11.2.0.4 [Release 11.1 to 11.2]Information in this document applies to any platform.GoalStep by step guide on how to create a physical standby database using RMAN DUPLICATE FROM ACT

总结搭建Oracle11g DG踩的坑

此次的操作环境是Oracle11g 单实例,os为Linux,采用duplicate在线创建物理备库 primary上设置相关参数 ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(ora11g,stdb)';alter system set log_archive_dest_2='SERVICE=DB_DG2 lgwr async valid_for=(online_logfiles,primary_role) db_unique_name=std

Oracle11g 搭建单实例DataGuard (转载)

原文:http://blog.itpub.net/29324876/viewspace-1246133/ 环境:主备库都为单实例并且数据库SID相同 OS:red hat 6.5 Oracle:11.2.0.4.3 主库操作 1. 开启归档模式   创建归档目录 [[email protected] ~]# mkdir -p /u01/archivelog [[email protected] ~]# chown -R oracle:oinstall /u01/archivelog [[emai

Duplicate From Active Database

RMAN 'Duplicate From Active Database' Feature in 11G (文档 ID 452868.1) 转到底部 APPLIES TO: Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterInformation in this document applies to any platform. PURPOSE The scope of this bulletin is to dis

oracle 11g RMAN:Active Database Duplication for standby database 创建dg 命令解读

基于生产的duplicate 复制,如果事先没有手动配置pfile(设定内存,进程,dg相关配置参数,数据库相关路径参数)则会出现各种参数无法转换的问题: 因为duplicate 会从生产自动拷贝pfile,控制文件,密码文件过来,如果主库和备库环境不一样(数据库软件路径,数据文件存储路径) 如果没在duplicate的命令中完整指定新环境备库的各种参数涉及路径,及转换参数,就会默认使用从主库拷贝过来的spfile中的参数设置(会忽略oracle 自定义的的缺省配置:比如adr 缺省会放在ORA

【RMAN】RMAN-05001: auxiliary filename conflicts with the target database

oracle 11.2.0.4 运行以下脚本,使用活动数据库复制技术创建dataguard备库报错rman-005001: run{ duplicate target database for standby from active database spfile     set db_unique_name='dbkingstd'     set log_file_name_convert '/u01/app/oracle/oradata/dbking','/u01/app/oracle/or