DSNL401E INDOUBT THREAD RESOLUTION WITH COORDINATOR 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-no1 AND IN TRACE RECORD WITH IFCID=203 AND IFCID SEQUENCE NUMBER=seq-no2

Explanation

Db2 has participant responsibility in the logical unit of work identified by 'luwid=token'. Resolution with the coordinator identified by 'location' shows heuristic damage occurred. The Db2 thread representing the logical unit of work was previously resolved with the RECOVER INDOUBT command. The action taken was to commit the thread. Subsequently, communication was reestablished with the coordinator and resolution shows that the coordinator aborted the thread.
  • The application was told that commit failed.
  • Any resources updated at the coordinator were rolled back.
  • Updated resources at this Db2 were committed.
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-no1
The IFCID sequence number associated with the 207 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. This trace record is written when the heuristic damage condition was detected and contains information about the damage condition.
seq-no2
The IFCID sequence number associated with the 203 trace record. The sequence number is printed in hexadecimal format. If the sequence number is zero, IFCID 203 was not active or it was active with a destination of the resident trace table only. IFCID 203 is a member of statistics class 4, which has a default destination of SMF. This trace record was written when the heuristic decision to commit or abort was made and contains information about the decision, including the names of any downstream participants.

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-no1'. Call the database administrator.

Database Administrator Action: Correct the damage. This is not an easy task. Since the time of the heuristic action, the data that was committed with the RECOVER INDOUBT command might have been used by many applications - read and/or write. Correcting the damage might involve reversing the effects of these applications as well. Tools available are:
  • 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, and any downstream participant locations involved in the logical unit of work.
  • 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.