Oracle Autonomous Health Framework (AHF) 23.1 Release Notes Summary
- New “Undetermined” check status: Orachk and Exachk now mark checks as Undetermined when they cannot run reliably—for example, because of permission or resource-discovery issues—instead of incorrectly reporting them as failures. This status is weighted like a skipped check in Health Score calculations.
- Configuration comparison across systems: Orachk and Exachk can compare two compliance collections, such as primary versus standby or production versus test. The diff report highlights different, unique, and common configuration values.
- JSON output for AHFCTL: Several AHFCTL commands now support
-json, enabling easier integration with scripts and other tools for status, update history, and switch information. - SQL Agent connection pooling: AHF’s SQL Agent keeps reusable database connections open instead of launching a new SQL*Plus process for every query. This reduces CPU, memory use, and database audit connection logs.
- New best-practice checks: Common checks cover Enterprise Manager status and important long-term-release fixes. Orachk checks password-file sharing; Exachk checks CPU oversubscription, VM CPU configuration, cloud filesystem use, and
dbcs-agent/dbcs-adminstatus.