DB2 Version 10.1 for Linux, UNIX, and Windows

States of connections and activities in a service class

Service classes collect connection statistics for each service class. You can see which connections and activities are in a service class, and the state of either the connection or activity.

States of a connection

Following are the possible states of a connection in a service class:

CONNECTED: The connection successfully connected to the database but is not yet associated with its workload and service superclass.
DECOUPLED: The connection does not have a coordinator agent assigned (concentrator case).
DISCONNECTPEND: The connection is disconnecting from the database.
FORCED: The connection has been forced.
INTERRUPTED: The connection has been interrupted.
MAPPED: The connection is mapped to a workload and has joined a service superclass. The connection can now submit activities for execution.
QUEUED: The connection coordinator agent is queued by a DB2® connection or activity threshold that offers queuing, such as the CONCURRENTDBCOORDACTIVITIES threshold. In a multimember database environment, this state might indicate that the coordinator agent has made an RPC to another member to obtain threshold tickets and has not yet received a response.
TRANSIENT: The connection is attempting to join a service class that has reached its connections threshold. The connection is queued to join the service class. When the service class is not violating its connections threshold, the connection will join the service class. A connection in the transient state cannot submit activities for execution.
TERMINATING: The connection received a connect reset from the client or is being terminated because of a force or an error condition.
UOWEXEC: The connection is processing a request.
UOWWAIT: The connection is waiting for a request from the client.

States of an activity

Following are the possible states of an activity in a service class:

CANCEL_PENDING: If you cancel an activity that has no agent actively working on a request for the activity, the activity is placed in the CANCEL_PENDING state and is cancelled on the next request that is received.
EXECUTING: The activity is executing.
IDLE: There is no agent actively processing a request for the activity.
INITIALIZING: The activity was created and is being prepared for execution.
QUEUED: The activity cannot be executed because of a concurrency threshold at the database or service class level. The activity is queued until it is permitted to execute.
TERMINATING: The activity is being terminated.
UNKNOWN: The state of the activity is unknown.