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
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:
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>.
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.
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