Oracle Autonomous Health Framework (AHF) 26.5 Release Notes Summary

  • Stricter SSH host-key validation for Exachk: Exachk validates SSH host keys more strictly when it connects to Exadata storage cells and switches. If a target is absent from known_hosts or its saved key is stale, Exachk rejects the connection and skips data collection from that target. Administrators should refresh stale entries, ensure consistent known_hosts files across database nodes, and avoid unsupported legacy DSA (ssh-dss) keys.
  • Automatic TFA self-diagnostics after collection failures: If tfactl diagcollect fails, TFA automatically runs tfactl diagnosetfa. This proactively gathers information needed to investigate the failure, reducing manual troubleshooting effort and helping support teams identify the root cause faster.
  • Cluster-wide diagnostic flood control: TFA now limits redundant diagnostic collections across cluster nodes during event storms or recurring alerts. This reduces collection overhead, avoids creating unnecessary diagnostic bundles, conserves repository storage, and makes collected data easier to review.
  • New Orachk and Exachk best-practice checks: The release adds Exadata checks that verify whether cryptographic policy is enabled—at both general and storage-server levels—and introduces checks for Exadata critical issues DB56 and DB57. These checks help surface security and platform-health risks earlier.