Changes in this Release

This preface lists changes in the Oracle Autonomous Health Framework Checks and Diagnostics User's Guide 26.2.

Exadata Live Update Status Integration in exachk Reports

AHF 26.2 introduces Exadata Live Update status information into the Infrastructure and Configuration Summary section of the exachk HTML and JSON reports under the Oracle Database Server component.

Note:

This feature is applicable only to Exadata systems running in KVM Host or Guest VM environments.

The Live Update status is determined by executing the imagehistory command on each compute node and parsing its output to identify the current patching state of the system.

Exadata Live Update Status Values

The Exadata Live Update Status field can display one of the following four values:

  1. Not Applicable (No Software Updates Applied)

    Displayed when the system has never been patched and remains in its original fresh image state.

    imagehistory shows:

    • Exadata Live Update Version: n/a
    • Imaging mode: fresh
  2. Not Applicable (Traditional Updates Applied)

    Displayed when the most recent update was performed using the traditional (manual) patching method rather than Exadata Live Update.

    In the latest imagehistory entry:
    • Exadata Live Update Version: n/a
  3. Exadata Live Update Pending Reboot to Finalize Outstanding Work

    Displayed when a Live Update has been successfully applied, but a system reboot has not yet occurred to complete the finalization process.

    The latest imagehistory entry contains:
    • Live Update applied. Reboot at any time to finalize outstanding items.
  4. Exadata Live Update Applied Successfully and Finalized at Reboot Time <timestamp>

    Displayed when a Live Update has been applied and subsequently finalized through a system reboot.

    • The <timestamp> reflects the time of finalization.
    • The value is derived from the follow-up imagehistory entry that no longer includes the pending reboot message.

Infrastructure and Configuration Summary Display

A single Exadata Live Update Status row is added to the Oracle Database Server component table within the Infrastructure and Configuration Summary.

  • Compute nodes are grouped based on their Live Update status value.
  • Each group displays the corresponding status, allowing quick identification of nodes requiring attention (for example, pending reboot).

Parent topic: Changes in this Release

New Oracle Orachk and Oracle Exachk Best Practice Checks

Release 25.11 includes the following new Oracle Orachk and Oracle Exachk best practice checks.

Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk

  • Exadata Critical Issue DB55

All checks can be explored in more detail via the Health Check Catalogs.

Related Topics

Parent topic: Changes in this Release