Changes in this Release for Oracle ORAchk and EXAchk User’s Guide 18.4.0

This preface lists changes in Oracle® ORAchk and EXAchk User’s Guide 18.4.0.

Automatically Run on Oracle Exadata User Domain (DomU)

Installing Oracle Trace File Analyzer on Oracle Exadata automatically sets up and runs the Oracle EXAchk daemon on the user domain (DomU).

The daemon restarts at 1 am every day to discover any environment changes. The daemon runs a full local Oracle EXAchk check at 2 am every day, and a partial run of the most impactful checks every 6 hours through the exatier1 profile.

The daemon automatically purges any collections older than 2 weeks.

If you install Oracle EXAchk in stand-alone mode, then run exachk -autostart to enable auto start for quick setup on Oracle Exadata user domain.

You can change the daemon settings after enabling auto start. To remove auto start any time, run exachk -autostop or tfactl run exachk -autostop.

Support for Oracle Exadata 19.1.0

This release adds Oracle EXAchk support for the latest Oracle Exadata release 19.1.0.

Ensure That You Run Only the Up-To-Date Checks

Starting in this release, Oracle ORAchk and Oracle EXAchk will provide only the checks that are less than a year old.

Health Check information is constantly changing over time. What is applicable today, may not be applicable several months later. This is the reason Oracle ORAchk and Oracle EXAchk have always had a quarterly release cycle.

The older Health checks are the more risk of them containing out of date information. So from this release onwards Oracle ORAchk and Oracle EXAchk will provide only the checks that are less than a year old.

If Oracle ORAchk or Oracle EXAchk is more than six months old, then the tool (as per previous releases) presents a warning message advising you to upgrade and offers you the ability to download a new version. If Oracle ORAchk or Oracle EXAchk is more than a year old, then the tool will not run any checks.

Performance Improvement through Caching Discovery Data

Starting in this release, Oracle ORAchk and Oracle EXAchk cache the discovery data.

Internal testing on Oracle Exadata systems has shown caching of discovery data improved runtime performance by cutting the execution time of critical checks in half.

The following command options are included in this release:

  • -discovery: Cache discovery data.
  • -checkdiscovery: Optionally verify discovery.
  • -usediscovery: Use discovery data.
  • -refreshdiscovery: Refresh discovery data.
  • -rmdiscovery: Remove discovery data.

Related Topics

Ability to Patch Between Releases

Starting in this release, Oracle ORAchk and Oracle EXAchk has the ability to patch between the releases. The patching allows for updates to both health checks and code.

When the patches are ready to deploy, they will be made available through the regular patching mechanisms on https://support.oracle.com and https://updates.oracle.com.

The following command options are included in this release:

  • -applypatch exachk_{bug_num}.zip | orachk_{bug_num}.zip: Apply a new patch.
  • -querypatch all: Find all patches installed.
  • -querypatch {bug_num}: Find if a specific patch is installed.
  • -rollbackpatch {bug_num}: Rollback a specific patch.

Check Specific Timeouts to Reduce Skipped Checks

Health Checks are skipped sometimes because the check takes longer to run than the default timeout value.

This release adds check specific timeout values.

When checks are written by Oracle a check specific timeout value is applied. This timeout value is based on our understanding of how long we expect that check to take to run.

If you find certain checks are still timing out, then you can override the individual check timeout value using: export RAT_TIMEOUT={value_in_seconds}

New Oracle Stack Health Checks

This release includes new health checks for both Oracle ORAchk and Oracle EXAchk including a number of Oracle Exadata critical issues.

The Health Check Catalog is also contained within the download.