Attempting to start the observer raises an error:
DGMGRL> start observer:
DGM-16954: Unable to open and lock the Observer configuration file Failed.
Identify two possible reasons for this error?
A.
Fast-Start Failover is not yet enabled for this Data Guard configuration
B.
The observer configuration file is marked read-only.
C.
There is already an observer running for this Data Guard configuration.
D.
There is another observer running for a Data Guard configuration which uses the same observer configuration file
E.
The broker configuration has not yet been created.
DGM-16954: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for exclusive access.
Action: Make sure the Observer has the correct operating system privileges to write the file and there is no other Observer that is using the same file. Try the command again.
https://docs.oracle.com/cd/B19306_01/server.102/b14219/dgmus.htm
CD???
C&D doesn’t have much differences i can consider B as per your notes itself.
There is no possibility to start multiple observers and specify which ‘configuration file’ to use for the same DG configuration.
Hence my choice: B,C
C is incorrect, if that happens (second observer), you get another error message
DGMGRL> start observer
Error: ORA-16647: could not start more than one observer
Good one !!
B and D are correct.
the configuration file is called fsfo.dat, which is created in the current folder as soon you enter ‘start observer’.
stopping the observer does not cleanup that file.
-rw——- 1 oracle oinstall 104 May 18 13:54 fsfo.dat
oracle@observer1:~$ chmod -w fsfo.dat
oracle@observer1:~$ ls -ltra fsfo.dat
-r——– 1 oracle oinstall 104 May 18 13:54 fsfo.dat
restarting the observer
DGMGRL> start observer
DGM-16954: Unable to open and lock the Observer configuration file
Failed.
B, D is correct
BD
D:
By default the file is named fsfo.dat and is created in the working directory where the observer is started. The state file is locked when the observer is running to prevent multiple observers from using the same file. It’s generally a good idea to store the state file in a directory associated with the database to avoid locking issues when running multiple observers on the same host.
B,D