3.19 HealthCheck

Use this Knowledge Script to monitor the following parameters:

  • Cluster Instance Down: notify when an Oracle instance in a cluster fails or becomes inactive.

    Run this Knowledge Script for Oracle RAC monitoring only. This Knowledge Script uses the srvctl command functionality to fetch the statuses of all the cluster instances.

  • Database Connect: the connectivity and login capability of Oracle databases on UNIX and Linux systems. This script attempts to connect to the database you select. If the connection attempt is successful, this script reports the status of the database and of its login capability. If the connection attempt is unsuccessful, an event is raised.

  • Database Down: the status of a database. This script checks whether the Oracle RDBMS background processes are running and whether a local connection can be made.

    Each Oracle instance has a default set of background processes that must be running. An event is raised if any of the processes that you specified for monitoring in the Background processes to monitor parameter are down, or if a connection cannot be made to the database instance.

The account you use to run this script must have SELECT permissions for the following tables:

  • V_$INSTANCE
  • V_$VERSION
  • GV_$INSTANCE (for Oracle RAC monitoring only)

3.19.1 Resource Objects

Oracle Database folders. When you drop a script on an Oracle Database folder, a job executes on that database and monitors only that database.

3.19.2 Default Schedule

The default interval for this script is Every 10 minutes.

3.19.3 Setting Parameter Values

Set the following parameters as needed:

Description

How to Set It

Oracle Username

Enter the username that this script needs to access the target databases. If you run this script on more than one database, configure each database with the same username. To use SYSDBA authentication, leave this parameter blank. The default is blank.

Health Check

Cluster Instance Down

Select Yes to monitor Cluster Instance Down. The default is unselected.

Database Connect

Select Yes to monitor Database Connect. The default is unselected.

Database Down

Select Yes to monitor Database Down. The default is unselected.

Data Collection

Collect data for instance status?

Select Yes to collect data for charts and reports. If you enable data collection, the script returns the status of each instance:

  • 100--instance is running

  • 0--instance is down

The default is unselected.

Collect data for connection and login status?

Select Yes to collect data for charts and reports. If you enable data collection, the script returns the status of the database and of its login capability. The default is unselected.

Collect data for process and connection status?

Select Yes to collect data for charts and reports. When you enable data collection, the script returns the following values:

  • 100--all specified processes are running and a connection attempt was successful

  • 80--one or more processes was down but a connection attempt was successful

  • 0--no processes were running and/or a connection attempt failed

This parameter provides a way to report on the percentage of system uptime in any given period.

The default is unselected.

Event Notification

Raise event if instance is down or if unable to check status?

Select Yes to raise an event when the instance is down. The default is Yes.

Severity

Set the event severity level, from 1 to 40, to indicate the importance of the event detecting that an instance is down. The default is 10 (red event indicator).

Raise event if unable to connect?

Select Yes to raise an event if an attempt to connect to the Oracle database is unsuccessful. The default is Yes.

Severity

Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 5 (red event indicator).

Raise event with database and login status?

Select Yes to raise an event providing information on the database and login status. The default is unselected.

Severity

Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 35 (magenta event indicator).

Raise event if a process is down or unable to connect?

Select Yes to raise an event if an Oracle database or background process is detected down. The default is Yes.

Severity

Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 15 (yellow event indicator).

Event severity for internal failure

Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 5 (red event indicator).

Monitoring

Background processes to monitor (comma-separated, no spaces)

Enter the names of Oracle RDBMS background processes you want to monitor, separated by commas and no spaces. The default is: LGWR,PMON,SMON,RECO,DBWO,DBWR.

Create blackout file for a database if it appears to be down?

Select Yes if the script should create a file in the blackout directory so that no further jobs are run on this database. The SetMonitoringOptions script must be run to set the blackout directory before this file can be created. The default is unselected.