My Oracle Support Banner

Upgrade to 4.13 Fails on Step 8: Cleaning up install, When Setting up BDM Due to Invalid MIT Kerberos Credentials (Doc ID 2487744.1)

Last updated on JANUARY 09, 2020

Applies to:

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

Symptoms

NOTE: In the examples below, the bigdatamgr, bdmroothdfs are internal names used by Mammoth.

Upgrading to BDA 4.13 fails on Step 8 "Cleaning up install", when setting up Big Data Manager(BDM) due to MIT Kerberos credential failures. 

The Step 8 failure looks like:

************************************
Error [21587]: (//<HOSTNAME3>.<DOMAIN>//Stage[main]/Bdm::Addbdm/Exec[add_bdm]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/addbdm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/addbdm_<##>.out returned 1 instead of one of [0]
************************************

Checking the /opt/oracle/BDAMammoth/bdaconfig/tmp/addbdm_<##>.out on Node 3 shows an MIT Kerberos credential failure like:

...
kinit: Client 'bigdatamgr/@<REALM>' not found in Kerberos database while getting initial credentials
kinit: Client 'hdfs/@<REALM>' not found in Kerberos database while getting initial credentials
...
bigdatamgr.keytab: No such file or directory
...

 

Cause

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
Symptoms
Cause
Solution


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