In Oracle Clusterware 11g Release 2, each node in a cluster has a local registry for node specific resources, called an Oracle Local Registry (OLR), which is installed and configured when Oracle Clusterware installs OCR. Multiple processes on each node have simultaneous read and write access to the OLR particular to the node on which they reside, regardless of whether Oracle Clusterware is running or fully functional. The OLR provides various Oracle Clusterware processes with access to key configuration information even when Oracle Clusterware is not running on the node. One of its functions is to facilitate the Oracle Clusterware startup process in situations where the ASM stores the OCR and voting disks. During the startup process, the OLR is referenced to determine the exact location of the voting disks. This enables the node to join the cluster. After this initial phase, ASM is started. After ASM is started, processes that require the full OCR can start and the clusterware startup process completes.
By default, OLR is located at grid_home/cdata/hostname.olr.
The OLR contains the information about ORA_CRS_HOME, localhost version, active version, GPnP details, OCR latest backup time and location, information about OCR daily, weekly backup location
and node name etc.
You can manage the OLR by using the ocrcheck, ocrdump, and ocrconfig utilities with the -local option.
To see the location of the OLR, use the ocrcheck utility:
$ ocrcheck -config -local
You can check the status of the OLR as follows:
# ocrcheck -local
You can display the content of OLR to the text terminal that initiated the program using the OCRDUMP utility, as follows:
$ ocrdump -local -stdout
You can perform administrative tasks on OLR using the OCRCONFIG utility. To export OLR to a file:
# ocrconfig –local –export file_name
To import a specified file to OLR:
# ocrconfig –local –import file_name
To modify the OLR file on the local node:
# ocrconfig –local –repair olr file_name
Note: The olr keyword used with the -repair option is valid only when -local is used.
Thats it. Hope this will help you.
Thanks,
Chowdari
By default, OLR is located at grid_home/cdata/hostname.olr.
The OLR contains the information about ORA_CRS_HOME, localhost version, active version, GPnP details, OCR latest backup time and location, information about OCR daily, weekly backup location
and node name etc.
You can manage the OLR by using the ocrcheck, ocrdump, and ocrconfig utilities with the -local option.
To see the location of the OLR, use the ocrcheck utility:
$ ocrcheck -config -local
You can check the status of the OLR as follows:
# ocrcheck -local
You can display the content of OLR to the text terminal that initiated the program using the OCRDUMP utility, as follows:
$ ocrdump -local -stdout
You can perform administrative tasks on OLR using the OCRCONFIG utility. To export OLR to a file:
# ocrconfig –local –export file_name
To import a specified file to OLR:
# ocrconfig –local –import file_name
To modify the OLR file on the local node:
# ocrconfig –local –repair olr file_name
Note: The olr keyword used with the -repair option is valid only when -local is used.
Thats it. Hope this will help you.
Thanks,
Chowdari