Exadata X8M: Updating KSplice

There are several bugs that ksplice patches fix in Exadata. In our case it was a login issue. It would not allow you to ssh or login via serial console, not good. We installed the ksplice patch on all the nodes per Oracle. Although it is documented it is across a couple links so here is what I had to do:

Checking for a specific fix

In my case I cam looking for a specific bug that is related to my login issue. It may not be exact but it is part of the ksplice and is a good way to check if something is installed without listing all the fixes.

  1. Login lockup issue fix & updating ksplice patches:

Download ksplice kernel updates for Exadata Database Nodes

  1. Check for required ksplice fixes already installed, if it is stop update
# uptrack-show | egrep 'Missing rejected events|RDS peer reboot'
# uname -r
  1. For installing ksplices for Exadata refer to:

Installing ksplice for Exadata (Oracle Link)

  1. Download ksplice and upload to a local or remote mountable source

mkdir -p /mnt/depot /mnt/oel7
mount /mnt/depot
cd /mnt/depot/ad752h
ls -l
-rw-r–r– 1 nobody nobody 69922432 Sep 16 07:26 uptrack-updates-4.14.35-1902.301.1.el7uek.x86_64-20210825-0.noarch.rpm
-rw-r–r– 1 nobody nobody 11282756 Sep 16 10:19 uptrack-updates-4.14.35-2047.502.5.el7uek.x86_64-20210825-0.noarch.rpm

mount -o loop /home/ad752h/OracleLinux-R7-U8-Server-x86_64-dvd.iso /mnt/oel7
umount /mnt/oel7
mount -o loop /u01/ad752h_tmp/OracleLinux-R7-U8-Server-x86_64-dvd.iso /mnt/oel7

yum repolist
yum clean all
yum list installed computenode-exact
yum erase exadata-sun-computenode-exact.noarch -y

Make sure you get the correct kernel: uname -r to get the right patch

yum install uptrack-updates-4.14.35-1902.301.1.el7uek.x86_64-20210825-0.noarch.rpm -y
yum install uptrack-updates-4.14.35-2047.502.5.el7uek.x86_64-20210825-0.noarch.rpm -y

uptrack-show | egrep ‘Missing rejected events|RDS peer reboot’

  • After installing check if fix for connection failure is done:

uptrack-show | egrep ‘Missing rejected events|RDS peer reboot’

[1on6numr] Connection failure after RDS peer reboot.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.