DSNL403I INDOUBT THREAD RESOLUTION WITH PARTICIPANT location SHOWS HEURISTIC DAMAGE FOR luwid=token - REMOTE ABORT VERSUS LOCAL COMMIT. 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 abort the thread. This is inconsistent with the commit decision of the coordinator.
  • The application was told that commit succeeded.
  • Any resources updated at the participant were rolled back.
  • Updated resources at this Db2 were committed.
location
This 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, 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.

System action

Alert A004 is generated. A trace record with 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 COMMIT the database updates made by 'luwid'. At 'location' a heuristic decision was made to back out (ABORT) 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.