Oracle Local Registry (OLR) - New Component of Oracle Clusterware 11g Release 2

In Oracle Clusterware 11g Release2 an additional component related to the OCR called the Oracle Local Registry (OLR) is installed on each node in the cluster. The OLR is a local registry for node specific resources. THe OLR is not shared by other nodes in the cluster. It is installed and configured when Oracle clusterware is installed.

 

Purpose of OLR

It is the very first file that is accessed by OHASD service to startup 11gR2 clusterware when OCR is stored on ASM. OCR should be accessible to find out the resources which need to be started on a node. If OCR is on ASM, it can’t be read until ASM (which itself is a resource for the node and this information is stored in OCR) is up. To resolve this problem, information about the resources which need to be started on a node is stored in an operating system  file which is called Oracle Local Registry or OLR. Since OLR is a file an operating system file, it can be accessed by various processes on the node for read/write irrespective of the status of the clusterware (up/down). Hence, when  a node joins the cluster,  OLR on that node is read, various resources ,including ASM  are started on the node  . Once ASM is up , OCR is accessible and is used henceforth to manage all the clusterware resources. If OLR is missing or corrupted, clusterware can’t be started on that node!

 

Where is OLR located?

The OLR file is located in the grid_home/cdata/<hostname>.olr 

The location of OLR is stored in /etc/oracle/olr.loc.and used by OHASD .

 

What does OLR contain?

The OLR stores data about

• ORA_CRS_HOME
• localhost version
• active version
• GPnP details
• OCR latest backup time and location
• information about OCR daily, weekly backup location
•  node name etc.

This information stored in the OLR is needed by OHASD to start or join a cluster.

A quick  peek at the backup of the olr shows the resources that are being maintained.

[root@server01 ~]# ocrconfig -local -manualbackup

Server01     2016/12/12 11:12:27     /u01/app/11.2.0/grid/cdata/host01/backup_20161212_110527.olr

[root@Server01~]#strings /u01/app/11.2.0/grid/cdata/host01/backup_20161212_110527.olr |grep -v type |grep ora!

ora!drivers!acfs

ora!crsd

ora!asm

ora!evmd

ora!ctssd

ora!cssd

ora!cssdmonitor

ora!diskmon

ora!gpnpd

ora!gipcd

ora!mdnsd

 

OLR administration

You can view the status of the OLR file on each node by using the ocrcheck command with the –local parameter as seen here:

#ocrcheck -local

 

ocrdump can be used to  dump the contents of the OLR to tthe text terminal:

#ocrdump -local -stdout

 

You can use the ocrconfig command to export and import the OLR as seen in these examples:

#ocrconfig -local -export <export file name >

#ocrconfig -local -import <file name>

 

And you can repair the OLR file should it become corrupted with the ocrconfig command as seen in this example:

#ocrconfig -local -repair olr <file name>

 

The OLR is backed up at the end of an installation or an upgrade. After that time, you can only manually back up the OLR. Automatic backups are not supported for the OLR.

To manually back up OLR:

# ocrconfig –local –manualbackup

To view the contents of the OLR backup file:

#ocrdump -local -backupfile olr_backup_file_name

To change the OLR backup location

#ocrconfig -local -backuploc new_olr_backup_path

To restore OLR: 

# crsctl stop crs

# ocrconfig -local -restore file_name 

# ocrcheck -local 

# crsctl start crs 

$ cluvfy comp olr