Oracle^® MiniCluster S7-2 Administration Guide

Run orachk Health Checks (CLI)

Use this procedure to run health checks on database VMs. ORAchk does not run on APP VMs.

Before you can run ORAchk, you must download it and install it in the database VMs.

For more information about ORAchk, refer to ORAchk Overview.

1. Log in to a database VM and assume the root role.

   See Log in to a DB VM.

2. Change to the directory where orachk is installed.
3. Run orachk.

   root@mc1dbzg1-mc1zg1zone1:~# ./orachk     
            CRS stack is running and CRS_HOME is not set. Do you want to set 
   CRS_HOME to /u01/app/12.1.0.2/grid?[y/n][y]y     
   Checking for prompts on mc1dbzg1-mc1zg1zone1 for oracle user...     
   Checking ssh user equivalency settings on all nodes in cluster     
   Node mc1dbzg1-mc1zg1zone2 is not configured for ssh user equivalency and the script uses
        ssh to execute checks on remote nodes.     
   Without this facility the script cannot run audit checks on the remote nodes.     
   If necessary due to security policies the script can be run individually on each node.     
   Do you want to configure SSH for user root on mc1dbzg1-mc1zg1zone2  [y/n][y]y
   Enter root password on mc1dbzg1-mc1zg1zone2 :-     
   Verifying root password.     
    . .     
   Checking for prompts for oracle user on all nodes...     
       
   Searching for running databases . . . . .     
            . .          
   List of running databases registered in OCR          1.rac12c1          2. None of above
   Select databases from list for checking best practices. For multiple     databases,
   select 1 for All or comma separated number like 1,2 etc     [1-2][1].1
   
   . . .   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
   --------------------------------------------------------------------------------------------
   mc1dbzg1-mc1zg1zone1 Yes         Yes           Yes     Yes       Yes        rac12c11     
   --------------------------------------------------------------------------------------------
   . . . . . . root passwords are incorrect or login to as root is     disabled in ssh
   configuration for following nodes.     
   You can still continue but root privileged checks will not be executed on following nodes.
            1. mc1dbzg1-mc1zg1zone2     
            Do you want to continue[y/n][y]:- y
            *** Checking Best Practice Recommendations (PASS/WARNING/FAIL) ***     
   Collections and audit checks log file is     
       /root/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741/log/orachk.log     
       
       
   Checking for prompts in /root/.profile     on mc1dbzg1-mc1zg1zone1 for
       root user...     
       =============================================================
             Node name - mc1dbzg1-mc1zg1zone1     
       ============================================================= 
   Collecting - ASM Disk Groups          
   Collecting - ASM Disk I/O stats
   Collecting - ASM Diskgroup Attributes          
   Collecting - ASM disk partnership imbalance          
   Collecting - ASM diskgroup attributes     
   Collecting - ASM diskgroup usable free space          .
   .
   <output omitted>
   .
            Detailed report (html) -
       /root/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741.html
       UPLOAD(if required) -     /root/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741.zip