Oracle Big Data Appliance Mammoth Install v2.2.1 Is Failing At Step 12 (Doc ID 1594525.1)

Last updated on MARCH 23, 2014

Applies to:

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

Symptoms

Mammoth 2.2.1 installation fails at step 12 with Oracle Data Integrator (ODI) type errors like the following:

ERROR: Puppet agent run on node bda1node03 had errors. List of errors follows
Oct 23 08:42:39 tlbd1q01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[rcu_setup]/returns) change from notrun to 0 failed: /opt
/oracle/rcuintegration-11.1.1.3.3/bin/rcu -silent -databaseType MYSQL -createRepo
sitory -connectString bda1node03.example.com:3306:mysql -dbUser root -schemaPref
ix BDA -component ODI < /opt/oracle/BDAMammoth/bdaconfig/tmp/rcuparams.txt &> /op
t/oracle/BDAMammoth/bdaconfig/tmp/rcucreate_1382542830.out returned 1 instead of
one of [0] at opt/oracle/BDAMammoth/puppet/modules/odi/manifests/odisetup.pp:130
INFO: Also check the log file in /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-tlbd
1q03-2013102384111.log
ERROR: Puppet agent run on node bda1node04 had errors. List of errors follows
Oct 23 08:42:39 tlbd1q01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[rcu_setup]/returns) change from notrun to 0 failed: /opt
/oracle/rcuintegration-11.1.1.3.3/bin/rcu -silent -databaseType MYSQL -createRepo
sitory -connectString bda1node03.example.com:3306:mysql -dbUser root -schemaPref
ix BDA -component ODI < /opt/oracle/BDAMammoth/bdaconfig/tmp/rcuparams.txt &> /op
t/oracle/BDAMammoth/bdaconfig/tmp/rcucreate_1382542830.out returned 1 instead of
one of [0] at opt/oracle/BDAMammoth/puppet/modules/odi/manifests/odisetup.pp:130
Oct 23 08:42:39 bda1node01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[grant_bda_connect_priv] Dependency Exec[rcu_setup] has
failures: true
Oct 23 08:42:39 bda1node01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[grant_bda_connect_priv] Skipping because of failed depe
ndencies
Oct 23 08:42:39 bda1node01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[setup_agent] Skipping because of failed dependencies
Oct 23 08:42:39 bda1node01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[odi-agent] Dependency Exec[rcu_setup] has failures: t
rue
Oct 23 08:42:39 bda1node01 - puppet-master[17408]: (//bda1node04.example.com//Stage[
main]/Odi::Odisetup/Exec[odi-agent]) Skipping because of failed dependencies
INFO: Also check the log file in opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-tlbd
1q04-2013102384111.log

 

Or the following symptom may be noticed:

Hang in step 12 and also below error noticed in '/opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-<nodename>-<timestamp>.log':

change from notrun to 0 failed: /opt/oracle/rcuintegration-11.1.1.3.3/bin/rcu -silent -databaseType MYSQL -createRepository -connectString dpbgp01node03.lacaixa.es:3306:mysql -dbUser root -schemaPrefix BDA -component ODI < /opt/oracle/BDAMammoth/bdaconfig/tmp/rcuparams.txt &> /opt/oracle/BDAMammoth/bdaconfig/tmp/rcucreate_1385641677.out
returned 1 instead of one of [0] at /opt/oracle/BDAMammoth/puppet/modules/odi/manifests/odisetup.pp:131


From the /opt/oracle/BDAMammoth/bdaconfig/tmp/rcucreate_<timestamp>.out file (node 3) the following error may be seen:

Please enter the value of Custom Variable [Supervisor Password] for Component ODI [Min Length:6, Max Length:12]
Value of Custom Variable Supervisor Password is less than minimum length of 6 characters. Value should be between 6 and 12 characters.
Please enter the value of Custom Variable [Supervisor Password] for Component ODI [Min Length:6, Max Length:12]

 

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