omnihealthcheck
checks the status of Application Recovery Manager services and the consistency of the Application Recovery Manager internal database (IDB). It can only be run on the Cell Manager.
omnihealthcheck
SYNOPSIS
omnihealthcheck
DESCRIPTION
The omnihealthcheck command reads the specified configuration file where each line of the file is treated as a separate command and is executed. Note that the commands must be listed with full pathnames except if they are Application Recovery Manager commands located in AppRM_home\bin on the Windows Cell Manager or /opt/omni/bin or /opt/omni/sbin directories on the UNIX Cell Manager. Note also that the configuration file must be in the UNICODE format on the Windows Cell Manager. If the configuration file is not specified, the default file is used: AppRM_home\Config\server\HealthCheckConfig on the Windows Cell Manager or /etc/opt/omni/server/HealthCheckConfig on the UNIX Cell Manager.
If the default file is used, omnihealthcheck checks if Application Recovery Manager services (RDS, CRS, MMD, omnitrig, and omniinet) are active.
Exit codes of individual commands are inspected at the end.
There are 3 different exit codes for the omnihealthcheck command:
0: All listed commands and their exit codes have been executed.
1: At least one of the commands in the configuration file could not be executed or has completed with an exit code other than 0.
2: The configuration file could not be read.
The final health check exit code is 0 (OK) only if all executed commands from the configuration file completed successfully (exit codes of all executed individual commands from the configuration file are 0).
Output of the omnihealthcheck command is saved in
AppRM_home\Log\server\HealthCheck.log on the Windows Cell Manager
Command line interface reference | 125 |
