2. Changes in Previous Releases
  3. AHF Release 23.4

AHF Release 23.4

Parent topic: Changes in Previous Releases

Insights into Oracle Database Appliance (ODA) and Generic Oracle RAC Systems

AHF Insights now runs on ODA and generic Oracle RAC systems in addition to its previous support for Exadata.

AHF Insights provides a bird's-eye view of an entire system. The rich interface showcases:

  • Environment topology
  • Configuration
  • Database and System Kernel parameters
  • Compliance management and drift tracking including recommended RU's
  • Timeline of sequence of events
  • Visual highlighting of anomalies in system metrics
  • Root causes for issues and fixes for some anomalous cases

Operating System information on systems prior to 19.3 is not supported.

AHF Insights reports can be generated using the command: ahf analysis create --type insights.

To get started with AHF Insights see Introduction to AHF Insights.

Parent topic: AHF Release 23.4

Tracking and Reporting of System Level Changes

The tfactl changes command has been enhanced to now report system level changes in the following areas:

  • Oracle Database parameters set to non-default values
  • Oracle Home installations
  • Oracle Home patch installation
  • Operating system parameters that are relevant to Oracle Grid Infrastructure and Oracle Database installations
  • Operating system patches

Command output displays both current and previous values. Change results can also be generated in JSON format by adding the -json option. Changes are reported on a per-node basis by default but can be controlled using the -node option. Output it limited to a maximum of 30-day period.

For more information, see tfactl changes.

Parent topic: AHF Release 23.4

Support JSON Payload as Options for tfactl Commands

Cloud Operations need to be able to easily request Oracle Trace File Analyzer collections from the OneView interface and be able to support new AHF collection features without having to request changes to cloud agent code.

By supporting the use of JSON to provide a list of arguments for all tfactl commands that json can be constructed by the requestor and simply be passed through the cloud agent to AHF.

New Collection options can be supported immediately by the initial request without the need to request Cloud agent clode changes.

This feature simply extracts the json provided and expands it to call in to the current tfactl command line interface.

Parent topic: AHF Release 23.4

New Options for Understanding the Status of Diagnostic Collections

New tfactl print collections -status options hav been added to understand the status of AHF diagnostic collections if they are successful, failed, or still running.

The tfactl print collections command has been enhanced to provide three new options:
  • tfactl print collections -status FAILED: Prints failed collections.
  • tfactl print collections -status QUEUED: Prints collections that are queued and yet to start.
  • tfactl print collections -status COMPLETED: Prints completed collections.

For more information, see tfactl print.

Parent topic: AHF Release 23.4

Oracle Orachk Support to Send Email Attachments as JSON

Starting in release 23.4, Oracle Orachk supports sending email attachments in JSON format instead of HTML when specified.

Use the -attachment_type option or set the RAT_ATTACHMENT_TYPE environment variable to send email attachments in JSON format. This feature is intended to use with the following two Oracle Orachk email notification methods:

  • together with the -sendemail option
  • through the NOTIFICATION_EMAIL and AUTORUN_FLAGS configuration in the autoruns
  • What's included in the attached JSON files?
    • The attachments for manual runs include the orachk_summary.json and orachk_valid_results.json files.
    • For scheduled runs, the diff JSON file is also attached together with files mentioned above.
  • How to specify the attachment type for a manual run?
    • Using the -attachment_type option:
      orachk -sendemail user@domain.com -attachment_type json
    • Or, setting the RAT environment variable instead:
      export RAT_ATTACHMENT_TYPE=json
  • How to specify the attachment type as JSON for scheduled runs?
    You must
    • configure NOTIFICATION_EMAIL value for the corresponding autorun entry, for example:
      orachk -set 'NOTIFICATION_EMAIL=user@domain.com' -id autostart_client
    • configure AUTORUN_FLAGS value for the corresponding autorun entry, for example:
      orachk -set 'AUTORUN_FLAGS=<previous autorun flags> -attachment_type json' -id autostart_client

Parent topic: AHF Release 23.4

Unified AHF Command-Line Interface Enhancements

Review the list of enhancements made to AHF CLI in release 23.4.

  • ahf software get-latest-mrp-level: Get the latest MRP level to see if the metadata needs to be updated. 
    ahf software get-latest-mrp-level
19.18
    Database: Database MRP 19.18.0.0.230418
    GI      : GI MRP 19.18.0.0.230418
19.17
    Database: Database MRP 19.17.0.0.230418
    GI      : GI MRP 19.17.0.0.230418

    For more information, see ahf software.

  • --clusters clu1 clu2 clu3: Specify a space-delimited list of clusters to include in the AHF Balance fleet scope of the analysis.
    ahf analysis create --type impact --scope fleet --name fleet1 --clusters clu1 clu2 clu3

    For more information, see ahf analysis

  • --refresh: Create analysis report with the most recent data from AHF Insights sources.
    ahf analysis create --type insights --refresh

    For more information, see ahf analysis

Parent topic: AHF Release 23.4

New Oracle Orachk and Oracle Exachk Best Practice Checks

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

Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk

  • AHF Balance check for CPU contention between databases
  • AHF CPU oversubscription check

Oracle Orachk Specific Best Practice Checks

  • Validate database listener service configuration with clusterware

Oracle Exachk Specific Best Practice Checks

  • Validate KMS configuration for database encryption
  • Compare instance name between CRS and cloud registration file

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

Related Topics

Parent topic: AHF Release 23.4