How to Remove the Unsupported UEK4QU5 Kernel on BDA V4.7,V4.8,V4.9 If It Is Installed But Not Yet Booted Into
(Doc ID 2317630.1)
Last updated on NOVEMBER 14, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.7.0 to 4.9.0 [Release 4.7 to 4.9]
On BDA V4.7, V4.8, V4.9 with OL6 the recommended kernel versions can be found in: Recommended Kernel and Firmware Versions to Avoid Known Issues After Upgrade to BDA V4.7, BDA V4.8, BDA V4.9 (Doc ID 2296538.1).
From that note the recommended OL6 kernel version for BDA V4.7-V4.9 is 4.1.12-94.3.9.el6uek.x86_64 or higher as available in the UEK4QU4 branch in the public yum repository. The current UEK4QU4 branch kernel in public yum is 4.1.12-94.5.9.el6uek.x86_64. You can not upgrade to a UEK4QU5 branch as it is NOT supported. Hence you can not upgrade to 4.1.12-103* which is in the UEK4QU5 stream.
Recommended Kernel and Firmware Versions to Avoid Known Issues After Upgrade to BDA V4.7, BDA V4.8, BDA V4.9 (Doc ID 2296538.1) directs you to How To Upgrade a Kernel on BDA V4.2 and Higher/V4.1 (Doc ID 2033797.1) for details on the kernel upgrade.
If for any reason it happens that the UEK4QU5 kernel, 4.1.12-103* is installed on the system, then after running "reset-grub-conf" as directed by Doc ID 2033797.1, the generated /boot/grub/grub.conf will contain the unsupported UEK4QU5 4.1.12-103* kernel at the top of the file forcing boot into the unsupported UEK4QU5 kernel.
This could happen for example if you used "yum update" to update the kernel instead of the "yum install" command.
In this case you could see output like below indicating both UEK4QU4 and UEK4QU5 kernels would be installed:
Consider the steps here as a way to try and resolve this issue if you have not yet rebooted into the UEK4QU5 kernel. If you have not booted into the UEK4QU5 kernel try removing the unsupported UEK4QU5 4.1.12-103* kernel and regenerate a reset-grub-conf to allow reboot into the latest UEK4QU4 kernel.
If you have already booted into the UEK4QU5 kernel open an SR with Oracle Support.
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