DSNL405I THREAD luwid=token PLACED IN INDOUBT STATE BECAUSE OF COMMUNICATION FAILURE WITH COORDINATOR location. INFORMATION RECORDED IN TRACE RECORD WITH IFCID=209 AND IFCID SEQUENCE NUMBER=seq-no

Explanation

During execution of the two phase commit protocol with the coordinator identified by 'location', communication failed. Phase 1 of the protocol completed and the thread is prepared for either commit or abort.

The thread is placed in the indoubt state and appears in a DISPLAY THREAD TYPE (INDOUBT) report. Periodic attempts are made to reestablish communication with the coordinator for automatic indoubt resolution. If successful, message DSNL407 or DSNL415 is written.
luwid=token
The global logical unit of work id and the local token that identify the thread.
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
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 209 was not active or it was active with a destination of the resident trace table only. IFCID 209 is a member of statistics class 4, which has a default destination of SMF.

System action

Alert A006 is generated. A trace record whose IFCID=209 is written.

Operator response

If message DSNL407 or DSNL415 for the LUWID specified in the DSNL405 message does not appear in a reasonable amount of time, call the system programmer.

System programmer response

Determine the cause of the communication failure and have the problem fixed. Db2 periodically attempts to reestablish communication. If the problem cannot be fixed in a reasonable amount of time, call the database administrator. Manual resolution of the indoubt thread might be necessary to release locked resources.

Database Administrator Action: Take the following actions to resolve this thread using manual means (that is, take heuristic action) if it is necessary to release locks held by this thread.
  • Determine the proper commit or abort decision by contacting the database administrator at the coordinator 'location' shown in this message in order to determine whether the thread with LUWID=luwid committed or aborted.
    If the coordinator system is another Db2, the following steps can be taken at the Db2 coordinator to determine the commit or abort decision.
    1. If the coordinator Db2 system is running and a Db2 conditional restart was not performed since the error was detected at this (the participant) location, ask the database administrator at the Db2 coordinator location to issue one of the following DISPLAY THREAD TYPE(INDOUBT) commands:
      • A -DISPLAY THREAD TYPE(INDOUBT), using the LOCATION keyword and specifying the location name of the local Db2.
      • A -DISPLAY THREAD TYPE(INDOUBT) LUWID(luwid)
      If a thread with LUWID=luwid appears in the display, then the display also includes the commit or abort decision. If no thread with LUWID=luwid appears in the display, then the thread was aborted.
    2. If the Db2 coordinator is down or if a conditional restart was performed there, ask the database administrator at the Db2 coordinator to run DSN1LOGP, specifying SUMMARY(ONLY) FILTER LUWID(luwid). The output from DSN1LOGP includes the commit or abort decision.
  • Use the RECOVER INDOUBT command to commit or abort the thread.