ORA-20079: full resync from primary database is not done

When we added new files in primary database sometime below errors raise in Stand by database while RMAN
backup is running.

RMAN backups are run from Standby server.  Whenever a structural change is made on the primary , attempts to resync from the primary using db_unique_name  during the standby backup fails:

ORA-20079: full resync from primary database is not done

doing automatic resync from primary
resyncing from database with DB_UNIQUE_NAME testdb

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 08/23/2014 22:45:24
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 08/23/2014 22:45:24
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist

Files have been added at the Primary site

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

Primary: testdb
standby: testdb123

$ rman target  sys/test123@testdb123 catalog rman/rman@rcat
RMAN> resync catalog from db_unique_name testdb;
resyncing from database with DB_UNIQUE_NAME testdb
starting full resync of recovery catalog
full resync complete



Now you can run RMAN backup.