My Oracle Support Banner

After Step 3 of BDA V4.7 Upgrade Rebooted Nodes Come Back Online with "/root/BDA_REBOOT_FAILED" Due to "ERROR: Wrong Hadoop parcel version" or "/root/BDA_REBOOT_WARNINGS" Due to "WARNING:Wrong Alternatives for Hadoop" (Doc ID 2218123.1)

Last updated on JANUARY 15, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.7.0 to 4.8.0 [Release 4.7 to 4.8]
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. 

During upgrade to BDA V4.7 after the Step 3 reboot it is found that one or more nodes come back online but /root/BDA_REBOOT_SUCCEEDED is not present. Instead one of these files is found:

/root/BDA_REBOOT_FAILED
or
/root/BDA_REBOOT_WARNINGS

 

Detailed symptoms are as below. The output here is based on a BDA V4.6 to 4.7 upgrade.

1. On one or more nodes: /root/BDA_REBOOT_FAILED or /etc/BDA_REBOOT_WARNINGS is found instead of /root/BDA_REBOOT_SUCCEEDED.

2. The file /root/BDA_REBOOT_FAILED contains output like below on a 4.6 to 4.7 upgrade: 

  

 

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.