Examine this query and its output:
SQL> select fs_failover_status, fs_failover_current_target,
2 fs_failover_observer_present, fs_failover_oserver_host
3 from v$database:
FS_FAILOVER_STATUS FS_FAILOVER_CURRENT_TARGET
FS_FAILOVER_OBSERVER_PRESENT FS_FAILOVER_OBSERVER_HOST
————— ———————– —————- ——————
BYSTANDER cats NO
O17.example.com
Which are true?
A.
The observer is not connected to the database on which the query was executed.
B.
Cats is a bystander database.
C.
The observer is connected to the database on which the query was executed.
D.
The observer is currently running on o17.example.com.
E.
The observer is not running, but should run on o17.example.com.
Explanation:
Viewing Information About the Observer
You can find information about the observer by querying the following columns in the V$DATABASE view:
* FS_FAILOVER_OBSERVER_HOST shows the name of the computer on which the observer is running. Here it is cats.
* FS_FAILOVER_OBSERVER_PRESENT shows whether or not the observer is connected to the local database. Here the value is NO.https://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
FS_FAILOVER_CURRENT_TARGET
DB_UNIQUE_NAME of the standby that is the current FSFO target standby for the Data Guard configuration
FS_FAILOVER_OBSERVER_PRESENT
Indicates whether the observer is currently connected to the local database (YES) or not (NO)
FS_FAILOVER_STATUS (BYSTANDER)
Fast-start failover is enabled, but this standby database is not the target of the fast-start failover. The database cannot provide fast-start failover status information.
FS_FAILOVER_OBSERVER_HOST
Machine name that is currently hosting the observer process
AE?
correct answer is A&D
tested in lab
if the observer is not running, the fs_failover_observer_host is null. observer_present is yes in the primary and its target, no in the bystanders
So in this case, observer is running, but we are in a bystander
A, D.
A, D
Actually the question calls for more than one answer (“Which are true?”)
D
This question has two answers: A, D