SYS_DML_RESOURCES

Information on “costly” DML statements (in SQL). A DML statement is regarded as costly when the number of logical IOs it triggers and/or its activity time in the DBH is very high compared to other DML statements.

The NUMBER_OF_LOGICAL_IO and ACTIVE_TIME columns in particular contain information relevant to the costs of a statement.

Column name	Data type	Contents
CATALOG_NAME	CHAR (18)	Database name
START_TIME	TIMESTAMP (3)	Start time of the DML statement
END_TIME	TIMESTAMP (3)	End time of the DML statement
HOST_NAME	CHAR (8)	Host name from the identification of the requesting user
APPLICATION_NAME	CHAR (8)	Application name from the identification of the requesting user
CUSTOMER_NAME	CHAR (8)	Name of the requesting user from the identification of the requesting user
CONVERSATION_ID	CHAR (8)	Identification of the requesting user with respect to UTM and SESAM-DBAccess
TAC_NAME	CHAR (8)	Job name of the user ID or name of the program unit which executed the DML statement
MODULE_NAME	CHAR (8)	Name of the compilation unit in which the waiting DML statement was executed
STATEMENT_NAME	VARCHAR (18)	Internal name of the DML statement
STATEMENT_TYPE	VARCHAR (31)	<type of statement> (e.g. INSERT)
NUMBER_OF_LOGICAL_IO	INTEGER	Number of logical read and write accesses
NUMBER_OF_PHYSICAL_IO	INTEGER	Number of physical read and write accesses
ELAPSED_TIME	INTEGER	Time which has actually elapsed (milliseconds)
ACTIVE_TIME	INTEGER	Activity time in the DBH (milliseconds)
ACTIVE_TIME_DBH	INTEGER	Activity time in DBH tasks (milliseconds)
ACTIVE_TIME_SVT	INTEGER	Activity time in service tasks (milliseconds)
MEASURE_OF_COSTS	INTEGER	Internal measure of the costs of the application

Table 114: SYS_DML_RESOURCES view of the SYS_INFO_SCHEMA