6 Managing Oracle Cluster Registry and Voting Files
Oracle Clusterware includes two important components that manage configuration and node membership: Oracle Cluster Registry (OCR), which also includes the local component Oracle Local Registry (OLR), and voting files.
-
OCR stores Oracle Clusterware and Oracle RAC database configuration information
-
OLR resides on every node in the cluster and manages Oracle Clusterware configuration information for each particular node
-
Voting files store information about node membership. Each voting file must be accessible by all nodes in the cluster for nodes to be members of the cluster
Notes:
-
Oracle Clusterware 12c does not support the use of raw or block devices. To upgrade to Oracle Clusterware 12c from a previous Oracle Clusterware release on which you were using raw or block devices, you must migrate OCR and voting files to Oracle Automatic Storage Management (Oracle ASM) or a shared file system before you upgrade.
-
You can store OCR and voting files on Oracle ASM or a shared file system on Standalone Clusters.
In Oracle Database 12c Release 2 (12.2), the placement of OCR and voting disk files directly on a shared file system was desupported. Starting with Oracle Database 19c (19.3), that desupport is rescinded for Standalone Clusters. For Oracle Domain Services Clusters, you must continue to place OCR and voting disk files in disk groups managed by Oracle ASM.
Oracle recommends that you configure multiple voting files during Oracle Clusterware installation to improve availability. If you choose to put the voting files into an Oracle ASM disk group, then Oracle ASM ensures the configuration of multiple voting files if you use a normal or high redundancy disk group. If you choose to store the voting files on a shared file system, then select the option to configure multiple voting files, in which case you will have to specify three different file systems based on different disks.
If necessary, you can dynamically add or replace voting files after you complete the Oracle Clusterware installation process without stopping the cluster.
This chapter includes the following topics:
Managing Oracle Cluster Registry and Oracle Local Registry
Use OCRCONFIG, OCRDUMP, and OCRCHECK to manage OCR and the Oracle Local Registry (OLR).
OCR contains information about all Oracle resources in the cluster.
OLR is a registry similar to OCR located on each node in a cluster, but contains information specific to each node. It contains manageability information about Oracle Clusterware, including dependencies between various services. Oracle High Availability Services uses this information. OLR is located on local storage on each node in a cluster. Its default location is in the path Grid_home/cdatahost_name.olr
, where Grid_home
is the Oracle Grid Infrastructure home, and host_name
is the host name of the node.
Administering OCR is decribed in the following topics:
Related Topics
Migrating Oracle Cluster Registry to Oracle Automatic Storage Management
With the Oracle Clusterware storage residing in an Oracle ASM disk group, you can manage both database and clusterware storage using Oracle Enterprise Manager.
To improve Oracle Clusterware storage manageability, OCR is configured, by default, to use Oracle ASM in Oracle Database 12c. However, if you upgrade from a previous version of Oracle Clusterware, you can migrate OCR to reside on Oracle ASM, and take advantage of the improvements in managing Oracle Clusterware storage.
Note:
If you upgrade from a previous version of Oracle Clusterware to Oracle Clusterware 12c and you want to store OCR in an Oracle ASM disk group, then you must set the ASM Compatibility compatibility attribute to 11.2.0.2
, or later.
To migrate OCR to Oracle ASM using OCRCONFIG:
The following example shows how to migrate two OCRs to Oracle ASM using OCRCONFIG.
# ocrconfig -add +new_disk_group
# ocrconfig -delete /ocrdata/ocr_1
# ocrconfig -delete /ocrdata/ocr_2
Note:
-
OCR inherits the redundancy of the disk group. If you want high redundancy for OCR, you must configure the disk group with high redundancy when you create it.
-
Oracle recommends that you put the SPFILE for Oracle ASM in this newly-created OCR location.
Adding, Replacing, Repairing, and Removing Oracle Cluster Registry Locations
Manage OCR locations using OCRCONFIG.
The Oracle installation process for Oracle Clusterware gives you the option of automatically mirroring OCR. You can manually put the mirrored OCRs on a shared Network File System (NFS), or on any cluster file system that is certified by Oracle. Alternatively, you can place OCR on Oracle ASM and allow it to create mirrors automatically, depending on the redundancy option you select.
You can manually mirror OCR, as described in the Adding an Oracle Cluster Registry Location section, if you:
-
Upgraded to Oracle Clusterware 12c but did not choose to mirror OCR during the upgrade
-
Created only one OCR location during the Oracle Clusterware installation
Oracle recommends that you configure:
-
At least three OCR locations, if OCR is configured on non-mirrored or non-redundant storage. Oracle strongly recommends that you mirror OCR if the underlying storage is not RAID. Mirroring can help prevent OCR from becoming a single point of failure.
-
At least two OCR locations if OCR is configured on an Oracle ASM disk group. You should configure OCR in two independent disk groups. Typically this is the work area and the recovery area.
-
At least two OCR locations if OCR is configured on mirrored hardware or third-party mirrored volumes.
Note:
-
If the original OCR location does not exist, then you must create an empty (0 byte) OCR location with appropriate permissions before you run the
ocrconfig -add
orocrconfig -replace
commands. -
Ensure that the OCR devices that you specify in the OCR configuration exist and that these OCR devices are valid.
-
Ensure that the Oracle ASM disk group that you specify exists and is mounted.
-
The new OCR file, device, or disk group must be accessible from all of the active nodes in the cluster.
In addition to mirroring OCR locations, managing OCR locations include:
-
Repairing an Oracle Cluster Registry Configuration on a Local Node
-
Overriding the Oracle Cluster Registry Data Loss Protection Mechanism
Note:
The operations in this section affect OCR throughout the entire cluster: the operations change the OCR configuration information in the ocr.loc
file on Linux and UNIX systems and the Registry keys on Windows systems. However, the ocrconfig
command cannot modify OCR configuration information for nodes that are shut down or for nodes on which Oracle Clusterware is not running.
Adding an Oracle Cluster Registry Location
Use the procedure in this section to add an OCR location. Oracle Clusterware can manage up to five redundant OCR locations.
Note:
If OCR resides on a cluster file system file or a network file system, create an empty (0 byte) OCR location file before performing the procedures in this section.
As the root
user, run the following command to add an OCR location to either Oracle ASM or other storage device:
# ocrconfig -add +asm_disk_group | file_name
Note:
On Linux and UNIX systems, you must be root
to run ocrconfig
commands. On Windows systems, the user must be a member of the Administrator's group.
Removing an Oracle Cluster Registry Location
To remove an OCR location or a failed OCR location, at least one other OCR must be online. You can remove an OCR location to reduce OCR-related overhead or to stop mirroring your OCR because you moved OCR to redundant storage such as RAID.
Perform the following procedure as the root
user to remove an OCR location from your Oracle Clusterware environment:
Replacing an Oracle Cluster Registry Location
If you must change an existing OCR location, or change a failed OCR location to a working location, then you can use the following procedure, if all remaining OCR locations remain online. The ocrconfig -replace
command requires that at least two OCR locations are configured.
To change an Oracle Cluster Registry location:
Complete the following procedure:
Related Topics
Repairing an Oracle Cluster Registry Configuration on a Local Node
It may be necessary to repair OCR if your cluster configuration changes while that node is stopped and this node is the only member in the cluster.
Repairing an OCR involves either adding, deleting, or replacing an OCR location. For example, if any node that is part of your current Oracle RAC cluster is shut down, then you must update the OCR configuration on the stopped node to let that node rejoin the cluster after the node is restarted. Use the following command syntax as root
on the restarted node where you use either a destination_file
or +ASM_disk_group
to indicate the current and target OCR locations:
# ocrconfig -repair -replace current_OCR_location -replacement target_OCR_location
This operation only changes OCR on the node on which you run this command. For example, if the OCR location is /dev/sde1
, then use the command syntax ocrconfig -repair -add /dev/sde1
on this node to repair OCR on that node.
Note:
-
You cannot repair the OCR configuration on a node on which the Oracle Cluster Ready Services daemon is running.
-
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. -
If you run the
ocrconfig -add | -repair | -replace
command, then the device, file, or Oracle ASM disk group that you are adding must be accessible. This means that a device must exist. You must create an empty (0 byte) OCR location, or the Oracle ASM disk group must exist and be mounted.
Overriding the Oracle Cluster Registry Data Loss Protection Mechanism
OCR has a mechanism that prevents data loss due to accidental overwrites. If you configure a mirrored OCR and if Oracle Clusterware cannot access the mirrored OCR locations and also cannot verify that the available OCR location contains the most recent configuration, then Oracle Clusterware prevents further modification to the available OCR location. In addition, the process prevents overwriting by prohibiting Oracle Clusterware from starting on the node on which only one OCR is available. In such cases, Oracle Database displays an alert message in either Oracle Enterprise Manager, the Oracle Clusterware alert log files, or both. If this problem is local to only one node, you can use other nodes to start your cluster database.
However, if you are unable to start any cluster node in your environment and if you can neither repair OCR nor restore access to all OCR locations, then you can override the protection mechanism. The procedure described in the following list enables you to start the cluster using the available OCR location. However, overriding the protection mechanism can result in the loss of data that was not available when the previous known good state was created.
Caution:
Overriding OCR using the following procedure can result in the loss of OCR updates that were made between the time of the last known good OCR update made to the currently accessible OCR and the time at which you performed the overwrite. In other words, running the ocrconfig -overwrite
command can result in data loss if the OCR location that you are using to perform the overwrite does not contain the latest configuration updates for your cluster environment.
Perform the following procedure to overwrite OCR if a node cannot start and if the alert log contains CLSD-1009 and CLSD-1011 messages.
Backing Up Oracle Cluster Registry
This section describes how to back up OCR content and use it for recovery. The first method uses automatically generated OCR copies and the second method enables you to issue a backup command manually:
-
Automatic backups: Oracle Clusterware automatically creates OCR backups every four hours. At any one time, Oracle Database always retains the last three backup copies of OCR. The CRSD process that creates the backups also creates and retains an OCR backup for each full day and after each week. You cannot customize the backup frequencies or the number of files that Oracle Database retains.
-
Manual backups: Run the
ocrconfig -manualbackup
command on a node where the Oracle Clusterware stack is up and running to force Oracle Clusterware to perform a backup of OCR at any time, rather than wait for the automatic backup. You must run the command as a user with administrative privileges. The-manualbackup
option is especially useful when you want to obtain a binary backup on demand, such as before you make changes to OCR. The OLR only supports manual backups.
When the clusterware stack is down on all nodes in the cluster, the backups that are listed by the ocrconfig -showbackup
command may differ from node to node.
Note:
After you install or upgrade Oracle Clusterware on a node, or add a node to the cluster, when the root.sh
script finishes, it backs up OLR.
This section includes the following topics:
Listing Backup Files
Run the following command to list the backup files:
ocrconfig -showbackup
The ocrconfig -showbackup
command displays the backup location, timestamp, and the originating node name of the backup files that Oracle Clusterware creates. By default, the -showbackup
option displays information for both automatic and manual backups but you can include the auto
or manual
flag to display only the automatic backup information or only the manual backup information, respectively.
Run the following command to inspect the contents and verify the integrity of the backup file:
ocrdump -backupfile backup_file_name
You can use any backup software to copy the automatically generated backup files at least once daily to a different device from where the primary OCR resides.
As of Oracle Clusterware 12c release 2 (12.2), the default location for generating backups is an Oracle ASM disk group, which you can change between Oracle ASM disk groups, but you cannot change to a local file system. Oracle recommends that you include the backup file created with the OCRCONFIG utility as part of your operating system backup using standard operating system or third-party tools.
Changing Backup Location
Run the following command to change the location where OCR creates backups:
# ocrconfig -backuploc file_name
The file_name
variable in the preceding command can be a full directory path name that is accessible by all nodes, or it can be an Oracle ASM disk group that is mounted on all nodes. You must migrate OCR to Oracle ASM before changing the OCR backup location to an Oracle ASM disk group. You can change the OCR backup location to an Oracle ASM disk group only if there is at least one Oracle ASM OCR location in a separate disk group.
For example, to specify an OCR backup location in a directory:
# ocrconfig -backuploc Grid_home/cdata/cluster3
To specify an OCR backup location in an Oracle ASM disk group:
# ocrconfig –backuploc +bkupdg
Note:
On Linux and UNIX systems, you must be root
user to run most but not all of the ocrconfig
command options. On Windows systems, the user must be a member of the Administrator's group.
Restoring Oracle Cluster Registry
A procedure for OCR restoration for your platform.
If a resource fails, then before attempting to restore OCR, restart the resource. As a definitive verification that OCR failed, run ocrcheck
and if the command returns a failure message, then both the primary OCR and the OCR mirror have failed.
Note:
-
You cannot restore your configuration from an OCR backup file using the
-import
option, which is explained in "Administering Oracle Cluster Registry with Export and Import Commands". You must instead use the-restore
option, as described in the following sections. -
If you store OCR on an Oracle ASM disk group and the disk group is not available, then you must recover and mount the Oracle ASM disk group.
Restoring the Oracle Cluster Registry on Linux or UNIX Systems
Use this procedure to restore OCR on Linux or UNIX systems.
If you are storing OCR on an Oracle ASM disk group, and that disk group is corrupt, then you must restore the Oracle ASM disk group using Oracle ASM utilities, and then mount the disk group again before recovering OCR. Recover OCR by running the ocrconfig -restore
command, as instructed in the following procedure.
Note:
If the original OCR location does not exist, then you must create an empty (0 byte) OCR location with the same name as the original OCR location before you run the ocrconfig -restore
command.
Use the following procedure to restore OCR on Linux or UNIX systems:
Restoring the Oracle Cluster Registry on Windows Systems
Use this procedure to restore OCR on Windows systems.
If you are storing OCR on an Oracle ASM disk group, and that disk group is corrupt, then you must restore the Oracle ASM disk group using Oracle ASM utilities, and then mount the disk group again before recovering OCR. Recover OCR by running the ocrconfig -restore
command.
Note:
If the original OCR location does not exist, then you must create an empty (0 byte) OCR location with the same name as the original OCR location before you run the ocrconfig -restore
command.
Use the following procedure to restore OCR on Windows systems:
Restoring the Oracle Cluster Registry in an Oracle Restart Environment
Use this procedure to restore OCR in an Oracle Restart environment.
Note:
-
OCR is present for backward compatibility.
-
Once an OCR location is created, it does not get updated in the Oracle Restart environment.
-
If the Oracle Restart home has been backed up, and if there is a failure, then restoring the Oracle Restart home restores OCR.
Related Topics
Diagnosing Oracle Cluster Registry Problems
Use the OCRDUMP and OCRCHECK utilities to diagnose OCR problems.
Related Topics
Administering Oracle Cluster Registry with Export and Import Commands
In addition to using the automatically created OCR backup files, you should also export OCR contents before and after making significant configuration changes, such as adding or deleting nodes from your environment, modifying Oracle Clusterware resources, and upgrading, downgrading or creating a database. Do this by using the ocrconfig -export
command, which exports OCR content to a file format.
Caution:
Note the following restrictions for restoring OCR:
-
The file format generated by
ocrconfig -restore
is incompatible with the file format generated byocrconfig -export
. Theocrconfig -export
andocrconfig -import
commands are compatible. Theocrconfig -manualbackup
andocrconfig -restore
commands are compatible. The two file formats are incompatible and must not be interchangeably used. -
When exporting OCR, Oracle recommends including "
ocr
", the cluster name, and the timestamp in the name string. For example:ocr_mycluster1_20090521_2130_export
Using the ocrconfig -export
command also enables you to restore OCR using the -import
option if your configuration changes cause errors. For example, if you have configuration problems that you cannot resolve, or if you are unable to restart Oracle Clusterware after such changes, then restore your configuration using the procedure for your platform.
Oracle recommends that you use either automatic or manual backups, and the ocrconfig -restore
command instead of the ocrconfig -export
and ocrconfig -import
commands to restore OCR for the following reasons:
-
A backup is a consistent snapshot of OCR, whereas an export is not.
-
Backups are created when the system is online. You must shut down Oracle Clusterware on all nodes in the cluster to get a consistent snapshot using the
ocrconfig -export
command. -
You can inspect a backup using the OCRDUMP utility. You cannot inspect the contents of an export.
-
You can list backups with the
ocrconfig -showbackup
command, whereas you must keep track of all generated exports.
This section includes the following topics:
-
Importing Oracle Cluster Registry Content on Linux or UNIX Systems
-
Importing Oracle Cluster Registry Content on Windows Systems
Note:
Most configuration changes that you make not only change OCR contents, the configuration changes also cause file and database object creation. Some of these changes are often not restored when you restore OCR. Do not restore OCR as a correction to revert to previous configurations, if some of these configuration changes should fail. This may result in an OCR location that has contents that do not match the state of the rest of your system.
Importing Oracle Cluster Registry Content on Linux or UNIX Systems
Use this procedure to import OCR on Linux or UNIX systems.
Note:
This procedure assumes default installation of Oracle Clusterware on all nodes in the cluster, where Oracle Clusterware autostart is enabled.
Note:
You can only import an exported OCR. To restore OCR from a backup, you must instead use the -restore
option, as described in "Backing Up Oracle Cluster Registry".
Oracle Local Registry
In Oracle Clusterware 12c, each node in a cluster has a local registry for node-specific resources, called an Oracle Local Registry (OLR), that 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.
By default, OLR is located at Grid_home
/cdata/
host_name
.olr
on each node.
Manage OLR using the OCRCHECK, OCRDUMP, and OCRCONFIG utilities as root
with the -local
option.
-
You can check the status of OLR on the local node using the OCRCHECK utility, as follows:
# ocrcheck -local Status of Oracle Cluster Registry is as follows : Version : 3 Total space (kbytes) : 262132 Used space (kbytes) : 9200 Available space (kbytes) : 252932 ID : 604793089 Device/File Name : /private2/crs/cdata/localhost/dglnx6.olr Device/File integrity check succeeded Local OCR integrity check succeeded
-
You can display the content of OLR on the local node to the text terminal that initiated the program using the OCRDUMP utility, as follows:
# ocrdump -local -stdout
-
You can perform administrative tasks on OLR on the local node using the OCRCONFIG utility.
-
# ocrconfig –local –export file_name
Note:
-
Oracle recommends that you use the
-manualbackup
and-restore
commands and not the-import
and-export
commands. -
When exporting OLR, Oracle recommends including "
olr
", the host name, and the timestamp in the name string. For example:olr_myhost1_20090603_0130_export
-
-
To import a specified file to OLR:
# ocrconfig –local –import file_name
-
# ocrconfig –local –manualbackup
Note:
Oracle Clusterware backs up OLR after installation or upgrade and, by default, periodically backs up OLR, thereafter. At any time after the initial backup, you can manually back up OLR.
Oracle also recommends that you create a new backup when you migrate OCR from Oracle ASM to other storage, or when you migrate OCR from other storage to Oracle ASM.
The default backup location for the OLR is in the path
Grid_home
/cdata/
host_name
. -
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
-
# crsctl stop crs # ocrconfig -local -restore file_name # ocrcheck -local # crsctl start crs $ cluvfy comp olr
-
Upgrading and Downgrading the Oracle Cluster Registry Configuration
When you upgrade Oracle Clusterware, it automatically runs the ocrconfig -upgrade
command. To downgrade, follow the downgrade instructions for each component and also downgrade OCR using the ocrconfig -downgrade
command. If you are upgrading OCR, then you can use the OCRCHECK utility to verify the integrity of OCR.
Managing Voting Files
This section includes the following topics for managing voting files in your cluster:
Caution:
The dd
commands used to back up and recover voting files in previous versions of Oracle Clusterware are not supported in Oracle Clusterware 12c. Restoring voting files that were copied using dd
or cp
commands can prevent the Oracle Clusterware 12c stack from coming up. Use the backup and restore procedures described in this chapter to ensure proper voting file functionality.
Note:
-
Voting file management requires a valid and working OCR. Before you add, delete, replace, or restore voting files, run the
ocrcheck
command asroot
. If OCR is not available or it is corrupt, then you must restore OCR as described in "Restoring Oracle Cluster Registry". -
If you upgrade from a previous version of Oracle Clusterware to Oracle Clusterware 12c and you want to store voting files in an Oracle ASM disk group, then you must set the ASM Compatibility (
COMPATIBLE.ASM
) compatibility attribute to12.1.0.0
.
Storing Voting Files on Oracle ASM
If you choose to store your voting files in Oracle ASM, then Oracle ASM stores all the voting files for the cluster in the disk group you choose.
Oracle ASM manages voting files differently from other files that it stores. You cannot use voting files stored in Oracle ASM and voting files not stored in Oracle ASM in the same cluster.
Once you configure voting files on Oracle ASM, you can only make changes to the voting files' configuration using the crsctl replace votedisk
command. This is true even in cases where there are no working voting files. Despite the fact that crsctl query css votedisk
reports zero vote disks in use, Oracle Clusterware remembers the fact that Oracle ASM was in use and the replace
verb is required. Only after you use the replace
verb to move voting files back to non-Oracle ASM storage are the verbs add css votedisk
and delete css votedisk
again usable.
The number of voting files you can store in a particular Oracle ASM disk group depends upon the redundancy of the disk group.
By default, Oracle ASM puts each voting file in its own failure group within the disk group. A failure group is a subset of the disks in a disk group. Failure groups define disks that share components, such that if one fails then other disks sharing the component might also fail. An example of what you might define as a failure group would be a set of SCSI disks sharing the same SCSI controller. Failure groups are used to determine which Oracle ASM disks to use for storing redundant data. For example, if two-way mirroring is specified for a file, then redundant copies of file extents must be stored in separate failure groups.
The redundancy level that you choose for the Oracle ASM disk group determines how Oracle ASM mirrors files in the disk group, and determines the number of disks and amount of disk space that you require. If the voting files are in a disk group, then the disk groups that contain Oracle Clusterware files (OCR and voting files) have a higher minimum number of failure groups than other disk groups because the voting files are stored in quorum failure groups.
A quorum failure group is a special type of failure group that is used to store the Oracle Clusterware voting files. The quorum failure group is used to ensure that a quorum of the specified failure groups are available. When Oracle ASM mounts a disk group that contains Oracle Clusterware files, the quorum failure group is used to determine if the disk group can be mounted if there is a loss of one or more failure groups. Disks in the quorum failure group do not contain user data, therefore a quorum failure group is not considered when determining redundancy requirements in respect to storing user data.
An Oracle ASM flex disk group is a disk group type that supports Oracle ASM file groups and quota groups. In general, a flex disk group enables users to manage storage at the granularity of the database, in addition to at the disk group level.
Redundancy levels include:
-
External redundancy: An external redundancy disk group requires a minimum of one disk device. The effective disk space in an external redundancy disk group is the sum of the disk space in all of its devices.
Because Oracle ASM does not mirror data in an external redundancy disk group, Oracle recommends that you use external redundancy with storage devices such as RAID, or other similar devices that provide their own data protection mechanisms.
-
Normal redundancy: A normal redundancy disk group requires a minimum of two disk devices (or two failure groups). The effective disk space in a normal redundancy disk group is half the sum of the disk space in all of its devices.
For Oracle Clusterware files, a normal redundancy disk group requires a minimum of three disk devices (two of the three disks are used by failure groups and all three disks are used by the quorum failure group) and provides three voting files and one OCR and mirror of the OCR. When using a normal redundancy disk group, the cluster can survive the loss of one failure group.
-
High redundancy: In a high redundancy disk group, Oracle ASM uses three-way mirroring to increase performance and provide the highest level of reliability. A high redundancy disk group requires a minimum of three disk devices (or three failure groups). The effective disk space in a high redundancy disk group is one-third the sum of the disk space in all of its devices.
For Oracle Clusterware files, a high redundancy disk group requires a minimum of five disk devices (three of the five disks are used by failure groups and all five disks are used by the quorum failure group) and provides five voting files and one OCR and two mirrors of the OCR. With high redundancy, the cluster can survive the loss of two failure groups.
Using the crsctl replace votedisk
command, you can move a given set of voting files from one Oracle ASM disk group into another, or onto a certified file system. If you move voting files from one Oracle ASM disk group to another, then you can change the number of voting files by placing them in a disk group of a different redundancy level as the former disk group.
Note:
-
You cannot directly influence the number of voting files in one disk group.
-
You cannot use the
crsctl add | delete votedisk
commands on voting files stored in Oracle ASM disk groups because Oracle ASM manages the number of voting files according to the redundancy level of the disk group. -
You cannot add a voting file to a cluster file system if the voting files are stored in an Oracle ASM disk group. Oracle does not support having voting files in Oracle ASM and directly on a cluster file system for the same cluster at the same time.
Backing Up Voting Files
Oracle Clusterware automatically backs up voting file data in OCR as part of any configuration change and automatically restores the data to any voting file you add.
If all voting files are corrupted, however, you can restore them as described in "Restoring Voting Files".
Related Topics
Restoring Voting Files
If all of the voting files are corrupted, then you can restore them, as follows:
Adding, Deleting, or Migrating Voting Files
You can add, remove, and migrate voting files after you install Oracle Clusterware. Note that the commands you use to do this are different, depending on whether your voting files are located in Oracle ASM, or are located in another storage option.
Modifying Voting Files that are Stored in Oracle ASM
-
To display the voting file FUID and file path of each current voting file, run the
crsctl query css votedisk
command to display output similar to the following:$ crsctl query css votedisk -- ----- ----------------- --------- --------- ## STATE File Universal Id File Name Disk group 1. ONLINE 6f57843d89464c46ea747362e8a3fa43 (/dev/sdb1) [DATA] 2. ONLINE 7c54856e98474f61bf349401e7c9fb95 (/dev/sdc1) [DATA] 3. ONLINE 9c46232b76234f61fc934673d5c8ec59 (/dev/sdd1) [DATA]
This command returns a disk sequence number, the status of the disk, the FUID, the path of the disk, and the name of the Oracle ASM disk group on which the disk is stored.
-
To migrate voting files from Oracle ASM to an alternative storage device, specify the path to the non-Oracle ASM storage device with which you want to replace the Oracle ASM disk group using the following command:
$ crsctl replace votedisk path_to_voting_disk
You can run this command on any node in the cluster.
-
To replace all voting files not stored in Oracle ASM with voting files managed by Oracle ASM in an Oracle ASM disk group, run the following command:
$ crsctl replace votedisk +asm_disk_group
Modifying Voting Files that are Not Stored on Oracle ASM
-
To display the voting file FUID and file path of each current voting file, run the following command:
$ crsctl query css votedisk ## STATE File Universal Id File Name Disk group -- ----- ----------------- --------- --------- 1. ONLINE 7c54856e98474f61bf349401e7c9fb95 (/cfs/host09_vd3) []
This command returns a disk sequence number, the status of the disk, the FUID, and the path of the disk and no name of an Oracle ASM disk group.
-
To add one or more voting files, run the following command, replacing the
path_to_voting_disk
variable with one or more space-delimited, complete paths to the voting files you want to add:$ crsctl add css votedisk path_to_voting_disk [...]
-
To replace voting file A with voting file B, you must add voting file B, and then delete voting file A. To add a new disk and remove the existing disk, run the following command, replacing the
path_to_voting_diskB
variable with the fully qualified path name of voting file B:$ crsctl add css votedisk path_to_voting_diskB -purge
The
-purge
option deletes existing voting files. -
To remove a voting file, run the following command, specifying one or more space-delimited, voting file FUIDs or comma-delimited directory paths to the voting files you want to remove:
$ crsctl delete css votedisk {FUID | path_to_voting_disk[...]}
Note:
If the cluster is down and cannot restart due to lost voting files, then you must start CSS in exclusive mode by running the following command, as root
:
# crsctl start crs -excl
After you start CSS in exclusive mode, you can replace the voting file, as follows:
# crsctl replace votedisk path_to_voting_disk