During RMAN DUPLICATE command, you might face this error message returned by RMAN.
C:\Users\administrator>rman target sys/pass11g@pri auxiliary sys/pass11g@aux
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Sep 9 12:35:18 2015
connected to target database: PROD (DBID=3343192461)
connected to auxiliary database: STBY (not mounted)
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 09-SEP-15
using channel ORA_AUX_DISK_1
contents of Memory Script:
{
backup as copy reuse
targetfile 'd:\oracle\11203\DB\DATABASE\PWDprod1.ORA' auxiliary format
'd:\oracle\11203\DB\DATABASE\PWDprod2.ORA' ;
}
executing Memory Script
Starting backup at 09-SEP-15
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=695 instance=opera1 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/09/2015 12:41:29
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/09/2015 12:41:28
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
ORA-17629: Cannot connect to the remote database server
|
It actually means that TNS service at the primary database host is not properly configured to connect with the AUXTILIARY database specified in the connect string in above command block (C:\Users\administrator>rman target sys/pass11g@pri auxiliary sys/pass11g@aux). You should make sure that “aux” TNS service is properly configured at the primary site and you can connect with the auxiliary instance using this TNS service. For further details on. error ORA-12154, see this document
Thanks, very much I forgot to configure tns entry for the dr database on the primary and faced this issue. Your blog helped to resolve the issue.
ReplyDelete