Restoring Voting Files

If all of the voting files are corrupted, then you can restore them, as follows:

Restore OCR as described in "Restoring Oracle Cluster Registry", if necessary.

This step is necessary only if OCR is also corrupted or otherwise unavailable, such as if OCR is on Oracle ASM and the disk group is no longer available.

See Also:

Oracle Automatic Storage Management Administrator's Guide for more information about managing Oracle ASM disk groups
Run the following command as root from only one node to start the Oracle Clusterware stack in exclusive mode, which does not require voting files to be present or usable:
```
# crsctl start crs -excl
```

Run the crsctl query css votedisk command to retrieve the list of voting files currently defined, 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 list may be empty if all voting files were corrupted, or may have entries that are marked as status 3 or OFF.

Depending on where you store your voting files, do one of the following:
- If the voting files are stored in Oracle ASM, then run the following command to migrate the voting files to the Oracle ASM disk group you specify:
```
crsctl replace votedisk +asm_disk_group
```
  The Oracle ASM disk group to which you migrate the voting files must exist in Oracle ASM. You can use this command whether the voting files were stored in Oracle ASM or some other storage device.
- If you did not store voting files in Oracle ASM, then run the following command using the File Universal Identifier (FUID) obtained in the previous step:
```
$ crsctl delete css votedisk FUID
```
  Add a voting file, as follows:
```
$ crsctl add css votedisk path_to_voting_disk
```
Stop the Oracle Clusterware stack as root:
```
# crsctl stop crs
```
Note:

If the Oracle Clusterware stack is running in exclusive mode, then use the -f option to force the shutdown of the stack.
Restart the Oracle Clusterware stack in normal mode as root:
```
# crsctl start crs
```