AHF Release 24.1

Option to Collect Oracle Auto Service Request (ASR) Client Logs

Starting with AHF 24.1, Oracle Trace File Analyzer collects Oracle Auto Service Request (ASR) client's logs present under /var/opt/asrmanager/log/. Collecting these logs enables to you triage ASR related failures in Oracle Database Appliance (ODA).

Collect ASR log files using the new -asr or the existing -oda component, for example:

tfactl diagcollect -asr

or

tfactl diagcollect -oda

Related Topics

AHF Print Collections Improvements

A new option -id has been added to the tfactl print collections -json command to display collection details for a specific collection ID.

tfactl print collections -id <collection ID> -json
tfactl print collections -id 20240104010433stbm000004-vm18 -json
[
    {
        “CollectionId”: “20240104010433stbm000004-vm18",
        “InitiatedNode”: “stbm000004-vm18",
        “CollectionType”: “Manual Collection”,
        “RequestUser”: “root”,
        “NodeList”: “[stbm000004-vm17, stbm000004-vm18]“,
        “StartTime”: “2024-01-04T00:04:30.000-0600",
        “EndTime”: “2024-01-04T01:04:30.000-0600",
        “ComponentList”: “[omsi, emagent, acfs, asmproxy, sosreport, crsclient,
emagenti, oms, qos, dbwlm, ocm, cha, cfgtools, afd, avs, dbclient, rdbms, cvu,
os, crs, syslens, hami, em, chmos, goldengate, asmio, dataguard, install,
compliance, tns, asm, rhp, emplugins, wls]“,
        “UploadStatus”: “FAILED”,
        “CollectionStatus”: “COMPLETED”,
        “NodeCollection”: [
            {
                “Host”: “stbm000004-vm18”,
                “Tag”:
“/u01/app/giusr/oracle.ahf/data/repository/collection_Thu_Jan_04_01_04_37_CST_2024_node_all/“,
                “ZipFileName”:
“/u01/app/giusr/oracle.ahf/data/repository/collection_Thu_Jan_04_01_04_37_CST_2024_node_all/stbm000004-vm18.tfa_Thu_Jan_04_01_04_36_CST_2024.zip”,
                “ZipFileSize”: “38896",
                “CollectionTime”: “183",
                “CheckSum”:
“d882835fe5bcee4b8d5381b59572f2b75dc7499ddf3adf5771e3ea75fa39e975",
                “checksum_algo”: “sha256"
            },
            {
                “Host”: “stbm000004-vm17",
                “Tag”:
“/u01/app/giusr/oracle.ahf/data/repository/collection_Thu_Jan_04_01_04_37_CST_2024_node_all/“,
                “ZipFileName”:
“/u01/app/giusr/oracle.ahf/data/repository/collection_Thu_Jan_04_01_04_37_CST_2024_node_all/stbm000004-vm17.tfa_Thu_Jan_04_01_04_36_CST_2024.zip”,
                “ZipFileSize”: “42759",
                “CollectionTime”: “186",
                “CheckSum”:
“b090611f11e94814782b12f798e60ef0e054fbad47e94d950a3a24c698a79986",
                “checksum_algo”: “sha256"
            }
        ]
    }
]

Related Topics

Oracle Orachk/Oracle Exachk Diff Report Enhancements

In the Configurations Comparison section, certain parameters that are expected to have different values are now reported under the Common Configs table.

Related Topics

Terminal Release for AIX and Solaris Platforms

Several old operating systems are approaching their end of life, as a result AHF is announcing terminal releases.

AHF 23.8.1 will be the terminal release for:

  • AIX 7.1
  • Solaris 11.3

This terminal release will continue to be supported on these platforms, but future AHF releases will not support these operating system versions.

For more information, see Unsupported platforms.

Related Topics

Compliance Checks for Oracle RAC Extended Clusters

AHF adds support for running compliance checks against Oracle RAC Extended Clusters.

An Oracle RAC Extended Cluster consists of nodes that are located in multiple locations called sites.

When you deploy an Oracle Standalone Cluster, you can also choose to configure the cluster as an Oracle RAC Extended Cluster. You can extend an Oracle RAC cluster across two, or more, geographically separate sites, each equipped with its own storage. In the event that one of the sites fails, the other site acts as an active standby.

AHF can now run compliance checks to verify the configuration of RAC Extended Clusters. These checks can be run with the command:

ahfctl compliance -includeprofile extended

For more information, see About Oracle Extended Clusters.

Insights Helps Explain Why Events Occurred

AHF Insights now provides the ability to drill into Major Events, showing the CPU and I/O stats, providing context for why the event occurred.

The AHF Insights Operating System Analysis -> Report -> Summary Timeline shows when problems occurred and correlates them with the timing of lifecycle events such as Database start or stop.

The Summary Timeline has now been enhanced to include useful context data such as CPU and I/O OS metrics under the Major Events section.

With this addition AHF Insights shows not only what happened and where, but also why.

Insights Timeline Makes Problem Analysis and Resolution Easier

AHF Insights timeline chart and table now dynamically adjust time ranges and allow to copy results as plain text.

The AHF Insights Timeline chart can be zoomed to focus on just the events of interest. The below event table now filters dynamically based on the chart zoom. A new copy button capturing everything from the filtered event table as plain text – making problem event analysis and documentation super easy.

Insights into Disk Space Problems

AHF Insights shows the number of disk space problems detected and color-codes disks based on their usage.

The AHF Insights Home dashboard now highlights on the Space Analysis panel, the number of disk space problems detected. Drilling down onto the Space Analysis Report includes a new color-coded view of all the usage of all disks.

This makes detecting and and understanding disk space usage problems fast and easy.

Latest Python and Java Third-Parties

AHF has upgraded the versions of Python and Java third-party software to fix Common Vulnerabilities and Exposures (CVEs).

AHF 24.1 has upgraded the versions of many third party libraries in both Python and Java. The following CVEs are all fixed:

For more information, see .Third-Party License Information

Deprecated Oracle Trace File Analyzer Masking Feature

Deprecated tfactl set redact=mask|sanitize in release 24.1

New Oracle Orachk and Oracle Exachk Best Practice Checks

Release 24.1 includes the following new Oracle Orachk and Oracle Exachk best practice checks.

Oracle Orachk Specific Best Practice Checks

  • Verify loopback interface MTU size

Oracle Exachk Specific Best Practice Checks

  • Exadata Critical Issue EX83
  • Exadata Critical Issue EX84

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