My Oracle Support Banner

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 JANUARY 23, 2020

Applies to:

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


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 line 1724
GridSteps::MsgPrint('EE', 'Cannot continue with operation') called at MammothSteps/ line 291
MammothSteps::BdaJsonConfig::ReadFromJSONParamFile('RACKS', '{\x{a} "RACKS" :\x{a} [\x{a} {\x{a} "RACK_NAME" :
"json-selec...') called at MammothSteps/ line 1965
MammothSteps::BdaJsonConfig::GenerateConsolidatedJSONParamFile('HASH(<HASH>)', 'ARRAY(<ARRAY>)', 0) called at
MammothSteps/ line 972
MammothSteps::BdaJsonConfig::LoadJSONConfigFileInt('HASH(<HASH>)', 'HASH(<HASH>)') called at line 2590
GridSteps::LoadJSONConfigFile() called at /opt/oracle/BDAMammoth/bdaconfig/ line 13



To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.