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

Hi,

Sometimes You can get “RMAN-20079: full resync from primary database is not done ” error.

 

Details of error are as follows.

RMAN-20079: full resync from primary database is not done
Cause: Resync from standby detected that a full resync from primary database is required.
One of the following events on primary database may have caused this error:
1) one or more tablespaces or datafiles were added
2) one or more tablespaces or datafiles were dropped
3) one or more datafiles status changed
Action: Perform full resync after connecting to primary database.

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

Doing automatic resync from primary
resyncing from database with DB_UNIQUE_NAME < db unique name>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/30/2020 23:11:00
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 04/30/2020 23:11:00
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist





This error is related with the  TNS connect string when connecting to the standby.

This error is related with the Primary Database TNS Alias. Because MSDB is primary and MSDBDG is Standby side.
$ rman target / catalog <username>/<password>@<catalog tns>
RMAN> resync catalog from db_unique_name MSDB;

resyncing from database with DB_UNIQUE_NAME MSDB
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync from db_unique_name command on default channel at 04/30/2020 15:29:39
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-03113: end-of-file on communication channel
ORA-17629: Cannot connect to the remote database server

 

Use the Standby TNS Alias instead of Primary Alias. To solve this error, use the Standby TNS Alias as follows.

 

$ rman target <username>/<password>@MSDBDG catalog <username>/<password>@<catalog tns>

RMAN> resync catalog from db_unique_name MSDB;

resyncing from database with DB_UNIQUE_NAME MSDB
starting full resync of recovery catalog
full resync complete

Do you want to learn more details about RMAN, then read the following articles.

https://ittutorial.org/rman-backup-restore-and-recovery-tutorials-for-beginners-in-the-oracle-database/

 

 363 views last month,  8 views today

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience. I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource. I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks. I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients. If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress mehmetsalih.deveci@outlook.com. -                                                                                                                                                                                                                                                 - Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  mehmetsalih.deveci@outlook.com a mail atabilirsiniz.

Check Also

ORA-01438: value larger than specified precision allowed for this column

Hi, I got ” ORA-01438: value larger than specified precision allowed for this column” error …

Leave a Reply