Statistics class 4 trace records
The statistics class 4 trace includes error situations that involve indoubt threads during the distributed two-phase commit process.
The trace records available for diagnosis of indoubt thread error conditions are IFCIDs 0203 - 0210 and 0234 - 0236. For a complete description of these and the other statistics class 4 IFCIDs (0191 - 0195 and 0238), see SDSNIVPD(DSNWMSGS). The IFCIDs described here are helpful in the diagnosis and resolution of indoubt thread error conditions.
IFCID 0203
IFCID 0203 reports a heuristic decision that forces a commit or rollback for a distributed indoubt thread. A heuristic decision is made when errors prevent or significantly delay automatic indoubt thread resolution.
This record is written when:
- A Db2 RECOVER INDOUBT command is issued
- During the resynchronization process
This IFCID is often produced under a system service task rather than the Db2 agent's task. For this reason, the fields in this trace record should take precedence over similar values that are found in the product information portion of the IFC trace data. For example, the LUWID in the product information describes the Db2 system service task. The LUWID in this record describes the Db2 agent's thread.
IFCID 0204
IFCID 0204 is written when Db2 attempts to reconnect to a remote system that requests a cold start.
A cold start means that the remote system has no memory of the work that was in progress when the previous connection failed. Db2 produces this record only when Db2 has memory of threads whose outcome must be resolved.
If Db2 was the coordinator of one or more of those threads, the partner system might have been indoubt when the cold start occurred. The Db2 coordinator assumes that the participant recovery log record is lost or damaged and indoubt threads cannot be resolved.
If the partner system was the coordinator of one or more of those threads, the local Db2 subsystem might be indoubt, requiring manual intervention with the RECOVER INDOUBT command.
This IFCID is often produced under a system service task rather than the Db2 agent's task. For this reason, the fields in this trace record should take precedence over similar values that are found in the product information portion of the IFC trace data. For example, the LUWID in the product information describes the Db2 system service task. The LUWID in this record describes the Db2 agent's thread.
IFCID 0207
IFCID 0207 reports when heuristic damage is detected during two-phase commit resynchronization.
Heuristic damage occurs when an operator forces an indoubt unit of work to commit or rollback, and the operator's choice conflicts with the outcome chosen by the coordinator of the unit of work. If the alerting Db2 is the participant, the damage is at this Db2. If the alerting Db2 is the coordinator, the damage is at the participant.
This trace record is recorded by the Db2 subsystem that makes the heuristic decision and any Db2 coordinator immediately upstream from that subsystem. Other Db2 subsystems that are involved in the unit of work do not produce this trace record.
This IFCID is often produced under a system service task rather than the Db2 agent's task. For this reason, the fields in this trace record should take precedence over similar values that are found in the product information portion of the IFC trace data. For example, the LUWID in the product information describes the Db2 system service task. The LUWID in this record describes the Db2 agent's thread.
IFCID 0209
IFCID 0209 is written when a communication failure occurs after 1 and before or during phase 2 of the resynchronization process.
The thread that experiences the communication failure might still be indoubt at the participant location. If Db2 is the participant, the status is indoubt. If Db2 is the coordinator, the status is commit or rollback.
IFCID 0234
IFCID 0234 records when CICS® or IMS attempts to perform indoubt thread resolution for a network identifier (NID) which Db2 does not recognize.
This error can occur due to the following reasons:
- a Db2 conditional restart
- a Db2 restart after your recover all of Db2 to a previous point in time
- an IMS or a CICS start with downlevel recovery logs
When a restart loses indoubt logical units of work, other downstream participants might be left with indoubt threads.
IFCID 0235
IFCID 0235 is written when a Db2 conditional restart results in partial information about a LUWID that might require resynchronization with a coordinator or participant. Incomplete information about the LUWID prevents resynchronization.
This IFCID is often produced under a system service task rather than the Db2 agent's task. For this reason, the fields in this trace record should take precedence over similar values that are found in the product information portion of the IFC trace data. For example, the LUWID in the product information describes the Db2 system service task. The LUWID in this record describes the Db2 agent's thread.