Running Compliance Checks in Silent Mode

Use Automated Daemon Mode to schedule and run compliance checks automatically. Silent mode remains available primarily for backward compatibility.

Note:

Silent mode is maintained for customers who used it before daemon mode became available. Silent mode runs a limited set of checks and is not actively enhanced. For automated compliance checking, use Automated Daemon Mode where possible.

The checks performed in silent mode depend on the option you specify:

• -s runs silent-mode compliance checks but does not run checks on storage servers and switches.
• -S excludes database server checks that require root access. It also does not run checks on storage servers and switches.

Configure passwordless SSH equivalency when silent-mode checks need to run across remote systems. Passwordless SSH is not required when remote checks are unnecessary, such as when checking a single-instance database locally.

The output generated in silent mode is similar to the output from an on-demand compliance check.

Note:

On an Oracle Engineered System, if the environment is not configured appropriately for silent-mode operation, storage server and InfiniBand switch checks are not performed.

Including Checks that Require Root Access

Run the compliance check as root, or configure the required sudo access, to include checks that require root privileges.

Use the -s option followed by any other required options.

For Oracle Orachk:

orachk -s

For Oracle Exachk:

exachk -s

Excluding Checks that Require Root Access

Use the -S option to run compliance checks without checks that require root access.

For Oracle Orachk:

orachk -S

For Oracle Exachk:

exachk -S