ORA-16820: fast-start failover observer is no longer observing this database
PROBLEM NOTE:
When I try to start the Observer from the Observer server, my configuration output shows that
ORA-16820: fast-start failover observer is no longer observing this database.
DGMGRL> show configuration verbose;
Configuration - DG_Bhuvan
Protection Mode: MaxAvailability
Databases:
BHUVAN_A - Primary database
Error: ORA-16820: fast-start failover observer is no longer observing this database
BHUVAN_B - (*) 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'
CommunicationTimeout = '180'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: BHUVAN_B
Observer: bhuoraobs001
Lag Limit: 30 seconds (not in use)
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Configuration Status:
ERROR
DGMGRL>
-- VIEWING CONFIGURATION DETAILS FOR PRIMARY DB ON DG
DGMGRL> show database verbose 'BHUVAN_A';
Database - BHUVAN_A
Role: PRIMARY
Instance(s):
BHUVAN_1
BHUVAN_2
Database Error(s):
ORA-16820: fast-start failover observer is no longer observing this database
Properties:
DGConnectIdentifier = 'BHUVAN_A_DG'
ObserverConnectIdentifier = ''
....
(*) - Please check specific instance for the property value
Database Status:
ERROR
-- VIEWING CONFIGURATION DETAILS FOR STANDBY DB ON DG
DGMGRL> show database verbose 'BHUVAN_B';
Database - BHUVAN_B
Role: PHYSICAL STANDBY
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: OFF
Instance(s):
BHUVAN_1
BHUVAN_2 (apply instance)
Database Error(s):
ORA-16820: fast-start failover observer is no longer observing this database
Properties:
DGConnectIdentifier = 'BHUVAN_B_DG'
ObserverConnectIdentifier = ''
....
(*) - Please check specific instance for the property value
Database Status:
ERROR
SOLUTION:
After doing a lot of research we found that “DGConnectIdentifier" should be used when you try to connect from primary & standby database to start the observer respectively
Ex:
DGConnectIdentifier = 'BHUVAN_A_DG' – PRIMARY DB Configuration
DGConnectIdentifier = 'BHUVAN_B_DG' – STANDBY DB Configuration
STARTING OBSERVER IN BACKGROUND MODE
dgmgrl -logfile $HOME/observer.log sys/oracle@bhuvan_a "start observer" &
BHUVAN_A_DG =
(DESCRIPTION =
(ADDRESS=(PROTOCOL=TCP)(HOST=node1-vip)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=node2-vip)(PORT=1521))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME= BHUVAN_A))
)
BHUVAN_B_DG =
(DESCRIPTION =
(ADDRESS=(PROTOCOL=TCP)(HOST= node1-vip)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST= node2-vip)(PORT=1521))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME= BHUVAN_B ))
)
Other wise your observer will come down automatically
DGMGRL> show configuration verbose;
Configuration - DG_Bhuvan
Protection Mode: MaxAvailability
Databases:
BHUVAN_A - Primary database
BHUVAN_B - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
FastStartFailoverLagLimit = '30'
CommunicationTimeout = '180'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: BHUVAN _B
Observer: bhuoraobs001
Lag Limit: 30 seconds (not in use)
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Configuration Status:
SUCCESS
DGMGRL>
ORA-16819: fast-start failover observer not started
ACTION: you have not started the Observer, so you have to start the observer
dgmgrl -logfile $HOME/observer.log sys/oracle@bhuvan_a "start observer" &
I just saw one target Target: BHUVAN _B has a space before the dash
ReplyDelete