I shall be discussing/sharing various Data Guard configuration issues that we confronted during our extensive DR setup and testing at our premises.
=========
rman target / auxiliary sys/password@standby_tns
channel ORA_DISK_1: SID=97 instance=NEPRD1 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 18:16:51
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 05/14/2013 18:16:51
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied <<<>>>>
ORA-17629: Cannot connect to the remote database server
Cause:
The above issue is likely to be hit when you initiate an active database duplication command on 11gR2 or higher RAC database while setting-up a standby RAC database.
Workaround:
Ensure you used a TNS that is static to a particular instance of the RAC database while connecting to the source database. As shown below:
rman target sys/password@TNS auxiliary sys/password@standby_tns
--TNS must be configured to instance, no service with multiple instances (load balancing) should be used.
ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
In case the above error is confronted in the place of ORA-17627:ORA-01017, you there need to ensure that the database doesn't configured with SCAN LISTENER. If so, create a temporary listener, and ensure you use the TNS pointing to the the listener to avoid the issue.
===
=========
rman target / auxiliary sys/password@standby_tns
channel ORA_DISK_1: SID=97 instance=NEPRD1 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 18:16:51
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 05/14/2013 18:16:51
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied <<<>>>>
ORA-17629: Cannot connect to the remote database server
Cause:
The above issue is likely to be hit when you initiate an active database duplication command on 11gR2 or higher RAC database while setting-up a standby RAC database.
Workaround:
Ensure you used a TNS that is static to a particular instance of the RAC database while connecting to the source database. As shown below:
rman target sys/password@TNS auxiliary sys/password@standby_tns
--TNS must be configured to instance, no service with multiple instances (load balancing) should be used.
ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
In case the above error is confronted in the place of ORA-17627:ORA-01017, you there need to ensure that the database doesn't configured with SCAN LISTENER. If so, create a temporary listener, and ensure you use the TNS pointing to the the listener to avoid the issue.
===
No comments:
Post a Comment