AHF Release 24.9

Parent topic: 2024 AHF Releases

Database Performance Tuning Made Easier

A new Performance Reports section has been added to AHF Insights, featuring PerfHub, AWR, and AWR Compare reports, simplifying database performance tuning.

AHF now captures diagnostic data needed for performance tuning via the dbperf SRDC, using the command:
tfactl diagcollect -srdc dbperf -database db_name
The most useful performance tuning reports are now embedded directly within the AHF Insights report. The Performance Reports section includes:
  • PerfHub Reports
  • AWR Reports
  • AWR Compare Reports
To use the new Performance Reports section:
  1. Run: tfactl diagcollect -srdc dbperf -database db_name
  2. Extract the diagnostic collection and open the Insights report.
  3. Navigate to the Performance Reports section and open the relevant report.
For more details on using these performance reports, see:

Parent topic: AHF Release 24.9

Detect New Causes of Node Eviction and Database Slow Performance

AHF now automatically identifies new causes of node eviction, instance eviction, and database slow performance, providing a detailed summary of the problem, cause, and recommended resolution within the Insights report.

Since version 24.4, AHF has had the capability to detect issues and present a summary along with resolutions (Node Eviction Detection and Resolution). The Problem Summary page is accessible under the Detected Problems panel in Insights.

This release introduces the ability to automatically detect the following additional issues:
  • Node evictions due to High CPU Steal
  • Database slow performance due to poorly sized network message buffers
  • Database slow performance due to incorrect configuration of recovery blocks
To generate a diagnostic collection:
  1. Run tfactl diagcollect and follow the prompts to select the relevant issue.
  2. Transfer the resulting zip file to a machine with a browser.
  3. Open the Insights report and review the Detected Problems section for a detailed analysis.

This streamlined detection process simplifies troubleshooting and helps resolve performance issues faster.

For more information, see:

Parent topic: AHF Release 24.9

Easier to Ensure Oracle Data Guard Readiness

AHF Insights now simplifies ensuring Oracle Data Guard readiness by calculating failover and switchover readiness, comparing configurations between primary and standby databases, and highlighting key performance metrics in the Data Guard section.

Managing Oracle Data Guard can be complex, particularly when calculating switchover/failover readiness and ensuring configuration symmetry between primary and standby databases. AHF 24.5 introduced the Data Guard Health Report Included in AHF Insights, and this functionality has now been redesigned and enhanced, accessible via the Data Guard panel.

New Configuration Page Features:
  • Displays Data Guard configuration, including switchover and failover readiness calculations.
  • Lists databases with their roles and status.
  • Shows transport lag, apply lag, and average apply rate.

These metrics help identify potential issues with redo transport and log apply services and determine if the standby database is keeping pace with the primary.

Clicking the Details button opens the Database Symmetry page, which allows you to:
  • Compare configurations between the primary and standby databases.
  • View Database Wait Events and corresponding wait times, aiding in pinpointing performance bottlenecks.

Note:

Database Wait Events and Log Switches are specific to the system where the Insights report is generated. For a full picture, generate Insights reports on both the primary and standby systems.
To create an Insights report with Data Guard, run:
ahf analysis create --type insights

For more information, see Explore Diagnostic Insights.

Parent topic: AHF Release 24.9

Database Monitoring Via Database User Credentials

AHF now supports database monitoring using a configured username and password, eliminating the need for SYSDBA privileges.

Previously, AHF monitored and alerted on database anomalies by connecting as SYSDBA through operating system authentication. However, this approach was not feasible when operating system authentication was disabled.

With Oracle Database versions 19.0.0.0.0 and above, AHF can now monitor databases using a configured username and password. This enhancement removes the dependency on operating system authentication and helps reduce the generation of audit records.

If you’ve already set up a user and password for AHF, it will use these credentials automatically. To configure AHF to use a specific username and password, run the following command:
ahfctl setpassword

For more information about creating a database user for AHF to connect to the database, see Database Monitoring Using Database User Credentials.

For more information on configuring database monitoring, refer to Managing and Configuring Oracle Trace File Analyzer.

For more information about setting password, refer to ahfctl setpassword.

Parent topic: AHF Release 24.9

Best Practice Reporting for Latest Security Risks

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

As of AHF 24.9, the integrated DBSAT version has been upgraded to 3.1. For more information on DBSAT version 3.1, see Announcing Database Security Assessment Tool (DBSAT) 3.1.

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: AHF Release 24.9

New Oracle Orachk and Oracle Exachk Best Practice Checks

Release 24.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 the SYS and SYSTEM accounts are using the DEFAULT profile
  • Verify the DEFAULT profile parameters
  • Verify EXECUTE privileges exist in the PUBLIC role

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

Related Topics

Parent topic: AHF Release 24.9