ORA-16820
fast-start failover observer is no longer observing this database
Cause
A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:
- The host where the observer was running was not available.
- The network connection between the observer and this database was not available.
- The observer process was terminated unexpectedly.
Action
Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Oracle Data Guard configuration and issuing the DGMGRL STOP OBSERVER command, and then start a new observer on another host using the DGMGRL START OBSERVER command.
ORA-16820
fast-start failover observer is no longer observing this database
Cause
A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:
- The host where the observer was running was not available.
- The network connection between the observer and this database was not available.
- The observer process was terminated unexpectedly.
Action
Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Oracle Data Guard configuration and issuing the DGMGRL STOP OBSERVER command and then start a new observer on another host using the DGMGRL START OBSERVER command.
ORA-16820
fast-start failover observer is no longer observing this database
Cause
A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:
- The host where the observer was running was not available.
- The network connection between the observer and this database was not available.
- The observer process was terminated unexpectedly.
Action
Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Oracle Data Guard configuration and issuing the DGMGRL STOP OBSERVER command and then start a new observer on another host using the DGMGRL START OBSERVER command.