Broker reports ORA-16858: last communication time from redo source could not be

Broker reports ORA-16858: last communication time from redo source could not be determined (文件 ID 2064384.1)

現象：

DGMGRL> show configuration

Configuration - cdblhr18c

  Protection Mode: MaxPerformance

  Members:

  cdblhr18c    - Primary database

    cdblhr18cdg  - Physical standby database 

  Members Not Receiving Redo:

  cdblhr18cdg2 - Physical standby database 

    Error: ORA-16810: multiple errors or warnings detected for the member

Fast-Start Failover: DISABLED

Configuration Status:

ERROR   (status updated 58 seconds ago)

DGMGRL> show database CDBLHR18cdg2

Database - cdblhr18cdg2

  Role:               PHYSICAL STANDBY

  Intended State:     APPLY-ON

  Transport Lag:      4 minutes (computed 10 seconds ago)

  Apply Lag:          4 minutes (computed 10 seconds ago)

  Average Apply Rate: 2.00 KByte/s

  Real Time Query:    ON

  Instance(s):

    CDBLHR18cdg2

  Database Error(s):

    ORA-16685: database does not receive redo data

  Database Warning(s):

    ORA-16853: apply lag has exceeded specified threshold

    ORA-16855: transport lag has exceeded specified threshold

Database Status:

ERROR

DGMGRL> show database CDBLHR18cdg2 RedoRoutes

  RedoRoutes = ''

DGMGRL> show database CDBLHR18cdg RedoRoutes

  RedoRoutes = '(cdblhr18cdg:cdblhr18cdg2)'

DGMGRL> 

DGMGRL> show database CDBLHR18c RedoRoutes

  RedoRoutes = ''

DGMGRL> 

解決： RedoRoutes需要設定在主庫上。

edit database cdblhr18c set property  RedoRoutes    ='(cdblhr18cdg:cdblhr18cdg2 ASYNC)';

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

SYMPTOMS

In a 12c configuration, Broker reports the errors:

ORA-16810: multiple errors or warnings detected for the database
ORA-16858: last communication time from redo source could not be determined

 

DGMGRL> show configuration

Configuration - cdb_t5

Protection Mode: MaxPerformance
Databases:
cdbph2 - Primary database
cdbphsb2 - Physical standby database
cdbphsb4 - Physical standby database
Error: ORA-16685: this database does not receive redo data

Fast-Start Failover: DISABLED

Configuration Status:
ERROR

 

DGMGRL> show database cdbphsb4

Database - cdbphsb4

Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Apply Rate: (unknown)
Real Time Query: OFF
Instance(s):
cdbphsb4

Database Error(s):
ORA-16685: this database does not receive redo data

Database Warning(s):
ORA-16858: last communication time from redo source could not be determined

CAUSE

 Broker parameter RedoRoutes is not set correctly

SOLUTION

Modify Broker parameter redoroutes for the Primary to include both databases (i.e. ALL):

   DGMGRL> edit database cdbph2 set property redoroutes='(LOCAL: ALL)';

 

An alternate solution is to list the Standby databases' DB_UNIQUE_NAME values separated by commas:

    DGMGRL> edit database cdbph2 set property redoroutes='(cdbphsb2, cdbphsb4)';

 

 

RedoRoutes is a new 12c Data Guard Broker property with the following format:

     RedoRoutes = ‘(<Redo Source> : <Redo Destination>)’

 

The Redo Source field must contain either the keyword LOCAL or ANY, or a comma-separated list of DB_UNIQUE_NAME values: {LOCAL | ANY | db_unique_name_1,[,db_unique_name_n]}

The Redo Destination field must contain the keyword ALL or a comma-separated list of database names, each of which can be followed by an optional redo transport attribute: {ALL [attribute] | db_unique_name_1 [attribute] [,db_unique_name_n [attribute]]}

The ALL keyword is an alias for all possible destinations in the configuration.

The optional redo transport attribute specifies the redo transport mode to use to send redo to the associated destination.

It can have one of three values: [ASYNC | SYNC | FASTSYNC]

If the redo transport attribute is not specified, then the redo transport mode used will be the one specified by the LogXptMode property for the destination.

---

---

About Me

........................................................................................................................ ● 本文作者：小麥苗，部分內容整理自網路，若有侵權請聯絡小麥苗刪除 ● 本文在itpub、部落格園、CSDN和個人微 信公眾號（ xiaomaimiaolhr）上有同步更新 ● 本文itpub地址： http://blog.itpub.net/26736162 ● 本文部落格園地址： http://www.cnblogs.com/lhrbest ● 本文CSDN地址： https://blog.csdn.net/lihuarongaini ● 本文pdf版、個人簡介及小麥苗雲盤地址： http://blog.itpub.net/26736162/viewspace-1624453/ ● 資料庫筆試面試題庫及解答： http://blog.itpub.net/26736162/viewspace-2134706/ ● DBA寶典今日頭條號地址： http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826 ........................................................................................................................ ● QQ群號： 230161599 、618766405 ● 微 信群：可加我微 信，我拉大家進群，非誠勿擾 ● 聯絡我請加QQ好友 （ 646634621 ），註明新增緣由 ● 於 2019-09-01 06:00 ~ 2019-09-31 24:00 在西安完成 ● 最新修改時間：2019-09-01 06:00 ~ 2019-09-31 24:00 ● 文章內容來源於小麥苗的學習筆記，部分整理自網路，若有侵權或不當之處還請諒解 ● 版權所有，歡迎分享本文，轉載請保留出處 ........................................................................................................................ ● 小麥苗的微店： https://weidian.com/s/793741433?wfr=c&ifr=shopdetail ● 小麥苗出版的資料庫類叢書： http://blog.itpub.net/26736162/viewspace-2142121/ ● 小麥苗OCP、OCM、高可用網路班： http://blog.itpub.net/26736162/viewspace-2148098/ ● 小麥苗騰訊課堂主頁： https://lhr.ke.qq.com/ ........................................................................................................................ 使用 微 信客戶端掃描下面的二維碼來關注小麥苗的微 信公眾號（ xiaomaimiaolhr）及QQ群（DBA寶典）、新增小麥苗微 信， 學習最實用的資料庫技術。 ........................................................................................................................

 

 

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/26736162/viewspace-2656874/，如需轉載，請註明出處，否則將追究法律責任。