My Oracle Support Banner

Mammoth Upgrade to 5.1 Or Mammoth 5.1 Install Fails on "SetupKDC" in Clusters AD Kerberos Enabled (Doc ID 2642663.1)

Last updated on FEBRUARY 28, 2020

Applies to:

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

Symptoms

  

NOTE: In the examples below, user details, UUID values, hostnames, etc. represent a fictitious sample. Any similarity to actual persons, environments, or entities, is purely coincidental and not intended in any manner. 

Mammoth upgrade to 5.1 or Mammoth 5.1 installations fail on the "SetupKDC" step in clusters with AD Kerberos enabled.

The Mammoth failure at the "SetupKDC" step looks like:

"ERROR: Unable to create oracle user on the Active Directory, please make sure that
the Oracle OS and Cloudera admin passwords meet your Active Directory password restrictions before continuing."

Checking the file: /opt/oracle/BDAMammoth/bdaconfig/tmp/createaduser.out, shows output like below, which indicates there is a problem creating a user called oracle@<REALM>.

ldap_add: Already exists (68)
additional info: 00002071: UpdErr: DSID-<DSID>, problem 6005 (ENTRY_EXISTS), data 0 adding new entry "CN=oracle,ou=<ORGANIZATION_UNIT>,dc=<REALM>"

However it is confirmed that the Oracle OS password and Cloudera admin passwords have been verified to meet all Active Directory password restrictions.

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.