Differences between regular and UE table output

Generally speaking, the event monitors that can write to both regular and unformatted event (UE) tables capture the same data. However, there are some minor differences to be aware of.

Order of columns

The first difference pertains to the order of the columns of the tables. When the event monitor generates regular tables, compared to the output produced by running EVMON_FORMAT_UE_TO_TABLES against a UE table, columns are generally presented in alphabetical order, with two exceptions:

If a PARTITION_KEY column is included in the output, it is the first column.
For tables that report metrics, related columns are grouped together. For example, columns that report time spent in the system are grouped together.

Columns returned

The other pertains to data types of columns. In most cases, the columns in write-to-table event monitors are the same as the columns produced by running EVMON_FORMAT_UE_TO_TABLES against a UE table. There are some differences however. These differences are summarized in Table 1.

Table 1. Summary of differences in returned columns
Logical data group	Columns returned in regular tables	Columns returned from EVMON_FORMAT_UE_TO_TABLES
All groups	PARTITION_KEY column included
uow	TYPE column included	TYPE column excluded
uow_package_list	ROUTINE_ID data type is BIGINT	ROUTINE_ID data type is INTEGER
pkgcache	XMLID column excluded	XMLID column included
lock	DL_CONNS data type is BIGINT	DL_CONNS data type is INTEGER
	ROLLED_BACK_PARTICIPANT_NO data type is SMALLINT	ROLLED_BACK_PARTICIPANT_NO data type is INTEGER
	XMLID column excluded	XMLID column included
lock_participants	AGENT_STATUS data type is BIGINT	AGENT_STATUS data type is INTEGER
	APPL_ID data type is VARCHAR(64)	APPL_ID data type is VARCHAR(128)
	APPL_NAME data type is VARCHAR(255)	APPL_NAME data type is VARCHAR(128)
	CLIENT_ACCTING data type is VARCHAR(200)	CLIENT_ACCTNG data type is VARCHAR(255)
	TABLESPACE_NAME data type is VARCHAR(18)	TABLESPACE_NAME data type is VARCHAR(128)
	XMLID column excluded	XMLID column included
	INTERNAL_DATA column included	Data contained in INTERNAL_DATA is not included.
lock_participant_activities	ACTIVITY_ID data type is BIGINT	ACTIVITY_ID data type is INTEGER
	Includes EVENT_ID, EVENT_TYPE and EVENT_TIMESTAMP rather than XMLID¹	XMLID column included
	CONSISTENCY_TOKEN is CHAR(8)	CONSISTENCY_TOKEN is VARCHAR(8)
lock_activity_values	ACTIVITY_ID data type is BIGINT	ACTIVITY_ID data type is INTEGER
	PARTICIPANT_NO data type is SMALLINT	PARTICIPANT_NO data type is INTEGER
	Includes EVENT_ID, EVENT_TYPE and EVENT_TIMESTAMP instead of XMLID.¹	XMLID column included
The XMLID column represents a compound monitor element made up of the concatenation of the event_header, event_id, event_type, event_timestamp and partition monitor elements.