This is the number
of rows deleted from the database as a result of
internal activity.
Table 1. Snapshot
Monitoring Information| Snapshot Level |
Logical Data Grouping |
Monitor
Switch |
|---|
| Database |
dbase |
Basic |
| Application |
appl |
Basic |
| Application |
stmt |
Basic |
| Dynamic SQL |
dynsql |
Statement |
For snapshot
monitoring, this counter can be reset.
Table 2. Event Monitoring Information| Event Type |
Logical
Data Grouping |
Monitor Switch |
|---|
| Database |
event_db |
- |
| Connection |
event_conn |
- |
| Statements |
event_stmt |
- |
- Usage
- This element can help you gain insight into internal
activity within
the database
manager of
which you might
not be aware. If this activity is high, you may want to evaluate
your table
design to determine if the referential constraints or triggers that
you have
defined on your database are necessary.
Internal delete activity
can
be a result of:
- A cascading delete enforcing an ON CASCADE
DELETE referential constraint
- A trigger being fired.
DB2 Version 9.7 for Linux, UNIX, and Windows