Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2043132.1
Update Date:2018-01-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  2043132.1 :   ODA "NOT_ENOUGH_SPACE_ON_FLASH" Error During Step 1 When Attempting To Deploy BM End User Bundle 12.x.  


Related Items
  • Oracle Database Appliance X4-2
  •  
  • Oracle Database Appliance
  •  
  • Oracle Database Appliance X3-2
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
  •  




Created from <SR 3-10958936581>

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Successfully performed a Bare Metal Restore using ODA 12.1.2.x ISO BMR file p12999313_12###_Linux-x86-64.zip.

While deploying the 12.1.2.x End User Bundle, Step 1 Fails - Network Setup is throwing the following error message:

...
 ERROR : Ran '/usr/bin/ssh -l root 192.168.16.25 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20150624115520.sh' and it returned code(9) and output is:
 
"NOT_ENOUGH_SPACE_ON_FLASH" not allowed while "strict subs" in use at GridSteps.pm line 15505.
 Compilation failed in require at /opt/oracle/oak/onecmd/GridInst.pl line 102.
 BEGIN failed--compilation aborted at /opt/oracle/oak/onecmd/GridInst.pl line 102.
...

 
IMPORTANT

The ODA platform being reimaged was a X3-2.
ODA X3-2 , ODA X4-2 and ODA V1 does not have a FLASH diskgroup
ODA X5-2 does have FLASH

An X3-2 deployment would not be expected to fail with "NOT_ENOUGH_SPACE_ON_FLASH" during the network portion of the deployment and on an ODA HW platform which does not utilize FLASH.

Changes

 Reimaging an existing ODA X3-2.

Cause

One of the two ODA X3-2 Nodes was reimaged but the second node OS was not reimaged.

The underlying cause was attempting to run the deployment on an ODA with two different ISO images.

Investigation confirmed that the ISO was applied on only one of the two nodes resulting in a mismatch of ISO images during the deployment, thus resulting in the unexpected error messages.

ODA factory shipped boxes will have the Bare Metal OS pre-installed on both ODA servers.

While some ODA commands and patches can be executed from the first node, a re-image using the respective ISO requires re-imaging both nodes before deployment.
 

Solution

Bare Metal Restore (BMR) both nodes using the same ODA version ISO to keep the images consistent between nodes.

This is typically done using the ILOM and a redirect but can also be performed local to each node.
Once both nodes have been re-imaged, then run FIRSTNET as described in the ODA set-up poster for your version.
Then copy over the ODA Bundle Patch and unpack the bundle as stated in the readme for the 12.1.2.x version.

 See <Document 888888.1> for current ODA version bundles.
 

For the latest documentation go to:

  --> docs.oracle.com
    --> Engineered systems
      ---> Oracle Database Appliance



References

<NOTE:888888.1> - Oracle Database Appliance - 12.2.1.1 and 2.X Supported ODA Versions & Known Issues

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback