ODA X5-2 Failure In Redeployment at Step 16 After Replacing IB with 10GBe Cards and Cabling

Asset ID:	1-72-2046446.1
Update Date:	2015-09-28
Keywords:

Solution Type Problem Resolution Sure

Solution 2046446.1 : ODA X5-2 Failure In Redeployment at Step 16 After Replacing IB with 10GBe Cards and Cabling

Applies to:

Oracle Database Appliance X5-2 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

X5-2 problem unable to complete deployment after swapping out the IB cards for 10GBe cards.
Logfiles showed that the error was consistently seen at Step 16 in the redeployment process.

Changes

The X5-2 by default uses IB / Infiniband connectivity between the two ODA Nodes.
The X5-2 ODA has the flexibility to use either the default IB interconnect or 10GBe but you will need to replace the IB cards with 10GBe cards.
In this case the IB was replaced with 10GBe cards.

For X5-2 12.1.2.2 and 12.1.2.3 requires a redeployment* of the ODA after replacing the IB with 10GBe cards
* 12.1.2.4 eliminates the requirement to redeploy if adding the 10GBe cards.

Cause

The problem was due to attempting to create an object that already existed.

Reviewing the log files confirmed that there had been more than one attempt to run the deployment after removing the IB cards and replacing with the 10Gbe cards.

Review of deployment trace file also confirmed that step 16 had already successfully completed creating the mdm database.
Re-running the deployment a second time failed consistently at step 16 as 'unable to complete'.
Trace file for step 16 showed that the name of the management db already existed - the error was due to a check preventing the deployment from creating the management db for a second time.

Solution

There are methods which can be used to manually complete a sequence of deployment steps by range or by step.
The solution to this issue is to run the rest of the steps 17,18,19,20,21,22,23.

This Note is regarding a problem during the change from IB to 10GBe requiring a redeployment: IB currently is unique to the X5-2 (and newer) Hardware platforms.
- To confirm which Hardware platform you are using as well as Bare Metal or Virtualized issue the following oakcli command

oakcli show env_hw

The resolution to this problem is generic and only requires confirming which steps need to be executed to complete the deployment.
Meaning: The actual Hardware platform used has no impact on the syntax used to run manual deployment steps.
There is an extra flag required due to the using Virtualized Platform (ODAVP) which is fairly consistent for all oakcli commands and also the GridInst.pl command used in this example.

As root cd to the following directory

cd /opt/oracle/oak/onecmd/

execute ./GridInst.pl -l or ./GridInst.pl -o -l (if using ODAVP) to determine the names and steps for your version:

NOTE: For more examples of using GridInst.pl see Note 2027830.1 ODA Deployment Steps By Version
-- An Outline of the Order and Number of Steps for Each ODA Version

Then, once you have determine the proper step or range of steps to complete the deployment

Examples

For ODA Bare Metal

./GridInst.pl -r 17-23

For ODAVP ( Virtualized Platform)

./GridInst.pl -o -r 17-23

After running the range of steps manually from 17-23 the deployment was completed successfully.

References

<NOTE:464666.1> - How to Send a File to Oracle Support Using FTPS
<NOTE:1600317.1> - ODA How to alter the DNS Names after the original configuration using GridInst.pl and the onecommand.params file ( Bare Metal )
<NOTE:952903.1> - How to update the IP address of the SCAN VIP resources (ora.scan{n}.vip)
<NOTE:2027830.1> - ODA Deployment Steps By Version -- An Outline of the Order and Number of Steps for Each ODA Version

Attachments

This solution has no attachment