Broker reports ORA-16858: last communication time from redo source (文档 ID 2064384.1)

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 = ‘(:)’

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宝典）、添加小麦苗微 信， 学习最实用的数据库技术。

........................................................................................................................