My Oracle Support Banner

Migrating a Failed Mammoth Node with "bdacli admin_cluster migrate <ORIGINAL_MAMMOTH_HOSTNAME>" on BDA 5.2 with CA Signed Certificates Fails Running enablecmhttps.sh (Doc ID 2945255.1)

Last updated on MAY 30, 2024

Applies to:

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

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

Migrating a failed Mammoth node to another host on BDA 5.2 using the command below fails in the InstallHadoop step. Note the command is run on the node which will become the new Mammoth node. 

 

Changes

 

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
Changes
Cause
Solution
 Restore the certificates in /opt/cloudera/security from backup
 Update /opt/oracle/bda/mammoth-5.2.0/ansible/bdaplaybook/templates/hadoop/enablecmhttps.j2
 Rerun the migration 
References


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