Configuring the Oracle Database agent
The Oracle Database agent provides monitoring capabilities for the availability, performance, and resource usage of the Oracle database. You can configure more than one Oracle Database instance to monitor different Oracle databases. The remote monitoring capability is also provided by this agent.
Before you begin
Before you configure the Oracle Database agent, you must grant privileges to the Oracle user account that is used by the Oracle Database agent. For more information about privileges, see Granting privileges to users for RDBMS instances.
About this task
- Availability of instances in the monitored Oracle database.
- Resource information such as memory, caches, segments, resource limitation, tablespace, undo (rollback), system metric, and system statistics.
- Activity information, such as OS statistics, sessions, contention, and alert log.
The Oracle Database agent is a multiple instance agent; you must create the first instance and start the agent manually.
The Managed System Name includes the instance name that you specify, for example,pc:connection_name-instance_name-host_name:RDB, where pc is your two character product code. The Managed System Name is limited to 32 characters. The instance name that you specify is limited to 28 characters, minus the length of your host name. For example, if you specify Oracle as your instance name, dbconn as your connection name, your managed system name is RZ:dbconn-oracle-hostname:RDB.
If you specify a long instance name, the Managed System name is truncated and the agent code does not display correctly.
The length of the connection_name, instance_name, and hostname_name variable is truncated when it exceeds 28 characters.
To avoid a subnode name that is truncated, change the subnode naming convention by setting the following environment variables: KRZ_SUBNODE_INCLUDING_AGENTNAME, KRZ_SUBNODE_INCLUDING_HOSTNAME, and KRZ_MAX_SUBNODE_ID_LENGTH.
- Default subnode name: DBConnection-Instance-Hostname
- Subnode name with environment variable set to NO: DBConnection-Hostname
- Default subnode name: DBConnection-Instance-Hostname
- Subnode name with environment variable set to NO: DBConnection-Instance