by Whenever a structural change is made on the primary, attempts to resync from the primary using db_unique_name during the standby RMAN backups, it fails with following error.
Db-unique-name for all databases participating in the Data Guard configuration has been configured.
|
1 2 3 4 5 6 7 8 9 10 11 12 |
RMAN> resync catalog; starting partial resync of recovery catalog ORA-20079: full resync from primary database is not done doing automatic resync from primary resyncing from database with DB_UNIQUE_NAME FSPRD_OGG RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of resync command on default channel at 01/24/2018 10:22:01 ORA-17629: Cannot connect to the remote database server ORA-17627: ORA-00942: table or view does not exist |
RMAN is trying to implicitly resync from the Primary using db_unique_name as it is aware that structural changes have been made. 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 is to use a TNS connect string when connecting to the standby.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
/home/oracle:>rman target sys/test_12@FSTST_STDBY catalog rcat/Test_cat12@rcat Recovery Manager: Release 12.1.0.2.0 - Production on Wed Jan 24 10:14:25 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. connected to target database: FSTST (DBID=11395890285) connected to recovery catalog database RMAN> resync catalog from db_unique_name FSTST_STDBY; starting partial resync of recovery catalog ORA-20079: full resync from primary database is not done doing automatic resync from primary resyncing from database with DB_UNIQUE_NAME FSTST_PRIMY RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of resync from db_unique_name command on default channel at 01/24/2018 10:15:06 RMAN-20051: datafile resync not completed |
Now I am getting datafile resync error. This is due to “Bug 20848335” and workaround is:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
# Query the standby database for datafiles with the AUX_NAME='UNKNOWN'; CDB$ROOT@FSTST> select file# from v$datafile where aux_name='UNKNOWN'; FILE# ---------- 200 # For each datafile reported above, execute the following command on the standby. CDB$ROOT@FSTST> execute sys.dbms_backup_restore.setDatafileAux(200,null); PL/SQL procedure successfully completed. CDB$ROOT@FSTST> commit; # Now Resync RMAN> resync catalog from db_unique_name FSTST_STDBY; starting full resync of recovery catalog full resync complete |
Mandy!!!
Reference:
Known Issues with RMAN Oracle12c Catalog (Doc ID 2039848.1)
Leave a Reply