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

Explanation

Db2 has participant responsibility in the logical unit of work identified by 'luwid=token' for the coordinator at COORDINATOR 'location' and coordination responsibility in the same logical unit of work for the participant at PARTICIPANT 'location'. Heuristic damage occurred.
  • The application was told that commit succeeded.
  • Any resources updated at the coordinator and at this Db2 were committed.
  • Updated resources at the participant were rolled back.
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, 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.

System action

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

System programmer response

Determine the destination of statistics class 4. Locate and print the trace record with SEQUENCE NUMBER='seq-no'. Call the database administrator.

Database Administrator Action: Inform the database administrator at the coordinator 'location' and at the participant 'location' of the problem.

Correcting the damage at the participant is not an easy task. Since the time of the heuristic action, the data that was aborted using manual means might have been used by many applications - read and/or write. Correcting the damage might involve reversing the effects of these applications as well. The following information that is available at Db2 might be helpful in correcting the problem:
  • The statistics trace class 4 contains an IFCID 207 trace record. This record contains the RBA of the first Db2 log record written for the logical unit of work whose LUWID is included in this message.
  • The DSN1LOGP utility provides a summary report that identifies the table spaces modified by the logical unit of work at the local Db2 as well as any downstream participant locations involved in the logical unit of work. This information, while not directly related to the damage at the participant, might be useful in determining the scope of the problem.
  • DISPLAY THREAD TYPE(INDOUBT) displays the RBA of the first Db2 log record written for the logical unit of work whose LUWID is included in this message. This information continues to appear in the DISPLAY THREAD report until it is purged with the RESET INDOUBT command.

Contact your IBM® Support Center for further assistance.