<<Back to Oracle Backup & Recovery Main Page
Doing automatic resync from primary
resyncing from database with DB_UNIQUE_NAME TEB
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
Cause:Some structural changes has been done at primary (eg datafile has been added) and backup is done from Standby.
RMAN is trying to implicitly resync from the Primary using db_unique_name as it is aware that structural changes have been made.However, RMAN is unable to connect to the primary because no connect string was used when connecting to the standby - in order to resync from another host in a Data Guard configuration , the connection to target must be made with a username, password and alias.
Solution:
Use a TNS connect string when connecting to the standby eg.
$rman target sys/password@stdby catalog rman/password@rcat
RMAN> resync catalog from db_unique_name Prim;
resyncing from database with DB_UNIQUE_NAME PRIM
starting full resync of recovery catalog
full resync complete
To do RMAN RESYNC from remote database we need to configure DB_UNIQUE_NAME in RMAN persistent configuration as below
RMAN>CONFIGURE DB_UNIQUE_NAME 'PRIM' CONNECT IDENTIFIER 'PRIM'; <= Primary DB
RMAN>CONFIGURE DB_UNIQUE_NAME 'STDBY' CONNECT IDENTIFIER 'STDBY'; <= Standby DB
Make sure that the connect string for PRIM and STDBY exists in $ORACLE_HOME/network/admin/tnsnames.ora file
Comments
Post a Comment