DSNL402I INDOUBT THREAD RESOLUTION WITH PARTICIPANT location SHOWS HEURISTIC DAMAGE FOR luwid=token - REMOTE COMMIT VERSUS LOCAL ABORT. INFORMATION RECORDED IN TRACE RECORD WITH IFCID=207 AND IFCID SEQUENCE NUMBER=seq-no

Explanation

Db2 has coordinator responsibility for the logical unit of work identified by 'luwid=token'. Resolution with a participant shows heuristic damage occurred. The participant identified by 'location' manually resolved the indoubt thread identified by 'luwid=token'. The action taken was to commit the thread. This is inconsistent with the abort decision of the coordinator.
  • The application was told that commit failed.
  • Any resources updated at the participant were committed.
  • Updated resources at this Db2 were rolled back.
location
The field contains one of the following:
  • The requester's relational database name (location name)
  • The requester's VTAM® LU name (<luname>)
  • The requester's IP address
luwid=token
The global logical unit of work id and the local token that identify the thread.
seq-no
The IFCID sequence number associated with the trace record. The sequence number is printed in hexadecimal format. If the sequence number is zero, then IFCID 207 was not active or it was active with a destination of the resident trace table only. IFCID 207 is a member of statistics class 4, which has a default destination of SMF.

If the location specified refers to a Db2 for Linux®, UNIX, and Windows system that is running at the DB2® 9 level or later, and that server location has enabled access to non-Db2 databases through the Federated Database or Information Integrator capability, then any updates made to that downstream non-Db2 database will be processed under the control of the Db2 for Linux, UNIX, and Windows unprotected update capability. This permits changes to be made to this downstream non-Db2 database, even when the changes were being requested through applications running under two-phase commit or protected update control, such as CICS® and IMS. During phase one of commit processing, the Db2 for Linux, UNIX, and Windows server will have actually committed the changes to the downstream non-Db2 database by the time it replies to this Db2 that it is prepared to accept a commit decision from. However, if during phase one commit negotiation with other downstream database servers and other coordinated resource managers from CICS or IMS, the decision is made to abort the unit of work, this will result in heuristic damage to the data at the non-Db2 database downstream of the Db2 for Linux, UNIX, and Windows server. No attempts will be made to resync with the identified remote location server, and a Db2 indoubt thread will not be left in Db2 to reflect this issue.

System action

Alert A004 is generated. A trace record whose IFCID=207 is written. Indoubt resolution with the participant completes.

System programmer response

Call the database administrator.

Database Administrator Action: Inform the database administrator at 'location' that heuristic damage occurred for the logical unit of work with LUWID='luwid'. Db2 was the coordinator for the logical unit of work and made the decision to abort the database updates made by 'luwid'. At 'location' a heuristic decision was made to COMMIT the updates made by 'luwid'.

Information about the heuristic damage continues to appear in the DISPLAY THREAD TYPE(INDOUBT) report until it is purged with the RESET INDOUBT command.