8.5.9 Updating Individual Packages

Due to security findings or customization, you may need to update individual (general purpose) Linux packages supplied in the Exadata release. You can do this by removing the relevant exadata-*-computenode-exact RPM first. The relevant RPM depends on your system configuration:

• exadata-ib-computenode-exact: Bare-metal system with InfiniBand Network Fabric.

• exadata-sun-computenode-exact: Bare-metal system or KVM host with RoCE Network Fabric.

• exadata-sun-kvm-computenode-exact: Virtual machine (VM) guests on Oracle Linux KVM.

• exadata-sun-ovs-computenode-exact: Oracle VM Server (OVS) management domain (Dom0).

• exadata-sun-vm-computenode-exact: Oracle VM Server (OVS) user domain (DomU).

Removing the RPM does not impact any functionality, but it removes a logical lock allowing you to update specific individual Linux RPMs.

If required, you can remove the relevant exadata-*-computenode-exact RPM. For example, to remove the RPM from a KVM host, run:

[root@dm01]# rpm -e exadata-sun-computenode-exact

Do not use yum or dnf, as these commands may also remove other RPMs in the dependency chain.

When updating to a new release, the update utility attempts to restore the relevant exadata-*-computenode-exact package. If the exadata-*-computenode-exact RPM cannot be restored, the update utility falls back to using the exadata-*-computenode-minimum RPM.

Note:

Do not force in packages using the rpm -Uvh --nodeps command, unless directed by Oracle Support Services.