oracle ora 16047,ORA-16047: DGID mismatch between destination setting and target database解决

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

类别：Oracle数据库   作者：码皇   来源：互联网   点击：

ORA-16047: DGID mismatch between destination setting and target database解决做DG的时候 主库两个节点无法把日志传到备库上[sql]SQL> select dest_name,status,type,database_mode,protection_mo

ORA-16047: DGID mismatch between destination setting and target database解决 做DG的时候 主库两个节点无法把日志传到备库上[sql] SQL> select dest_name,status,type,database_mode,protection_mode,destination,applied_seq#,db_unique_name from v$archive_dest_status;    DEST_NAME                 STATUS    TYPE       DATABASE_MODE   PROTECTION_MODE      DESTINATIO APPLIED_SEQ# DB_UNIQUE_NAME  ------------------------- --------- ---------- --------------- -------------------- ---------- ------------ ------------------------------  LOG_ARCHIVE_DEST_1        VALID     LOCAL      OPEN_READ-ONLY  MAXIMUM PERFORMANCE  +DATA/sharkd            0 sharkdg                                                                                      b/archivel                                                                                      og    LOG_ARCHIVE_DEST_2        ERROR     UNKNOWN    UNKNOWN         MAXIMUM PERFORMANCE  sharkdb                 0 sharkdb   发现 STATUS 非 VALID状态。select dest_id,error from v$archive_dest;ORA-16047: DGID mismatch between destination setting and target database看来没有把日志传过去查看 ALTER.ORA日志*** 2013-08-26 11:19:06.319Archived Log entry 1792 added for thread 1 sequence 902 ID 0xfe904e46 dest 1: /arch/1_902_822142156.dbfORA-16055: FAL request rejected检查 log_archive_dest_2 设置[sql] SQL> show parameter LOG_ARCHIVE_DEST_2    NAME                                 TYPE        VALUE  ------------------------------------ ----------- ------------------------------  log_archive_dest_2                   string      service=shardb lgwr sync affirm valid_for=(online_logfiles,primary_role)db_unique_name=sharkdg   [sql]    [sql] 查看备库的DB_UNIQUE_NAME 是否有错  果然设置成了SHARKDB了   [sql] 或查看log_archive_config='DG_CONFIG=()‘  [sql]    [sql] 修改了 LOG_ARCHIVE_DEST_2  SCOPE=BOTH   依旧要重启实例 否则好像并不能生效。

相关热词搜索：

ORA-16047: DGID mismatch