Changes in this Release

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

Automating Excluded Compliance Checks

AHF 25.8 introduces a new mechanism to automate the management of excluded compliance checks.

Previously, to skip certain checks in compliance reports, the excluded_check_ids.txt file had to be manually created on each node.

With this release, the process is automated, and updates are automatically propagated to all nodes.

  • No need to manually create or distribute excluded_check_ids.txt across nodes.
  • Excluded check IDs can now be added, listed, replaced, or removed using the ahf configuration commands.
  • Changes are automatically propagated to all nodes.

Use case scenarios:

  • When excluded_check_ids.txt exists with valid checks

    To print the excluded check IDs:

    ahf configuration get --property ahf.compliance.excluded-check-ids

    Example output:

    Excluded checks:  
ahf.compliance.excluded-check-ids: ['CHECKID1', 'CHECKID2', 'CHECKID3']
  • When excluded_check_ids.txt does not exist

    To exclude a check ID:

    ahf configuration set --property ahf.compliance.excluded-check-ids --value CHECKID2

    Example output:

    Successfully updated.

    This creates or updates the excluded_check_ids.txt file.

  • Overwriting the list of excluded checks

    If the file already exists with valid checks, you can replace the list:

    ahf configuration set --property ahf.compliance.excluded-check-ids --value CHECKID3 --replace

    Example output:

    Excluded checks:  
Successfully updated.

    This replaces the existing list with the new check ID(s).

  • Unsetting excluded checks

    To remove specific excluded checks:

    ahf configuration unset --type compliance --excluded-check-ids LIST_OF_EXCLUDED_CHECKS

    To unset all excluded checks:

    ahf configuration reset --property ahf.compliance.excluded-check-ids

Related Topics

Parent topic: Changes in this Release

Improved Handling of Remote Node Repository Closure

In AHF 25.8, collections are not terminated when a remote node’s repository is closed or reaches capacity. Instead, the affected node is skipped, allowing the collection to continue on other available nodes and complete successfully.

Collecting data for all nodes
 
TFA is using system timezone for collection, All times shown in UTC.
Scanning files from 2025-09-07 04:21:19 UTC to 2025-09-07 05:21:19 UTC
 
Collection Id : 20250907052122node
 
Waiting up to 120 seconds for collection to start
 
Detailed Logging at : /u01/app/oracle/oracle.ahf/data/repository/collection_Sun_Sep_07_05_21_26_UTC_2025_node_all/diagcollect_20250907052122_node.log
2025/09/07 05:21:33 UTC : WARNING : Skipping diagnostics collection on [node] due to closed AHF repository
2025/09/07 05:21:33 UTC : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
...

Parent topic: Changes in this Release

Inclusion of RMAN Logs for Oracle Database Appliance (ODA)

In AHF 25.8, collections for Oracle Database Appliance (ODA) include Oracle Recovery Manager (RMAN) logs, enhancing diagnostic coverage.

Parent topic: Changes in this Release

Extended Diagnostic Capabilities in Multitenant Environments

In AHF 25.8, Oracle Trace File Analyzer (TFA) adds support for collecting diagnostics from Pluggable Databases (PDBs) with DBTEXTINSTALL SRDC, enhancing diagnostic coverage in multitenant environments.

Parent topic: Changes in this Release

Allow Users with Platinum Role to Check if Fleet Insights is Configured

In AHF 25.8, Fleet Insights is available to all customers, allowing Platinum customers to set it up directly.

Users granted the Platinum role can verify in advance whether Fleet Insights is configured, even if the setup was performed by a different user. This capability enables a more seamless Platinum Support process.

After upgrading to AHF 25.8, any user with the Platinum role can confirm the configuration with:

ahf configuration check --type fleet-insights

Parent topic: Changes in this Release

Oracle Health Check Collections Manager Decoupled from AHF Installer Delivery

Oracle Health Check Collections Manager is an APEX application used to view and analyze compliance reports from multiple systems. The application is optional and is not configured or upgraded directly by the AHF installer.

Starting with AHF 25.8, Oracle Health Check Collections Manager is no longer included in the AHF installer. To reduce installer size and footprint, it is provided as a separate download from the main AHF download MOS Note.

Related Topics

Parent topic: Changes in this Release

New Oracle Orachk and Oracle Exachk Best Practice Checks

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

Oracle Orachk Specific Best Practice Checks
  • Verify Parameter DB_BLOCK_CHECKING [Standby]

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

Related Topics

Parent topic: Changes in this Release