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"
Last updated on SEPTEMBER 08, 2017
Applies to:Big Data Appliance Integrated Software - Version 4.5.0 and later
After the Mammoth upgrade Step 2 reboot the kernel is not upgraded.
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".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms