InactivityInterval
The InactivityInterval parameter specifies how long (in seconds) the High-speed Apply Engine should wait before reporting the status of agents if no units of recovery have been committed.
Attributes
This parameter has the following attributes:
Attribute | Value |
|---|---|
Section | [MonitorTuning] |
Abbreviation | None |
DBMS | Db2, Db2 UDB, Oracle |
Required? | No |
Valid values | An integer from 1 to 32767 that represents a number of seconds |
Default value | 300 |
Usage
Each time the internal processes are scanned (see ScanInterval), the High-speed Apply Engine checks the overall number of commits. If the number of seconds specified by the InactivityInterval parameter has elapsed since the commit count last increased, the status of the agents is displayed. The refreshed display repeats at that interval until the commit count increases. A value of zero disables the checking.
The following figure shows an example of the InactivityInterval parameter:
AGENT STATEMENT ID STATUS AS OF
----- ---------------------- ---------- -----------------
1 0 INACTIVE
2 50 FINISHED 18:31:03.016465
3 31 IN DBMS 18:31:04.824623
The terms in this example are defined as follows:
- AGENT is the agent identifier.
- STATEMENT ID is the current or last statement processed by the agent.
- STATUS can have the following statuses:
- INACTIVE means that the agent is starting up or there is no activity for that agent.
- IN DBMS means that the agent has called the DBMS for processing SQL.
- PROCESSING means that High-speed Apply Engine is executing code.
- WAITING means that the agent is ready for more work.
- FINISHED means that the agent is terminating or has terminated.
- AS OF refers to the last change in status.
Repeated displays indicate a possible long running SQL statement (IN DBMS) or program error (WAITING or PROCESSING).
Related topic