ODA: oakcli deploy fails with ERROR : Invalid nodenumber obtained, cannot continue

Asset ID:	1-72-1595593.1
Update Date:	2014-11-06
Keywords:

Solution Type Problem Resolution Sure

Solution 1595593.1 : ODA: oakcli deploy fails with ERROR : Invalid nodenumber obtained, cannot continue

Applies to:

Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Symptoms

oakcli deploy fails with the below error at Step 0:

ERROR : Invalid nodenumber obtained, cannot continue

Changes

New deployment

Cause

The nodenumber could not be determined during the deployment and the script fails. There are two possible reasons:

Cause 1. The nodes from multiple ODAs are mixed during racking. This can be determined by running:

/root/Extras/oakimagevalidate.pl

Below is the output when the nodes have different serial numbers:

Trying to get node number from Topology Validation tool
Topology Validation tool returned node number:0
ERROR: Invalid System Serial number

Cause 2. The file /opt/oracle/oak/conf/node_num.conf does not exist or is blank on one or both the nodes. This could happen if the nodes are powered up before the cabling is complete.

Solution

Solution 1. Re-rack the nodes with the correct corresponding serial numbers. Cleanup the deployment and re-deploy.

Solution 2. Where node_num.conf does not exist or blank:

First, create the /opt/oracle/oak/conf/node_num.conf file manually with NODENUM value as below:

On Node 1 => NODENUM=0

On Node 2 => NODENUM=1

Run the oakcli deploy.

If this fails, then it is best to cleanup the deployment and re-deploy.

References

<BUG:17556815> - DEPLOYING V2 ODA/OAK 2.6 FAILS W/INVALID NODENUMBER OBTAINED, CANNOT CONTINUE.
<BUG:17330027> - INVALID NODENUMBER OBTAINED, CANNOT CONTINUE
<NOTE:1409835.1> - ODA (Oracle Database Appliance): Deployment & Cleanup Steps

Attachments

This solution has no attachment