Changes in this Release

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

Best Practice Reporting for Latest Security Risks

AHF now integrates DBSAT version 4.0.0 recommendations into the best practice guidance provided in both Oracle Orachk and Oracle Exachk reports, offering enhanced security insights and compliance recommendations.

As of AHF 25.9, the integrated DBSAT version has been upgraded to 4.0.0. For more information on DBSAT version 4.0,0. see https://blogs.oracle.com/database/post/dbsat40.

To generate an AHF best practice report including security recommendations run:
ahfctl compliance -profile security
To generate an AHF best practice report including security recommendations as well as complete health of the system run:
ahfctl compliance -includeprofile security

For more information, see Integration of Oracle DBSAT into Oracle Autonomous Health Framework.

Parent topic: Changes in this Release

Easier Access to the Latest Compliance Reports

The new ahf data get-latest-reports command simplifies how users retrieve compliance reports across nodes.

With this enhancement, administrators and compliance officers can quickly access the latest full and Tier 1 compliance reports without manual intervention.

Key capabilities:

  • Effortless retrieval: Run ahf data get-latest-reports --type compliance to automatically collect the most recent full and Tier 1 compliance reports.
  • Cross-node convenience: Reports from remote nodes are automatically copied to the local node, ensuring all relevant files are centrally accessible.
  • Streamlined output: The output folder contains only the HTML summary reports. For detailed files (logs, metadata, raw data), users can connect to the respective remote nodes.

Example Usage:

ahf data get-latest-reports --type compliance

This enhancement saves time, reduces manual effort, and streamlines compliance workflows by making the latest reports immediately available on the local node, while still allowing deeper investigation on remote nodes when needed.

Related Topics

Parent topic: Changes in this Release

Enhanced Management Server (MS) Alert Collection for Exadata DomU Systems

The default Oracle Trace File Analyzer (TFA) diagnostic collection process for Exadata systems has been enhanced.

Going forward, whenever you run a default diagcollect, TFA will automatically include the alert_history_detail.txt file. This ensures that all relevant alerts from the Management Server (MS) and the Database Command Line Interface (dbmcli) generated during the previous seven days (up to the collection end date) are captured.

This enhancement delivers more comprehensive and consistent diagnostic data, helping to accelerate issue analysis and improve supportability for Exadata DomU environments.

Parent topic: Changes in this Release

Configuration-Driven Scan File Entities Identification

The selection of Scan File Entities is now controlled through the external file_monitor_config.json configuration file, replacing the previously hardcoded file mappings.

This update makes the process more flexible, maintainable, and easier to extend.

Parent topic: Changes in this Release

Enhanced Oracle Trace File Analyzer (TFA) Collection Metrics Improve OneView Performance Monitoring

TFA now provides detailed collection statistics, including log collection time and upload time.

These metrics are added to the monitoring JSON file and will be used by OneView to improve visibility into potential performance bottlenecks and identify components contributing to delays.

Parent topic: Changes in this Release

Oracle Trace File Analyzer (TFA) to Collect Response Files

Oracle Trace File Analyzer (TFA) now collects response (.rsp) files regardless of the time range specified for the diagnostic collection.

TFA will gather files from the following directories:

  • $GI_HOME/install/response
  • $DB_HOME/install/response

If the collection period does not include the file creation dates but response files exist in these directories, TFA ensures that at least the most recent file is collected.

Parent topic: Changes in this Release

Database Running Locally Pre-Check for OneView Requests

Oracle Trace File Analyzer (TFA) now includes a Database Running Locally pre-check for OneView requests.

This validation ensures that the specified database is running on the node where the collection request is executed. By confirming local database availability, the pre-check helps SRDCs run correctly and reliably.

Parent topic: Changes in this Release

Efficient ZIP Copying for Insights

Oracle Trace File Analyzer (TFA) now avoids copying the entire collection ZIP to the initiating node when generating an insights ZIP if the -nocopy option is used or if the collection is a OneView request.

This enhancement reduces unnecessary data transfer from remote nodes to the initiating node, improving efficiency.

Example:

tfactl diagcollect -last 1h -nocopy

Parent topic: Changes in this Release

New Oracle Orachk and Oracle Exachk Best Practice Checks

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

Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk

Verify kernel-space and user-space core dumps configuration

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

Related Topics

Parent topic: Changes in this Release