Step 1 of Mammoth 4.10 Install on X7-2 Rack Fails with "ERROR: Command parsing param file returned status 256"

(Doc ID 2350234.1)

Last updated on FEBRUARY 10, 2018

Applies to:

Big Data Appliance Integrated Software - Version 4.10.0 and later
Linux x86-64

Symptoms

Step 1 of a Mammoth 4.10 install on X7-2 servers fails with: "ERROR: Command parsing param file returned status 256".

The Step 1 failure looks like:

ERROR: Command parsing param file returned status 256
ERROR: Cannot continue with operation

The trace file shows that Mammoth is failing when generatingthe  consolidated JSON parameter file:

GridSteps::DieTrap('Exiting...') called at GridSteps.pm line 1724
GridSteps::MsgPrint('EE', 'Cannot continue with operation') called at MammothSteps/BdaJsonConfig.pm line 291
MammothSteps::BdaJsonConfig::ReadFromJSONParamFile('RACKS', '{\x{a} "RACKS" :\x{a} [\x{a} {\x{a} "RACK_NAME" :
"json-selec...') called at MammothSteps/BdaJsonConfig.pm line 1965
MammothSteps::BdaJsonConfig::GenerateConsolidatedJSONParamFile('HASH(0x###)', 'ARRAY(0x###)', 0) called at
MammothSteps/BdaJsonConfig.pm line 972
MammothSteps::BdaJsonConfig::LoadJSONConfigFileInt('HASH(0x###)', 'HASH(0x2###)') called at GridSteps.pm line 2590
GridSteps::LoadJSONConfigFile() called at /opt/oracle/BDAMammoth/bdaconfig/GridInst.pl line 13

 



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms