When using Oracle 12 Clusterware, which two actions are required to repair the ocr.loc file on host01 in a cluster having three other nodes called host02, host03,
and host04?
A.
Run ocr.config –repair on another node in the cluster to repair the ocr.loc file on host01
B.
Stop the clusterware stack on host01 only.
C.
Stop the clusterware stack on all cluster nodes.
D.
Run ocrconfig –repair on host01.
E.
Stop the clusterware stack on host01 and on the node used to issue the ocrconfig –repair command.
Explanation:
B: You cannot repair the OCR configuration on a node on which the Oracle Cluster Ready Services daemon is running.
D: When you repair OCR on a stopped node using ocrconfig -repair, you must provide the same OCR file name (which should be case-sensitive) as the OCR file
names on other nodes. https://docs.oracle.com/cd/E11882_01/rac.112/e41959/votocr.htm#CHDJJDEF
To repair OCR configuration, run this command on the node on which you have stopped Oracle Clusterware:
# ocrconfig -repair -add +DATA1
You cannot perform this operation on a node on which Oracle Clusterware is running.
B,D CORRECT
A) ocr.config doesn’t exists
c) This is wrong because is an local repair
E) This is wrong because is an local repair
ocrconfig -repair
Use the ocrconfig -repair command to repair an OCR configuration on the node from which you run this command. Use this command to add, delete, or replace an OCR location on a node that may have been stopped while you made changes to the OCR configuration in the cluster. OCR locations that you add must exist, have sufficient permissions, and, in the case of Oracle ASM disk groups, must be mounted before you can add them.