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

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

Only the Most Critical Checks Shown by Default
By default, Oracle ORAchk and Oracle EXAchk display only the most critical checks in the report output.
REST Interface
Oracle ORAchk and Oracle EXAchk now include full REST support allowing invocation and query over HTTPS.
Remote Node Connection without Passwordless SSH
If you do not wish to use passwordless SSH to connect to remote nodes, Oracle ORAchk and Oracle EXAchk can auto-generate the private key files for the remote nodes.
Python 3 Compatibility
Oracle ORAchk and Oracle EXAchk now support Python 3.6.
Support for Oracle Autonomous Database
Oracle EXAchk now provides support for Oracle Autonomous Database.
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.
Command-Line Options to Generate Password Protected Collection zip Files
This release includes Oracle ORAchk and Oracle EXAchk command-line options to encrypt and decrypt diagnostic collection zip files.

Only the Most Critical Checks Shown by Default

By default, Oracle ORAchk and Oracle EXAchk display only the most critical checks in the report output.

The critical checks are those which Oracle judges to have the most severe potential impact.

All other checks are still run and available in the report. You can view them by selecting appropriate option under the control Show checks with the following status.

To run only the critical checks, use appropriate profile:

./orachk -profile oratier1
./exachk -profile exatier1

Parent topic: Changes in this Release for Oracle ORAchk and EXAchk User’s Guide 18.2.0

REST Interface

Oracle ORAchk and Oracle EXAchk now include full REST support allowing invocation and query over HTTPS.

To facilitate REST support, Oracle REST Data Services (ORDS) is included within the install.

To enable REST, start ORDS by running the ./exachk -ordssetup command, and then start the daemon using the -ords option.

./exachk -d start -ords

Start a full health check run by accessing the URL:

https://host:7080/ords/tfaml/orachk/start_client

To run specific profiles:

https://host:7080/ords/tfaml/orachk/profile/profile1,profile2

To run specific checks:

https://host:7080/ords/tfaml/orachk/check/check_id,check_id

Any request returns a job ID that you can use to query the status or to download the result.

To query the status:

https://host:7080/ords/tfaml/orachk/status/job_id

To download the result:

https://host:7080/ords/tfaml/orachk/download/job_id

Remote Node Connection without Passwordless SSH

If you do not wish to use passwordless SSH to connect to remote nodes, Oracle ORAchk and Oracle EXAchk can auto-generate the private key files for the remote nodes.

The process used to generate the private key is as follows:

Prompt for remote node password.
Log in to the remote node, and generate private and public key pair on the remote node.
Copy the contents of public key into the .ssh/authorized_keys file of remote node and then delete the public key from the remote node.
Copy the private key of remote node into the local node, and use as identity file to make future connections.

Alternatively, you can provide the private key file yourself.

Parent topic: Changes in this Release for Oracle ORAchk and EXAchk User’s Guide 18.2.0