// // ORA-16047: DGID mismatch between destination setting and target database

A technical troubleshooting blog about Oracle with other Databases & Cloud Technologies.

ORA-16047: DGID mismatch between destination setting and target database

2 min read

Issue : ORA-16047: DGID mismatch between destination setting and target database

alert.log

alter database register logfile '/opt/data/oracle3/prod101/FRA/prod101/archivelog/2019_12_01/o1_mf_1_190698_gy5z61jw_.arc'
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Completed: alter database register logfile '/opt/data/oracle3/prod101/FRA/prod101/archivelog/2019_12_01/o1_mf_1_190698_gy5z61jw_.arc'
Sun Dec 01 12:19:35 2019
Media Recovery Log /opt/data/oracle3/prod101/FRA/prod101/archivelog/2019_12_01/o1_mf_1_190698_gy5z61jw_.arc
Sun Dec 01 12:20:03 2019
Media Recovery Waiting for thread 1 sequence 190699
 manually register archivelog
select DEST_ID,DEST_NAME,STATUS,BINDING,ERROR from v$ARCHIVE_DEST where status<>'INACTIVE';

 DEST_ID DEST_NAME                                          STATUS    BINDING    ERROR
---------- -------------------------------------------------- --------- ---------- -----------------------------------------------------------------
         1 LOG_ARCHIVE_DEST_1                                 VALID     OPTIONAL
         2 LOG_ARCHIVE_DEST_2                                 VALID     OPTIONAL
         3 LOG_ARCHIVE_DEST_3                                 DISABLED  OPTIONAL   ORA-16047: DGID mismatch between destination setting and target
                                                                                   database

Since LOG_ARCHIVE_DEST_3 is getting error, we will defer it and enable it back, which will resolve the issue.

SQL> sho parameter log_archive_dest_state_3

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest_state_3             string                           ENABLE
log_archive_dest_state_30            string                           enable
log_archive_dest_state_31            string                           enable
SQL>
SQL>
SQL> alter system set log_archive_dest_state_3=defer;

System altered.

SQL> sho parameter log_archive_dest_state_3

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest_state_3             string                           DEFER
log_archive_dest_state_30            string                           enable
log_archive_dest_state_31            string                           enable


SQL> select DEST_ID,DEST_NAME,STATUS,BINDING,ERROR from v$ARCHIVE_DEST where status<>'INACTIVE';

   DEST_ID DEST_NAME                                          STATUS    BINDING    ERROR
---------- -------------------------------------------------- --------- ---------- -----------------------------------------------------------------
         1 LOG_ARCHIVE_DEST_1                                 VALID     OPTIONAL
         2 LOG_ARCHIVE_DEST_2                                 VALID     OPTIONAL
         3 LOG_ARCHIVE_DEST_3                                 DISABLED  OPTIONAL   ORA-16047: DGID mismatch between destination setting and target
                                                                                   database

SQL> alter system set log_archive_dest_state_3=ENABLE;

System altered.

SQL>
SQL> select DEST_ID,DEST_NAME,STATUS,BINDING,ERROR from v$ARCHIVE_DEST where status<>'INACTIVE';

   DEST_ID DEST_NAME                                          STATUS    BINDING    ERROR
---------- -------------------------------------------------- --------- ---------- -----------------------------------------------------------------
         1 LOG_ARCHIVE_DEST_1                                 VALID     OPTIONAL
         2 LOG_ARCHIVE_DEST_2                                 VALID     OPTIONAL
         3 LOG_ARCHIVE_DEST_3                                 VALID     OPTIONAL

Error is now resolved.

Hope it worked !! 🙂