8.9 Using Exadata Autonomous Kernel Update

Optionally use Exadata Autonomous Kernel Update to retrieve applicable Oracle Linux kernel updates from the Ksplice update service and apply them to the running kernel without requiring a system reboot.

Oracle Exadata System Software release 26.2.0 introduces Exadata Autonomous Kernel Update, an opt-in capability that provides autonomous online Oracle Linux kernel updates for Oracle Exadata database servers and storage servers.

Exadata Autonomous Kernel Update is disabled by default. When fully enabled, the system automatically connects to the Ksplice update service, retrieves applicable Oracle Linux kernel updates, and applies them to the running kernel without requiring a system reboot.

Exadata Autonomous Kernel Update provides an automated alternative to preexisting manual Oracle Linux kernel update procedures described in Installing Kernel Updates on Exadata Database Servers and Installing Kernel Updates on Oracle Exadata Storage Servers.

Exadata Autonomous Kernel Update also complements the existing Exadata software update mechanisms. It does not replace Exadata Live Update, conventional Exadata updates, or regular Exadata maintenance releases. Exadata image updates continue to establish the durable operating system and kernel baseline, while Exadata Autonomous Kernel Update provides online runtime remediation between those updates.

Requirements

Before enabling Exadata Autonomous Kernel Update, ensure that the following requirements are met:

  • The system runs Oracle Exadata System Software release 26.2.0 or later.

  • The system has outbound HTTPS connectivity to updates.ksplice.com, either directly or through an HTTPS proxy.

  • A valid Ksplice access key is available.

    The access key is normally obtained through the Unbreakable Linux Network (ULN) Systems interface. It can also be viewed through status-ksplice.oracle.com. Treat the access key as a credential and do not expose it in unsecured correspondence, scripts, or shared configuration files.

  • A scheduled maintenance window is available during which the updates can be applied.

Note also:

  • Exadata Autonomous Kernel Update supports Oracle Linux kernel updates only. User-space updates are not supported on Exadata.

  • On each server, Exadata Autonomous Kernel Update is configured through settings in /etc/uptrack/uptrack.conf. It is not configured through DBMCLI or CELLCLI.

Enabling Exadata Autonomous Kernel Update

  1. Back up the existing configuration in /etc/uptrack/uptrack.conf.

    For example:

    # cp -p /etc/uptrack/uptrack.conf /etc/uptrack/uptrack.conf.pre-autonomous
  2. Edit /etc/uptrack/uptrack.conf.

    Add or update the following settings. Retain other site-specific settings already present in the file.

    [Auth]
    accesskey = <Ksplice-access-key>
    
    [Network]
    https_proxy = <proxy-url>
    gconf_proxy_lookup = no
    
    [Settings]
    autoinstall = <yes/no>
    offline_mode = no
    userspace = no
    exadata_cache = yes
    skip_apply_after_pkg_install = true
    upgrade_on_reboot = yes
    warn_missing_packages_on_init = no

    Setting notes:

    • If the system does not require a proxy, leave the https_proxy value empty:

      https_proxy =
    • Specify the application policy by setting the autoinstall value:

      • To enable automatic update retrieval and application, use:

        autoinstall = yes

        With this setting, updates are automatically retrieved and applied without any administrator intervention. Use this setting only during a scheduled maintenance window.

      • To disable automatic update retrieval and application, use:

        autoinstall = no

        With this setting, the system periodically checks for updates and logs the results. Use this setting whenever the system is not in a scheduled maintenance window.

  3. After editing /etc/uptrack/uptrack.conf, verify that Exadata Autonomous Kernel Update is enabled:

    # uptrack-show --verbose

    Confirm that the output contains:

    Running online uptrack.

Listing, Retrieving, and Applying Updates Immediately

When Exadata Autonomous Kernel Update is enabled, an administrator can perform the following immediate actions at any time, regardless of the current application policy:

  • To view a list of currently available updates, run:

    # uptrack-upgrade -v -n

    This command is also useful for verifying access-key authentication and network connectivity.

  • To immediately retrieve and apply all available updates, run:

    # uptrack-upgrade -v -y

    Use this command only during a scheduled maintenance window.

Verifying Applied Updates

Immediately after a successful update, there will be no available (unapplied) updates in the uptrack-show --available output:

# uptrack-show --available
Available updates:
            None
...

If available updates are listed immediately after an update, check the following before retrying:

  • HTTPS connectivity to updates.ksplice.com

  • HTTPS Proxy configuration

  • Ksplice access-key validity

  • Update activity in /var/log/ksplice.log

  • Compatibility of third-party or externally built kernel modules

Additionally:

  • To display updates currently applied to the running kernel, run:

    # uptrack-show
  • To display the effective kernel version after Ksplice updates have been applied, run:

    # uptrack-uname -r

    The effective kernel version can differ from the booted kernel version reported by uname -r.

Disabling Exadata Autonomous Kernel Update

  1. Back up the current configuration in /etc/uptrack/uptrack.conf.

    For example:

    # cp -p /etc/uptrack/uptrack.conf /etc/uptrack/uptrack.conf.pre-disabled
  2. Edit /etc/uptrack/uptrack.conf.

    Remove the access key and HTTPS proxy value (if set), and update the other settings as follows:

    [Auth]
    accesskey = 
    
    [Network]
    https_proxy =
    gconf_proxy_lookup = no
    
    [Settings]
    autoinstall = no
    offline_mode = yes
    userspace = no
    exadata_cache = yes
    skip_apply_after_pkg_install = true
    upgrade_on_reboot = yes
    warn_missing_packages_on_init = no
  3. After editing /etc/uptrack/uptrack.conf, verify that Exadata Autonomous Kernel Update is no longer active:

    # uptrack-show --verbose

    Confirm that the output contains:

    Running offline uptrack.