Configuring Oracle Database monitoring

The Monitoring Agent for Oracle Database provides monitoring capabilities for the availability, performance, and resource usage of the Oracle database. You can configure more than one Oracle Database agent instance to monitor different Oracle databases. Remote monitoring capability is also provided by this agent.

Before you begin

About this task

The directions here are for the most current release of the agent, except as indicated. For information about how to check the version of an agent in your environment, see Agent version.

For general Oracle database performance monitoring, the Oracle Database agent provides monitoring for the availability, performance, resource usage, and activities of the Oracle database, for example:

The Oracle Database agent is a multiple-instance agent. You must create the first instance and start the agent manually. Additionally, each agent instance can monitor multiple databases.

The Managed System Name for the Oracle Database agent includes a database connection name that you specify, an agent instance name that you specify, and the hostname of the computer where the agent is installed. For example, <pc>:connection_name-instance_name-host_name:<SUB>, where <pc> is your two character product code and <SUB> is the database type (Possible values are RDB, ASM, or DG). The Managed System Name is limited to 32 characters. The instance name that you specify is limited to 23 characters, minus the length of your hostname and database connection. For example, if you specify dbconn as your database connection name, Oracle02 as your agent instance name, and your hostname is Prod204a, your managed system name is RZ:dbconn-oracle02-Prod204a:RDB. This example uses 22 of the 23 characters available for the database connection name, agent instance name, and hostname.


  1. To configure the agent on Windows® systems, you can use the IBM Performance Management window or the silent response file.

  2. To configure the agent on Linux® and UNIX® systems, you can run the script and respond to prompts, or use the silent response file.

For advanced configuration only, the Oracle database administrator must enable the Oracle user to run the krzgrant.sql script to access the database, see Running the krzgrant.sql script. Log in to the IBM Cloud Pak console to view monitoring data.

If you are unable to view the data in the agent dashboards, first check the server connection logs and then the data provider logs. The default paths to these logs are as follows: