DGMGRL Error: ORA-16820: fast-start failover observer is no longer observing this database

advertisements

_____________________________________________________________________________________________________________________

Error Description

Data guard DGMGRL show configuration command gives Error: ORA-16820: fast-start failover observer is no longer observing this database

DGMGRL> show configuration verbose

Configuration - TRPROCONFIG
  Protection Mode: MaxAvailability
  Databases:
    TRPRO         - Primary database
      Error: ORA-16820: fast-start failover observer is no longer observing this database
    TRPRO_STANDBY - (*) Physical standby database
      Error: ORA-16820: fast-start failover observer is no longer observing this database
  (*) Fast-Start Failover target
  Properties:
    FastStartFailoverThreshold      = '30'
    OperationTimeout                = '30'
    FastStartFailoverLagLimit       = '30'
….
….
….
Configuration Status:
ERROR

Solution Description

You need start the observer. If you run the following query then you can see the FS_FAILOVER_OBSERVER_PRESENT  value is NO

SQL> select FS_FAILOVER_STATUS,FS_FAILOVER_CURRENT_TARGET,FS_FAILOVER_THRESHOLD,                 FS_FAILOVER_OBSERVER_PRESENT  from v$database;

FS_FAILOVER_STATUS     FS_FAILOVER_CURRENT_TARGET     FS_FAILOVER_THRESHOLD FS_FAIL

---------------------- ------------------------------ --------------------- -------

SYNCHRONIZED           TRPRO_STANDBY                                     30 NO

Any of the below options you can use to start the observer

DGMGRL> start observer
Observer started
Press ctrl-C to quit from the prompt.
From the command prompt and in background.
$ dgmgrl -logfile $HOME/observer.log sys/abc123 "start observer" &
[1] 7735
$ DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected.
SQL> select FS_FAILOVER_STATUS,FS_FAILOVER_CURRENT_TARGET,FS_FAILOVER_THRESHOLD,                 FS_FAILOVER_OBSERVER_PRESENT  from v$database;
FS_FAILOVER_STATUS     FS_FAILOVER_CURRENT_TARGET     FS_FAILOVER_THRESHOLD FS_FAIL
---------------------- ------------------------------ --------------------- -------
SYNCHRONIZED           TRPRO_STANDBY                                     30 YES

Now the issue is resolved.

DGMGRL> show configuration
Configuration - TRPROCONFIG
  Protection Mode: MaxAvailability
  Databases:
    TRPRO         - Primary database
    TRPRO_STANDBY - (*) Physical standby database
Fast-Start Failover: ENABLED
Configuration Status:
SUCCESS

_____________________________________________________________________________________________________________________

Website Stats