The SQLTEMPSPACE threshold specifies the maximum amount
of system temporary table space that can be consumed by a DML activity
at any member. DML activities often use temporary table
space for operations such as sorting and the manipulation of intermediate
result sets.
- Type
- Activity
- Definition domain
- Database, service superclass, service
subclass, work action, workload and statement
- Enforcement scope
- Member
- Tracked work
- See the information later in this topic
- Queuing
- No
- Unit
- Amount of temporary table space expressed in kilobytes (KB), megabytes
(MB), or gigabytes (GB)
- Predictive or reactive
- Reactive
Activities tracked by this threshold are as follows:
- DML activities that are issued at the coordinator member.
- Nested DML activities that are derived from user applications.
Consequently, DML activities that are issued by DB2® logic (such as utilities, SYSPROC procedures,
or internal SQL) are unaffected by this threshold.
The data server considers IMPORT, EXPORT, and other CLP
commands to be user logic. Activities that are invoked from within
IMPORT, EXPORT, and other CLP commands are subject to thresholds.