My Oracle Support Banner

After Mammoth Upgrade Step 2 Reboot the Kernel is Not Upgraded When "/etc/grub.conf" is Not a Symbolic Link to "/boot/grub/grub.conf" (Doc ID 2303030.1)

Last updated on OCTOBER 04, 2021

Applies to:

Big Data Appliance Integrated Software - Version 4.5.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. 

After the Mammoth upgrade Step 2 reboot the kernel is not upgraded.

Note the example here is based on X6-2 and lower servers on OL6.  See the checks in, How To Upgrade a Kernel on BDA V4.2 and Higher/V4.1 (Doc ID 2033797.1), for the expected output for X6-2 and lower servers on OL7, X7-2/X8-2 servers on OL6 and X7-2/X8-2 servers on OL7.


For example using a Mammoth 4.5 to 4.8 upgrade, after the Step 2 reboot, the kernel remains at the 4.5 version 2.6.39-400.294.1.el6uek.x86_64 rather than being upgraded to the 4.8 version 4.1.12-94.el6uek.x86_64.

For example during 4.5 to 4.8 upgrade after the Step 2 reboot "uname -a" output shows: 

b) The JDK is successfully upgraded.

c) The file /root/BDA_REBOOT_SUCCEEDED is present as it should be.

d) There is sufficient space in /boot as viewed with "df -h /boot".

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
 Proactive Solution
 Reactive Solution
References


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