A system-wide unique ID for the application. On a single-partitioned database, this identifier consists of a 16-bit counter. On a multi-partitioned database, this identifier consists of the coordinating partition number concatenated with a 16-bit counter. In addition, this identifier is the same on every partition where the application may make a secondary connection.
Table 2. Snapshot Monitoring InformationSnapshot Level |
Logical Data Grouping |
Monitor Switch |
Application |
appl_id_info |
Basic |
Lock |
appl_lock_list |
Basic |
DCS Application |
dcs_appl_info |
Basic |
Transaction |
event_xact |
- |
Table 3. Event Monitoring InformationEvent Type |
Logical Data Grouping |
Monitor Switch |
Locking |
- |
- |
Unit of work |
- |
- |
Connections |
event_connheader |
- |
Statements |
event_stmt |
- |
Statements |
event_subsection |
- |
Deadlocks1 |
event_dlconn |
- |
Deadlocks with Details1 |
event_detailed_dlconn |
- |
Threshold violations |
event_thresholdviolations |
- |
Activities |
event_activity |
- |
- 1
- This option has been deprecated. Its
use is no longer recommended and might be removed in a future release.
Use the CREATE EVENT MONITOR FOR LOCKING statement to monitor lock-related
events, such as lock timeouts, lock waits, and deadlocks.
Usage
This monitor element is an alias of
the agent_id monitor element.
When returned by MON_GET_MEMORY_POOL, this
monitor element is NULL except when the memory pool being described
is one of the following:
- APPLICATION
- STATISTICS
- STATEMENT
- SORT_PRIVATE.