The below two commands are generally
used to check the status of CRS. The first command lists the status of CRS on
the local node where as the other command shows the CRS status across all the
nodes in Cluster.

crsctl check crs <<-- for the local node

crsctl check cluster <<-- for remote nodes in
the cluster

[root@node1-pub ~]# crsctl check crs

Cluster Synchronization Services appears healthy

Cluster Ready Services appears healthy

Event Manager appears healthy

[root@node1-pub ~]#

For the below command to run, CSS
needs to be running on the local node. The "ONLINE" status for remote
node says that CSS is running on that node. When CSS is down on the remote
node, the status of "OFFLINE" is displayed for that node.

The ocrcheck command displays the no. of OCR files configured in
the Cluster. It is primarily used to chck the integrity of the OCR files. It
also displays the version of OCR as well as storage space information. You can
only have 2 OCR files at max.

Oracle performs physical backup of OCR
devices every 4 hours under the default backup directory
$ORA_CRS_HOME/cdata/<CLUSTER_NAME>and then it rolls that forward to Daily, weekly and monthly backup. You
can get the backup information by executing below command.

ocrconfig -showbackup

[root@node1-pub ~]# ocrconfig -showbackup

node2-pub2007/09/03 17:46:47/u01/app/crs/cdata/test-crs/backup00.ocr

node2-pub2007/09/03 13:46:45/u01/app/crs/cdata/test-crs/backup01.ocr

node2-pub2007/09/03 09:46:44/u01/app/crs/cdata/test-crs/backup02.ocr

node2-pub2007/09/03 01:46:39/u01/app/crs/cdata/test-crs/day.ocr

node2-pub2007/09/03 01:46:39/u01/app/crs/cdata/test-crs/week.ocr

[root@node1-pub ~]#

Manually backing up the OCR

ocrconfig -manualbackup <<--Physical Backup of OCR

The above command backs up OCR under
the default Backup directory. You can export the contents of the OCR using
below command (Logical backup).

(A)Take the Services, Database, ASM Instances and nodeapps down on both the
Nodes in Cluster. Also disable the nodeapps, asm and database instances to
prevent them from restarting in case if this node gets rebooted during this
process.

srvctl stop service -d test

srvctl stop database -d test

srvctl stop asm -n node1-pub

srvctl stop asm -n node2-pub

srvctl stop nodeapps -n node1-pub,node1-pub2

srvctl disable instance -d test -i test1,test2

srvctl disable asm -n node1-pub

srvctl disable asm -n node2-pub

srvctl disable nodeapps -n node1-pub

srvctl disable nodeapps -n node2-pub

(B)Modify the /etc/hosts and/or DNS, ifcfg-eth0 (local node) with the new IP
values on All the Nodes

(C)Restart the specific network interface in order to use the new IP.

ifconfig eth0 down

ifconfig eth0 up

Or, you can restart the network.
CAUTION: on NAS, restarting entire network may cause the node to be rebooted.

(D)Update the OCR with the New Public IP information.

In case of public IP, you have to delete the interface first and then
add it back with the new IP address. As oracle user, Issue the below command:

oifcfg delif -global eth0

oifcfg setif -global eth0/192.168.10.0:public

(E)Update the OCR with the New Virtual IP.

Virtual IP is part of the nodeapps and so you can modify the nodeapps to
update the Virtual IP information. As privileged user (root), Issue the below
commands: