AHF 25.4 is a stability-focused release that delivers a range of enhancements to improve overall reliability and performance.

These improvements contribute to a leaner, more efficient AHF environment—reducing resource usage while reinforcing platform robustness.

AHF now automatically detects increasing memory usage by processes and provides a clear summary of the issue, its root cause, and recommended resolution within the Insights interface.

Since version 24.4, AHF has been capable of identifying problems and presenting actionable summaries. These are accessible on the Problem Summary page, available under the Detected Problems panel in Insights.

Automatic Solutions for Database Problems with AHF 24.4

Refer to the user guide for detailed steps on resolving issues identified by AHF.

Resolve Problems AHF has Detected

AHF 25.4 introduces support for partial Oracle Trace File Analyzer log collections when initiated through OneView, enabling successful uploads even if some nodes fail to complete the collection.

Background:

Previously, if any node in the cluster failed during Oracle Trace File Analyzer log collection, OneView reported the overall status as FAILED. This caused partially collected diagnostics to be discarded, and no data was attached to the associated Service Request (SR).

Starting with AHF 25.4:

• Oracle Trace File Analyzer returns a SUCCESS status if log collection completes on some nodes, even if others fail.
• OneView and DBaaS tooling treat this status as valid and proceed to upload the available logs to the SR.
• This ensures that valuable diagnostic data is preserved and accessible for analysis, even in the event of partial failures.
• Oracle Trace File Analyzer also identifies missing data, allowing it to be collected separately if needed.

This enhancement addresses common real-world issues, such as:

• Oracle Trace File Analyzer service being down or unhealthy on specific nodes.
• Temporary socket connectivity issues between nodes.

Impact and Benefits:

• Improves diagnostic turnaround time.
• Enhances the customer experience by reducing the need for re-collection.
• Increases the success rate of log collections initiated through OneView.

Additionally, OneView will now notify users of partial collections, allowing support engineers to request missing logs manually if needed.

AHF 25.4 introduces support for triggering SRDC (Service Request Diagnostic Collection) on remote nodes, allowing diagnostics to be collected from the node where the issue actually occurred — even when the request originates from a different node.

Background:

Previously, SRDC collections could only be initiated on the node receiving the request, regardless of where the incident was observed. This limitation often resulted in unnecessary cluster-wide collections or missed opportunities to gather the most relevant diagnostic data.

With this enhancement:

• When an SRDC collection is triggered for an incident that occurred on a different node, AHF delegates the action to the appropriate remote node.
• This enables precise, targeted diagnostics by collecting data only from the affected node.
• Cluster-wide collections are no longer required for isolated issues.

Benefits:

• Enables OneView to send incident-specific SRDC requests to any node in the cluster.
• Enhances precision in SRDC collections within clustered environments.
• Reduces diagnostic overhead by avoiding unnecessary data collection from unaffected nodes.
• Aligns with real-world SR investigation practices, where problems often impact only a single node.

To initiate a diagnostic collection, run tfactl diagcollect and follow the prompts to select the relevant issue.

For more details, refer to Using On-Demand Diagnostic Collections.

Release 25.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 elevated priority for Global Cache Fusion processes

Oracle Orachk Specific Best Practice Checks

• Verify private interface name

Oracle Exachk Specific Best Practice Checks

• Verify voting disk integrity