Oracle Database Appliance - 3 Observations and 3 Resolutions

Oracle Database Appliance - 3 Observations and 3 Resolutions

During last couple weeks, I have been involved in various ODA activities from patching of an existing ODA to latest version to setting up new environments on ODA X5-2
I thought to share some lesson learnt :
 
1)  Patch failure
 
If you encounter in a situation which ODA patch fails and reports the following error 
Unable to get the nodenumber in the chassis
The resolution is to create /opt/oracle/oak/conf/node_num.conf on each compute node and add NODENUM=0 or NODENUM=1.

2) Network issue
 
If you setup new ODA and in the first boot, it should ask for fiber or copper connection and after providing the right option, ODA will keep the appropriate driver and will remove unnecessary drivers. If you do not see it in any new ODA x3-2 onwards when it is booted for the first time, you may see issue with setting up network later. 
To fix the issue, before further progress with deployment and setting up environment, run /opt/oracle/oak/lib/SetupX4Network.pl 

3)  Some oakcli commands fail
You may notice that some oakcli commands fail with the following error:


OAKERR:6000 Exception encountered in Module getMasterNode
OAKERR:6002 No master node was found 

This cause usually could be that the process cannot connect to oakd daemon on ODA. 
You could confirm this with running
oakcli show ismaster
If this command fails, it could be fixed by bouncing oakd using oakcli. As long as oakcli show ismaster does not work well, you may experience failure of some oakcli commands.

 


During last couple weeks, I have been involved in various ODA activities from patching of an existing ODA to latest version to setting up new environments on ODA X5-2
I thought to share some lesson learnt :
 
1)  Patch failure
 
If you encounter in a situation which ODA patch fails and reports the following error 
Unable to get the nodenumber in the chassis
The resolution is to create /opt/oracle/oak/conf/node_num.conf on each compute node and add NODENUM=0 or NODENUM=1.

2) Network issue
 
If you setup new ODA and in the first boot, it should ask for fiber or copper connection and after providing the right option, ODA will keep the appropriate driver and will remove unnecessary drivers. If you do not see it in any new ODA x3-2 onwards when it is booted for the first time, you may see issue with setting up network later. 
To fix the issue, before further progress with deployment and setting up environment, run /opt/oracle/oak/lib/SetupX4Network.pl 

3)  Some oakcli commands fail
You may notice that some oakcli commands fail with the following error:


OAKERR:6000 Exception encountered in Module getMasterNode
OAKERR:6002 No master node was found 

This cause usually could be that the process cannot connect to oakd daemon on ODA. 
You could confirm this with running
oakcli show ismaster
If this command fails, it could be fixed by bouncing oakd using oakcli. As long as oakcli show ismaster does not work well, you may experience failure of some oakcli commands.