Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
The Observer stop command should be called either from the Primary Database or from the Standby Databases connected to the Primary Database.
1. We stop the Observer.
[Primary-1]1 2 | DGMGRL> stop observer; Done. |
3. When the configuration is queried, we see the warning that the Observer is not running.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 | DGMGRL> show configuration verbose; Configuration - Broker_Configuration Protection Mode: MaxPerformance Databases: primary - Primary database Warning: ORA-16819: fast-start failover observer not started standby - (*) Physical standby database Warning: ORA-16819: fast-start failover observer not started logical - Logical standby database (*) Fast-Start Failover target Properties: FastStartFailoverThreshold = '100' OperationTimeout = '30' FastStartFailoverLagLimit = '900' CommunicationTimeout = '180' ObserverReconnect = '15' FastStartFailoverAutoReinstate = 'TRUE' FastStartFailoverPmyShutdown = 'TRUE' BystandersFollowRoleChange = 'ALL' ObserverOverride = 'FALSE' ExternalDestination1 = '' ExternalDestination2 = '' PrimaryLostWriteAction = 'CONTINUE' Fast-Start Failover: ENABLED Threshold: 100 seconds Target: standby Observer: (none) Lag Limit: 900 seconds Shutdown Primary: TRUE Auto-reinstate: TRUE Observer Reconnect: 15 seconds Observer Override: FALSE Configuration Status: |
WARNING
