This appendix describes the syntax of the Oracle Cluster Registry (OCR) configuration utility, OCRCONFIG. It also explains how to troubleshoot OCR using the OCRDUMP and OCRCHECK utilities. You can also use these utilities on Oracle Local Registry (OLR).
This appendix contains the following topics:
This section contains topics which relate to using the OCRCONFIG utility.
Use the ocrconfig
command to manage OCR. Using this utility you can import, export, add, delete, restore, overwrite, backup, repair, replace, move, upgrade, or downgrade OCR.
The ocrconfig
command syntax is as follows:
ocrconfig -option
To display the help output for the OCRCONFIG utility:
ocrconfig -help
To use the OCRCONFIG utility you must be logged into the operating system as a user with administrative privileges.
When you use the OCRCONFIG utility, a log file called ocrconfig_
pid
.log
is created in the $ORACLE_HOME/log/
host_name
/client
directory. Ensure that you have write privileges in this directory before running the OCRCONFIG utility.
This section lists the following OCRCONFIG commands:
Use the ocrconfig -add
command to add an OCR device or file.
ocrconfig -add file_name
You must run this command as root
.
The file_name
variable can be a device name, a file name, or the name of an ASM disk group. For example:
/dev/raw/raw1
/oradbocfs/crs/data.ocr
d:\oracle\mirror.ocr
+newdg
If you specify an ASM disk group, the name of the disk group must be preceded by a plus sign (+
).
To add an OCR file to the default location in ASM, data
:
# ocrconfig -add +data
Use the ocrconfig -backuploc
command to specify an OCR backup directory location.
ocrconfig [-local] -backuploc file_name
You must run this command as root
.
Use the -local
option to back up OLR.
The file_name
variable can be a full directory path name that is accessible by all nodes. For example:
Grid_home
/cdata/cluster3/
d:\cdata\cluster3
The default location for generating OCR backups on Linux or UNIX systems is Grid_home
/cdata/
cluster_name
, where cluster_name
is the name of your cluster. The Windows default location for generating OCR backups uses the same path structure.
The default location for generating OLR backups on Linux or UNIX systems is Grid_home
/cdata/
host_name
, where host_name
is the name of the node on which the OLR resides that you want to back up. The Windows default location for generating OLR backups uses the same path structure.
To specify an OCR backup location in a directory:
# ocrconfig -backuploc $Grid_home/cdata/cluster3
Use the ocrconfig -delete
command to remove an OCR device or file.
ocrconfig -delete file_name
You must run this command as root
.
The file_name
variable can be a device name, a file name, or the name of an ASM disk group. For example:
/dev/raw/raw1
/oradbocfs/crs/data.ocr
d:\oracle\mirror.ocr
+olddg
If you specify an ASM disk group, the name of the disk group must be preceded by a plus sign (+
).
To remove an OCR location:
# ocrconfig -delete +olddg
Use the ocrconfig -downgrade
command to downgrade OCR to an earlier specified version.
ocrconfig -downgrade [-version version_string]
You must run this command as root
.
To downgrade OCR to an earlier version:
# ocrconfig -downgrade -version
Use the ocrconfig -export
command to export the contents of OCR to a target file.
ocrconfig [-local] -export file_name
You must run this command as root
.
Use the -local
option to export the contents of OLR.
The file_name
variable can be a full path name or the name of an ASM disk group that is accessible by all nodes. For example:
/oradbocfs/crs/data.ocr
d:\oracle\
To export the contents of OCR to a file:
# ocrconfig -export d:\tmp\a
Use the ocrconfig -import
command to import the contents of a target file into which you exported the contents of OCR back into OCR.
ocrconfig [-local] -import file_name
You must run this command as root
.
Use the -local
option to import the contents of OLR from a file.
The file_name
variable can be a full path name or the name of an ASM disk group that is accessible by all nodes. For example:
/oradbocfs/crs/data.ocr
d:\oracle\
+backupdg
If you specify an ASM disk group, the name of the disk group must be preceded by a plus sign (+
).
You must shut down Oracle Clusterware before running this command.
To import the contents a file back into OCR:
# ocrconfig -import d:\tmp\a
Use the ocrconfig -manualbackup
command to back up OCR on demand in the location you specify with the -backuploc
option.
ocrconfig [-local] -manualbackup
You must run this command as root
.
Use the -local
option to perform a manual backup of OLR.
To back up OCR:
# ocrconfig -manualbackup
Use the ocrconfig -overwrite
command to overwrite an OCR configuration in the OCR metadata with the current OCR configuration information that is found on the node from which you run this command.
ocrconfig -overwrite
You must run this command as root
.
To overwrite an OCR configuration:
# ocrconfig -overwrite
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 configuration on a node that may have been stopped while you made changes to the OCR configuration in the cluster.
ocrconfig -repair -add file_name | -delete file_name | -replace current_file_name -replacement new_file_name
You must run this command as root
.
The file_name
variable can be a device name, a file name, or the name of an ASM disk group. For example:
/dev/raw/raw1
/oradbocfs/crs/data.ocr
d:\oracle\mirror.ocr
+newdg
If you specify an ASM disk group, the name of the disk group must be preceded by a plus sign (+
).
You can only use one option with ocrconfig -repair
at a time.
To repair an OCR configuration:
# ocrconfig -repair -delete +olddg
Use the ocrconfig -replace
command to replace an OCR device or file on the node from which you run this command.
ocrconfig -replace current_file_name -replacement new_file_name
You must run this command as root
.
The *_file_name
variable can be a device name, a file name, or the name of an ASM disk group. For example:
/dev/raw/raw1
/oradbocfs/crs/data.ocr
d:\oracle\mirror.ocr
+newdg
If you specify an ASM disk group, the name of the disk group must be preceded by a plus sign (+
).
To replace an OCR device or file:
# ocrconfig -replace /dev/raw/raw1 -replacement +newdg
Use the ocrconfig -restore
command to restore OCR from an automatically created OCR backup file.
ocrconfig [-local] -restore file_name
You must run this command as root
.
Use the -local
option to restore a backup of OLR.
The file_name variable can be a file name or an ASM file name from an ASM disk group. For example:
/oradbocfs/crs/BACKUP00.ocr
d:\oracle\BACKUP01.ocr
+backupdg:BACKUP02
If you specify an ASM disk group and file name, the name of the disk group must be preceded by a plus sign (+
) and the disk group and file name must be separated by a colon (:
).
To restore OCR from a file on ASM:
# ocrconfig -restore +backupdg:BACKUP02
Use the ocrconfig -showbackup
command to display the backup location, timestamp, and the originating node name of the backup files. By default, this command displays information for both automatic and manual backups unless you specify auto
or manual
.
ocrconfig [-local] -showbackup [auto | manual]
Use the -local
option to show manual OLR backup information. The -local
flag functions only with the manual
option.
You can optionally specify auto
or manual
to display information about only automatic backups or only manual backups, respectively:
auto
: Displays information about automatic backups that Oracle Clusterware created in the past 4 hours, 8 hours, 12 hours, and in the last day and week.
manual
: Displays information about manual backups that you invoke using the ocrconfig -manualbackup
command.
To display manual backup information for OLR:
$ ocrconfig -local -showbackup manual
Use the ocrconfig -upgrade
command to upgrade OCR from a previous version.
ocrconfig [-local] -upgrade [user [group]]
You must run this command as root
.
Use the -local
option to upgrade OLR.
To display manual backup information for OLR:
# ocrconfig -local -showbackup manual
This section describes various methods for troubleshooting problems with OCR, and obtaining diagnostic information from the utilities used to manage the OCR.
This section contains the following topics:
Table E-1 describes common OCR problems with corresponding resolution suggestions.
Table E-1 Common Oracle Cluster Registry Problems and Solutions
Problem | Solution |
---|---|
Not currently using OCR mirroring and would like to enable it. |
Run the |
OCR failed and you must replace it. Error messages in Oracle Enterprise Manager or OCR log file. |
Run the |
OCR has a misconfiguration. |
Run the |
You are experiencing a severe performance effect from OCR processing or you want to remove OCR for other reasons. |
Run the OCRCONFIG command with the |
OCR has failed and before you can fix it, the node must be rebooted with only one OCR. |
Run the |
The OCRCHECK utility displays the version of the OCR's block format, total space available and used space, OCRID, and the OCR locations that you have configured. OCRCHECK performs a block-by-block checksum
operation for all of the blocks in all of the OCRs that you have configured. It also returns an individual status for each file and a result for the overall OCR integrity check.
You can run the ocrcheck -help
command to display usage information about this utility.
The following example shows a sample of the OCRCHECK utility output:
# ocrcheck Status of Oracle Cluster Registry is as follows : Version : 3 Total space (kbytes) : 262120 Used space (kbytes) : 752 Available space (kbytes) : 261368 ID : 2098980155 Device/File Name : +dg1 Device/File integrity check succeeded Device/File Name : +dg2 Device/File integrity check succeeded Device/File not configured Device/File not configured Device/File not configured Cluster registry integrity check succeeded Logical corruption check succeeded
Note:
The logical corruption check is only performed if you run theocrcheck
command as root
.To display only configured OCR locations:
$ ocrcheck -config Oracle Cluster Registry configuration is : Device/File Name : Grid_home/oracle/has_work/data.ocr Device/File Name : Grid_home/oracle/has_work/mirror.ocr
Run the ocrcheck -local -config
command to obtain OLR information.
$ ocrcheck -local -config
Oracle Local Registry configuration is :
Device/File Name : Grid_home/oracle/has_work/data.olr.stact23
OCRCHECK creates a log file in the Grid_home
/log/
host_name
/client
directory. To change the log level, edit the Grid_home
/srvm/admin/ocrlog.ini
file.
This section explains how to use the OCRDUMP utility to view OCR and Oracle Local Registry (OLR) content for troubleshooting. The OCRDUMP utility enables you to view the OCR and OLR contents by writing the content to a file or stdout
in a readable format.
You can use several options for OCRDUMP. For example, you can limit the output to a key and its descendents. You can also write the contents to an XML file that you can view using a browser. OCRDUMP writes the OCR keys as ASCII strings and values in a data type format. OCRDUMP retrieves header information based on a best effort basis.
OCRDUMP also creates a log file in Grid_home
/log/
host_name
/client
. To change the log level, edit the Grid_home
/srvm/admin/ocrlog.ini
file.
To change the logging component, edit the entry containing the comploglvl=
entry. For example, to change the log level of the OCRAPI
component to 3 and to change the log level of the OCRRAW
component to 5, make the following entry in the ocrlog.ini
file:
comploglvl="OCRAPI:3;OCRRAW:5"
Note:
Make sure that you have file creation privileges in theGrid_home
directory before using the OCRDUMP utility.This section describes the OCRDUMP utility command syntax and usage. Run the ocrdump
command with the following syntax where file_name
is the name of a target file to which you want Oracle Database to write the Oracle Cluster Registry output and where key_name
is the name of a key from which you want Oracle Database to write Oracle Cluster Registry subtree content:
ocrdump [file_name | -stdout] [-local] [-backupfile backup_file_name] [-keyname key_name] [-xml] [-noheader]
Table E-2 describes the OCRDUMP utility options and option descriptions.
Table E-2 OCRDUMP Options and Option Descriptions
Options | Description |
---|---|
|
The name of a file to which you want OCRDUMP to write output. By default, OCRDUMP writes output to a predefined output file named |
|
Use this option to redirect the OCRDUMP output to the text terminal that initiated the program. If you do not redirect the output, OCRDUMP writes output to a predefined output file named |
|
Use this option to dump the contents of OLR. |
|
Use this option to view the contents of an OCR backup file. Use the |
|
The name of the backup file with the content you want to view. You can query the backups using the |
|
The name of an Oracle Cluster Registry key whose subtree is to be dumped. |
|
Use this option to write the output in XML format. |
|
Does not print the time at which you ran the command and when the Oracle Cluster Registry configuration occurred. |
The following ocrdump
utility examples extract various types of OCR information and write it to various targets:
ocrdump
Writes the OCR content to a file called OCRDUMPFILE
in the current directory.
ocrdump MYFILE
Writes the OCR content to a file called MYFILE
in the current directory.
ocrdump -stdout -keyname SYSTEM
Displays the OCR content from the subtree of the key SYSTEM
in the terminal window.
ocrdump -stdout -xml
Displays the OCR content in the terminal window in XML format.
ocrdump -stdout -backupfile $ORA_CRS_HOME/cdata/cluster_name/file_name
Writes the entire OCR and OLR content to a backup file located in the $ORA_CRS_HOME/cdata/
cluster_name
directory. You must run this command as root
to be able to view all of the keys. Be sure to name the file appropriately so that it can be recognized by anyone as an OCR backup file, such as BACKUPOO.ocr
.
The following OCRDUMP examples show the KEYNAME
, VALUE TYPE
, VALUE
, permission set (user
, group
, world
) and access rights for two sample runs of the ocrdump
command. The following shows the output for the SYSTEM.language
key that has a text value of AMERICAN_AMERICA.WE8ASCII37
.
[SYSTEM.language] ORATEXT : AMERICAN_AMERICA.WE8ASCII37 SECURITY : {USER_PERMISSION : PROCR_ALL_ACCESS, GROUP_PERMISSION : PROCR_READ, OTHER_PERMISSION : PROCR_READ, USER_NAME : user, GROUP_NAME : group }
The following shows the output for the SYSTEM.version
key that has integer value of 3
:
[SYSTEM.version] UB4 (10) : 3 SECURITY : {USER_PERMISSION : PROCR_ALL_ACCESS, GROUP_PERMISSION : PROCR_READ, OTHER_PERMISSION : PROCR_READ, USER_NAME : user, GROUP_NAME : group }
The OCRCONFIG utility creates a log file in Grid_home
/log/
host_name
/client
.
To change the amount of logging, edit the path in the Grid_home
/srvm/admin/ocrlog.ini
file.