1.4 Running Health Checks in Silent Mode

You can run health checks automatically by scheduling them with the Automated Daemon Mode operation.

Note:

Silent mode operation is maintained for backwards compatibility for the customers who were using it before the daemon mode was available. Silent mode is limited in the checks it runs and Oracle does not actively enhance it any further.

• Running health checks in silent mode using the -s option does not run any checks on the storage servers and switches.

• Running health checks in silent mode using the -S option excludes checks on database server that require root access, also does not run any checks on the storage servers and database servers.

To run health checks silently, configure passwordless SSH equivalency. It is not required to run remote checks, such as running against a single-instance database.

When health checks are run silently, output is similar to that described in On-Demand Mode Operation.

$ ./orachk -s


        Checking ssh user equivalency settings on all nodes in cluster

        Node dbserver1 is configured for ssh user equivalency for root user
         
        Node dbserver3 is configured for ssh user equivalency for root user
         

        Searching for running databases . . . . .

        . . . . . . 
        List of running databases registered in OCR
        1. ordsdb
        2. rdb11204
        3. All of above
        4. None of above


        Searching out ORACLE_HOME for selected databases.

        . . . . . . . . . . 

        . 
        Checking Status of Oracle Software Stack - Clusterware, ASM, RDBMS

        . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .
        -------------------------------------------------------------------------------------------------------
                                                Oracle Stack Status                            
        -------------------------------------------------------------------------------------------------------
        Host Name  CRS Installed  RDBMS Installed  CRS UP    ASM UP    RDBMS UP  DB Instance Name
        -------------------------------------------------------------------------------------------------------
        dbserver2  Yes             Yes             Yes        Yes      Yes      rdb112042 
        dbserver1  Yes             Yes             Yes        Yes      Yes      rdb112041 
        dbserver3  Yes             Yes             Yes        Yes      Yes      ordsdb_1 rdb112043 
        -------------------------------------------------------------------------------------------------------
        . . . . . . 


        *** Checking Best Practice Recommendations (PASS/WARNING/FAIL) ***
        . . . . . . 

Note:

The tool does not perform storage server or InfiniBand switch checks if it is configured to run in silent mode operation on an Oracle engineered system.

• Including Health Checks that Require root Access
  Run as root  or configure sudo  access to run health checks in silent mode and include checks that require root access.
• Excluding Health Checks that Require root Access
  To run health checks in silent mode and exclude checks that require root access, use –S followed by other required options.

1.4.1 Including Health Checks that Require root Access

Run as root  or configure sudo  access to run health checks in silent mode and include checks that require root access.

To run health checks including checks that require root access, use the –s option followed by other required options:

$ ./orachk –s

$ ./exachk –s

1.4.2 Excluding Health Checks that Require root Access

To run health checks in silent mode and exclude checks that require root access, use –S followed by other required options.

$ ./orachk –S

$ ./exachk –S