Last updated on JANUARY 29, 2014
Applies to:Big Data Appliance Integrated Software - Version 2.3.1 and later
Extending the CDH cluster with BDA software version 2.3.1 fails running step 2:
The following succeeds creating the mammoth-params file:
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/bda1node01-20140122192527.log and traces in /opt/oracle/BDAMammoth/bdaconfig/tmp/bda1node01-20140122192527.trc
INFO: Checking configuration file /opt/oracle/bda/install/state/mammoth-saved.params...
INFO: Using saved configuration file /opt/oracle/bda/install/state/mammoth-saved.params
INFO: To use the generated configuration file, remove /opt/oracle/bda/install/state/mammoth-saved.params
INFO: Loading configuration file /opt/oracle/bda/install/state/mammoth-saved.params...
INFO: Reading component versions from /opt/oracle/BDAMammoth/bdaconfig/COMPONENTS
INFO: Nodes from this rack are already in the cluster
Enter extension number (or just if none): 1
SUCCESS: Successfully generated parameter file mammoth-bda1-1.params
However the following error is seen while running step 2 of the mammoth installation:
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-02-20140122192620.log and traces in /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-02-20140122192620.trc
INFO: Checking configuration file /opt/oracle/BDAMammoth/bdaconfig/../mammoth-bda1.params...
ERROR: An Appliance of name bda1 has already been installed.
ERROR: Cannot continue with install. #Step 2#
INFO: Time spent in step 2 SetupPuppet is 0 seconds.
The trace shows that it failed at step 2:
GridSteps::DieTrap('Exiting...') called at GridSteps.pm line 1063
GridSteps::MsgPrint('EE', 'Cannot continue with install', 2) called at GridSteps.pm line 790
GridSteps::CheckStepAndLock(2) called at /opt/oracle/BDAMammoth/bdaconfig/GridInst.pl line 272
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms