Changes in this Release

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

AHF Insights Data Guard Reports

The Data Guard section in the Insights report has received a major upgrade based on valuable customer feedback.

  • Database State and Properties are now visible within the section, alongside enhancements in the new Data Guard Details page.
  • The newly introduced Log Switch Interval table enables quick identification of snapshots with an unusually high number of log switches, helping pinpoint potential issues faster.
  • Monitor your network more effectively with the new Transport Network Utilization chart.
  • Additionally, several bugs have been fixed to improve overall stability and performance.

Related Topics

Parent topic: Changes in this Release

AHF Diagnostic Collection Enhancements

Enhancements to AHF Diagnostic Collection improve data gathering, support large files, and offer better filtering for faster, more accurate diagnostics.

Improved Support for Large Files (>1 GB): AHF now better supports collecting large files exceeding 1 GB. Previously, AHF only collected a small portion from the end of very large files. Now, it gathers periodic size data to intelligently determine how much of the file to trim during collection, ensuring more relevant data is captured.

Inclusion of Orachk/Exachk JSON Reports: AHF collections have been enhanced to include Exachk JSON outputs alongside the traditional HTML reports, offering richer diagnostics and improved visibility into critical issues.

New Health Reporting for Collection Pre-Checks: As part of OneView-initiated Health Pre-Checks, AHF now supports a “partial success” state. This means that for AHF to be considered “Healthy” and able to perform collections, it no longer needs to pass on all nodes — success on at least one node or specified nodes is sufficient to initiate a collection request.

Kernel and Messages Log Inventory Support: AHF now comprehensively inventories and collects kernel and messages log files, including rotated and time-stamped variants. This enhancement ensures more accurate diagnostics across Linux environments.

Time and Node Filters for Listing Completed Collections: The tfactl print collections command now supports advanced filtering options to help users efficiently narrow down collection results by time range and node. Additional filters will be introduced in future releases.

Addition of ‘oranfstab’ to DNFS Diagnostics: The DNFS SRDC now collects the oranfstab file from both $ORACLE_HOME/dbs and /etc locations, ensuring full coverage regardless of file placement.

Support for PDB-Level Data Gathering for ORA-1555 Collection: When an ORA-1555 error occurs within a specific PDB, AHF can now collect data targeted to that PDB instead of collecting data only at the CDB level, providing more precise diagnostics.

New Filter Options:

  • -from <timestamp> and -to <timestamp>

    Retrieve collections within a specific time range. Supports UTC (Z) and timezone-aware (±HH:MM) formats.

    Examples:

    • tfactl print collections -from 2025-05-20T06:14:25Z -to 2025-05-20T07:15:25Z
    • tfactl print collections -from 2025-05-20T02:14:25-04:00 -to 2025-05-20T03:15:25-04:00
  • -for <timestamp | date>

    List collections for a specific date or exact timestamp.

    Examples:

    • tfactl print collections -for 2025-05-20
    • tfactl print collections -for 2025-05-20T06:14:25Z
    • tfactl print collections -for 2025-05-20T02:14:25-04:00
  • -node <node>

    Filter collections for a specific node.

    Example: tfactl print collections -for 2025-05-20 -node node2

Parent topic: Changes in this Release

Private Memory Difference in CHM Analysis Section of Oracle Orachk Report

The Private Memory diff feature highlights the change in derived private memory usage between two selected time ranges in the CHM Analysis section of the Oracle Orachk report.

When analyzing memory consumption across processes over specific timestamps, the inclusion of the Private Memory (pmem) metric—alongside RSS and Virtual Memory (vsize)—offers a more accurate and comprehensive view of actual memory utilization.

How pmem is derived:

Private memory for each process is calculated by subtracting the shared memory (shmem) from RSS. The aggregate private memory usage is then computed and presented, showing both:
  • The overall difference at the aggregated level, and
  • The difference at the individual process level.

This feature has been integrated into the inline diff report under the AvailableMemoryLow signature, providing users with deeper insights into memory usage trends.

Figure -1 Private Memory Difference in CHM Analysis Section of Oracle Orachk Report


This image illustrates Private Memory Difference in CHM Analysis Section of Oracle Orachk Report.

Figure -2 Private Memory Difference in CHM Analysis Section of Oracle Orachk Report


This image illustrates Private Memory Difference in CHM Analysis Section of Oracle Orachk Report.

Related Topics

Parent topic: Changes in this Release

AHF-IPC: Python IPC Library for Client-to-Daemon Communication

In previous implementations, client applications had to spawn subprocesses and manage low-level details of the Oracle Trace File Analyzer (TFA) daemon’s wire protocol to establish communication.

This release introduces a Python-based Inter-Process Communication (IPC) library, allowing clients to interact directly with the TFA daemon via a clean, well-defined API.

  • Eliminates subprocess management, reducing complexity in client applications.
  • Abstracts the wire protocol, improving code maintainability and reducing the risk of protocol mismatches.
  • Enables faster development through a streamlined interface tailored for Python clients.

This enhancement simplifies integration with the TFA daemon and improves the overall robustness of client-side tooling.

Parent topic: Changes in this Release

New Oracle Orachk and Oracle Exachk Best Practice Checks

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

Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk
  • Verify Parameter DB_BLOCK_CHECKSUM [Standby]
  • Verify Parameter DB_LOST_WRITE_PROTECT [Standby]
Oracle Orachk Specific Best Practice Checks
  • Verify fix for 35454504

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

Related Topics

Parent topic: Changes in this Release