AHF 23.9 includes a new command option reset to change the behavior of Oracle Orachk or Oracle Exachk daemon during autostart, autostop, and upgrade.

AHF Managelogs feature adds ability to manage audit dump logs.

The AHF Managelogs feature purges logs from default locations like the Grid Infrastructure and all Database Automatic Diagnostic Repository (ADR) destinations.

To do this purging Managelogs uses the Database Automatic Diagnostic Repository (ADR), however ADR does not manage audit dump files. As a result, audit dump files can grow and consume too much space.

The Managelogs feature has been expanded to optionally also include management of audit dump files for Grid Infrastructure and Database.

Configure automatic log purging

• Configure auto purge:

  tfactl set manageLogsAutoPurge=ON

• Include audit dumps:

  tfactl set managelogs.adump=ON

• Set the frequency of purging (defaults to 60 mins)

  tfactl set manageLogsAutoPurgeInterval=<n>

• Configure how old logs must be for them to be purged (default 30 days):

  tfactl set manageLogsAutoPurgePolicyAge=<d|h>

Purge logs on-demand

• Enable audit dumps:

  tfactl set managelogs.adump=ON

• Check the usage for audit dump destination

  tfactl managelogs -show usage

• Check variation for audit dump destination

  tfactl managelogs -show variation

• Purge audit dump files along with other destinations managed by managelogs:

  tfactl managelogs -purge

A new option -autoupdate has been added to ahfctl setupgrade and ahfctl unsetupgrade.

• To store autoupdate configurations, run, for example,

  ahfctl setupgrade -autoupgrade on -swstage /opt/oracle.ahf -frequency 1 -autoupdate on

• To turn on autoupdate configurations, run:

  ahfctl setupgrade -autoupdate on

• To turn off autoupdate configurations, run:

  ahfctl setupgrade -autoupdate off

• To unset autoupdate configurations, run:

  ahfctl unsetupgrade -autoupdate

AHF TFA collections, which include Insights reports are now created faster.

AHF Insights reports can be generated stand-alone using the command ahf analysis create --type insights. Alternatively, a TFA diagnostic collection can be created with an AHF Insights report included by adding the -insights option to the existing -diagcollect command.

This creation of the AHF Insights report often requires analysis of existing zipped diagnostics. Unzipping and processing the collections is CPU intensive and can be slow.

This process of analyzing the diagnostic collection to generate the AHF Insights report has been streamlined and performance improved. Timings will vary based on the type of collection being performed and the systems involved.

An example baseline from testing shows the following improvement, on the time taken to generate the included AHF Insights report:

• 23.8: tfactl diagcollect -asm -crs- os -tns -insights -last 1h >> 6.8 seconds
• 23.9: tfactl diagcollect -asm -crs- os -tns -insights -last 1h >> 1 second

Cluster Verification Utility (CVU) diagnostic files are included in AHF diagnostic collections.

As CVU (Cluster Verification Utility) diagnostic files contain periodic Grid Infrastructure configuration information and critical diagnostic reports they are often required for diagnosis of Grid Infrastructure problems.

AHF now collects all files under the following CVU directories:

• <GI_BASE>/crsdata/<node>/cvu/diagnostics/cvu_diag_report.txt
• <GI_BASE>/crsdata/@global/cvu/baseline/cvures/cvusnapshot*.zip

To include the CVU diagnostic files add the -cvu component to the diagcollect command.

tfactl diagcollect -cvu -last 1h -noclassify

By default, AHF will include CVU in CRS or Database collections for example, both these automatically include CVU diagnostics:

• tfactl diagcollect -crs -last 1h -noclassify

• tfactl diagcollect -database orcl -last 1h -noclassify

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