How to Recreate OCR / Voting Disk Accidentally Deleted [ID 399482.1]

How to Recreate OCR/Voting Disk Accidentally Deleted [ID 399482.1]
	Modified 26-OCT-2010     Type HOWTO     Status PUBLISHED

In this Document
  Goal
  Solution

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Oracle Server - Standard Edition - Version: 10.2.0.1 to 11.1.0.7   [Release: 10.2 to 11.1]
Linux x86
HP-UX PA-RISC (64-bit)
IBM AIX on POWER Systems (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
HP-UX Itanium
Linux x86-64
Linux Itanium
HP Tru64 UNIX
Oracle Clusterware

Goal

The goal of this document is to help customers who have accidentally deleted the OCR, voting disk or the files that are required for the operation of Oracle clusterware.

Depending on the issue, it may or may not be good idea to execute the steps provided.

• OCR 
  • If the OCR has been deleted, then check if the OCR mirror is OK and vice versa. It may be prudent to use the OCR mirror to create the OCR. For steps on this check the documentation Oracle� Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide 
  • If the OCR mirror and OCR have been deleted, then it may be faster to restore the OCR using the OCR backups. For steps on this check the documentation Oracle�Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide
• Voting Disk  
  • If there are multiple voting disks and one was accidentally deleted, then check if there are any backups of this voting disk. If there are no backups then we can add one using the crsctl add votedisk command. The complete steps are in the Oracle� Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide
• SCLS directories
  • These are internal only directories which are created by root.sh, if this directory is accidentally removed then they can only be created by the steps documented below
• Socket files in /tmp/.oracle or /var/tmp/.oracle
  • If these files are accidentally deleted, then stop the Oracle Clusterware on that node and restart it again. This will  recreate these socket files. If the socket files for cssd is deleted then the Oracle Clusterware stack may not come down in which case the node has to be bounced.

Solution

If none of the steps documented above can be used to restore the file that was accidentally deleted or is corrupted, then the following steps can be used to re-create/reinstantiate these files. The following steps require complete downtime on all the nodes.

1. Shutdown the Oracle Clusterware stack on all the nodes using command crsctl stop crs as root user.
2. Backup the entire Oracle Clusterware home.
3. Execute <CRS_HOME>/install/rootdelete.sh on all nodes
4. Execute <CRS_HOME>/install/rootdeinstall.sh on the node which is supposed to be the first node
5. The following commands should return nothing
   • ps -e | grep -i 'ocs[s]d'
   • ps -e | grep -i 'cr[s]d.bin'
   • ps -e | grep -i 'ev[m]d.bin'
6. Execute <CRS_HOME>/root.sh on first node
7. After successful root.sh execution on first node Execute root.sh on the rest of the nodes of the cluster
8. For 10gR2, use racgons. For 11g use onsconfig command. Examples for each are provided below.
   
   For 10g
   Execute as owner (generally oracle) of CRS_HOME command 
   <CRS_HOME>/install/racgons add_config hostname1:port hostname2:port

$/u01/crs/install/racgons add_config halinux1:6251 halinux2:6251

For 11g
Execute as owner (generally oracle) of CRS_HOME command
<CRS_HOME>/install/onsconfig add_config hostname1:port hostname2:port

$/u01/crs/install/onsconfig add_config halinux1:6251 halinux2:6251

 

1. Execute as owner of CRS_HOME (generally oracle)  <CRS_HOME>/bin/oifcfg setif -global. Please review Note 283684.1 for details.

$/u01/crs/bin/oifcfg setif -global  eth0/192.168.0.0:cluster_interconnect eth1/10.35.140.0:public

 

1. Add listener using netca. This may give errors if the listener.ora contains the entries already. If this is the case, move the listener.ora to /tmp from the $ORACLE_HOME/network/admin or from the $TNS_ADMIN directory if the TNS_ADMIN environmental is defined and then run netca. Add all the listeners that were added earlier.
2. Add ASM & database resource to the OCR using the appropriate srvctl add database command as the user who owns the ASM & database resource. Please ensure that this is not run as root user
3. Add  Instance, services using approproate srvctl add commands. Please refer to the documentation for the exact commands.
4. execute cluvfy stage -post crsinst -n node1,node2    ### Please ensure to replace node1,node2 with the node names of the cluster

 

 

 

 

------------------------------------------------------------------------------