3.9 CallsPerTransaction

Use this Knowledge Script to monitor the demand placed on a database instance by each transaction. This demand is determined by tracking the number of database calls (for example, to parse, execute, and fetch data) per committed transaction. When the number of database requests per transaction exceeds the threshold, the job raises an event.

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

V_$SYSSTAT
V_$VERSION

3.9.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.9.2 Default Schedule

The default interval for this script is Every 10 minutes.

3.9.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.

Collect data for calls per transaction?

Select Yes to collect data for charts and reports. When you enable data collection, the Knowledge Script returns the number of database calls per transaction. The default is unselected.

Raise event if threshold is exceeded?

Select Yes to raise an event if the number of calls per transaction exceeds the threshold. The default is Yes.

Threshold - Maximum number of calls per transaction

Enter a threshold for the maximum number of database calls per transaction allowed before the job raises an event. The default is 100.

Severity

Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 5 (red 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).