root.sh script failed on grid interface on 11.2.0.1 in Solaris 11 (Sparc/X64).




Errors may occurs as followed:

root.sh
=======
Start action for daemon aborted
CRS-26
               
crsdelete_node1.log
=========================
2014-12-01 11:51:32: ASM_DISCOVERY_STRING=/dev/rdsk/*
2014-12-01 11:51:32: ASM_DISKS=/dev/rdsk/c0t600144F0CCBE800800005472E7250001d0s0
2014-12-01 11:51:32: VOTING_DISKS=NO_VAL <<< no voting disk found.

ocssd.log
=========
2014-12-02 12:27:00.884: [ CLSF][1]Allocated CLSF context
2014-12-02 12:27:00.884: [ CSSD][1]clssnmlalloccx:phyname node1
2014-12-02 12:27:00.884: [ CSSD][1](:CSSNM00031:)clssnmlgetslot:No voting files available on node node1

Log file Collection:
==============
As root, please run $GRID_HOME/bin/diagcollection.sh -all" on failed nodes.

Note.330358.1 CRS 10gR2/ 11gR1/ 11gR2 Diagnostic Collection Guide


Solution:

1. Verifying shared storage accessibility using below command as grid user.

./runcluvfy.sh comp ssa -n node1 -verbose
./runcluvfy.sh comp ssa -n node1,node2 -verbose

If its ok follow the 2 steps or please provide the permission as below.

# chown grid:asmadmin /dev/rdsk/xyz
# chmod 660 /dev/rdsk/xyz

2. Make sure the voting disk is accessible, permissions and ownership is correct on both nodes.

Once fixed, kindly follow the steps on root.sh failed node.

Step 1: As root, run "$GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force"
Step2: As root, run root.sh

3. If the issue still persistent, Please check the private network interface weather it normal NIC or IB (Infinity Band). Because the 11.2.0.1 Grid home is not supported the IB network.

In case the private interface with IB network, please use a current supported release of GRID like 11.2.0.3, 11.2.0.4 or 12.1.0.2 and RDBMS version is 11.2.0.1

11.2.0.3, 11.2.0.4 or 12.1.0.2 Grid Infrastructure/CRS clusterware and a 11.2.0.1 RDBMS /RAC database home is oracle certified.

My suggestion is 11.2.0.4 Grid Infrastructure/CRS clusterware and a 11.2.0.1 RDBMS /RAC database home. Although better would be if also the database is 11.2.0.4, for supporting reasons.

Comments

Popular posts from this blog

[INS-40718] Single Client Access Name (SCAN): could not be resolved. ( LDOMS & Zones)

Bare Metal Restore Procedure for Compute Nodes on an Exadata Environment