Changes in this Release
This preface lists changes in the Oracle Autonomous Health Framework Checks and Diagnostics User's Guide 26.3.
- Diagnostic File Metadata Indexing No longer Enabled by Default
Prior to AHF 26.3, diagnostic file metadata was indexed using Lucene. This improved the performance of certain AHF DBA tools, but incurred CPU and memory overhead even in environments where those tools were not used. - Migration from Windows Management Instrumentation Command-line (WMIC) to Common Information Model (CIM)
Starting in AHF 26.3, Oracle Trace File Analyzer (TFA) uses PowerShell and the Common Information Model (CIM) instead of Windows Management Instrumentation Command-line (WMIC) for system queries and remote command execution on Microsoft Windows platforms. - Self-Signed Certificate Validity Initially Set to 365 Days
Starting in AHF 26.3, Oracle Trace File Analyzer (TFA) generates self-signed certificates with a validity period of 365 days to align with current security best practices. - System Overview Section Added to ISC Report
AHF 26.3 introduces a new System Overview section within the Infrastructure Software and Configuration (ISC) section of theexachkreport. - Oracle Exachk Dynamic Load-Aware Scheduler
AHF 26.3 introduces the Dynamic Load-Aware Scheduler for Exachk, which uses machine learning and telemetry analysis to identify optimal low-load windows for daily runs. - Store Switch Configuration Using AHF CLI
AHF 26.3 introduces CLI-based management for switch configurations. Administrators can set, get, check, or unset switch configurations for individual switches, specific nodes, or all switches. Configurations are securely stored in the AHF wallet, enabling centralized, secure, and flexible switch management. - New Oracle Orachk and Oracle Exachk Best Practice Checks
Release 26.3 includes the following new Oracle Orachk and Oracle Exachk best practice checks.
Diagnostic File Metadata Indexing No longer Enabled by Default
Prior to AHF 26.3, diagnostic file metadata was indexed using Lucene. This improved the performance of certain AHF DBA tools, but incurred CPU and memory overhead even in environments where those tools were not used.
Starting with AHF 26.3, Lucene-based file metadata indexing is disabled by default in Autonomous Health Framework (AHF) installations. This change helps reduce overall resource consumption, particularly CPU and memory usage, in the default configuration.
The default configuration now sets indexInventory=false, disabling Lucene metadata indexing for new installations. Lucene indexing can still be enabled through runtime controls when faster metadata lookups are required.
This change reduces default resource consumption and keeps TFA lightweight while preserving the option to enable Lucene indexing when needed.
Related Topics
Parent topic: Changes in this Release
Migration from Windows Management Instrumentation Command-line (WMIC) to Common Information Model (CIM)
Starting in AHF 26.3, Oracle Trace File Analyzer (TFA) uses PowerShell and the Common Information Model (CIM) instead of Windows Management Instrumentation Command-line (WMIC) for system queries and remote command execution on Microsoft Windows platforms.
Recent Microsoft Windows versions disable or remove Windows Management Instrumentation Command-line (WMIC), which prevented Oracle Trace File Analyzer (TFA) from performing certain system queries and remote command operations.
AHF/TFA on Microsoft Windows now uses PowerShell and the Common Information Model (CIM) for process queries, disk queries, and remote command execution. WMIC remains available as a fallback for older environments.
This change ensures TFA compatibility with modern Windows platforms, including Windows Server 2022 and later, enabling diagnostics collection without requiring WMIC.
Parent topic: Changes in this Release
Self-Signed Certificate Validity Initially Set to 365 Days
Starting in AHF 26.3, Oracle Trace File Analyzer (TFA) generates self-signed certificates with a validity period of 365 days to align with current security best practices.
Certificate rotation and regeneration workflows have been updated to support periodic renewal and synchronization across nodes.
This change improves TFA certificate management with security best practices while maintaining existing certificate functionality.
Over upcoming releases the validity will be reduced to further strengthen security.
Parent topic: Changes in this Release
System Overview Section Added to ISC Report
AHF 26.3 introduces a new System Overview section within the Infrastructure Software and Configuration (ISC) section of the exachk report.
This enhancement automatically identifies and surfaces key Exadata deployment characteristics that were previously unavailable in both the HTML and JSON outputs of exachk. It provides DBAs and support engineers with a unified view of the environment, eliminating the need for manual verification.
For more information, see System Overview Section Added to ISC Report.
Parent topic: Changes in this Release
Oracle Exachk Dynamic Load-Aware Scheduler
AHF 26.3 introduces the Dynamic Load-Aware Scheduler for Exachk, which uses machine learning and telemetry analysis to identify optimal low-load windows for daily runs.
It replaces static scheduling with intelligent, data-driven recommendations, minimizing system impact while ensuring consistent health checks.
For more information, see:
Parent topic: Changes in this Release
Store Switch Configuration Using AHF CLI
AHF 26.3 introduces CLI-based management for switch configurations. Administrators can set, get, check, or unset switch configurations for individual switches, specific nodes, or all switches. Configurations are securely stored in the AHF wallet, enabling centralized, secure, and flexible switch management.
For more information, see ahf configuration.
Parent topic: Changes in this Release
New Oracle Orachk and Oracle Exachk Best Practice Checks
Release 26.3 includes the following new Oracle Orachk and Oracle Exachk best practice checks.
Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk
- Verify RMAN Backup Destination Uses Compliant Storage or NFS Mount Options
All checks can be explored in more detail via the Health Check Catalogs.
Parent topic: Changes in this Release