DSNL404E PROTOCOL ERROR DURING INDOUBT THREAD RESOLUTION WITH COORDINATOR location LUWID=luwid=token INFORMATION RECORDED IN TRACE RECORD WITH IFCID=206 AND IFCID SEQUENCE NUMBER=seq-no

Explanation

Db2 has participant responsibility for the logical unit of work identified by 'luwid=token'. The Db2 thread associated with the logical unit of work is indoubt. A protocol error occurred during indoubt resolution with the coordinator identified by 'location'.
location
Either the relational database name (location-name) or the logical unit name (<luname>) of the coordinator.
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 206 was not active or it was active with a destination of the resident trace table only. IFCID 206 is a member of statistics class 4, which has a default destination of SMF.

System action

The indoubt thread remains indoubt. Alert A003 is generated. A trace record whose IFCID=206 is written.

System programmer response

This is an APARable error, probably at the coordinator, but possibly at the Db2 participant. The Db2 documentation required is contained in the statistics class 4 trace record that was written. 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: Db2 does not attempt to automatically resolve the indoubt thread. The indoubt thread must be manually resolved. The commit or abort decision made at the coordinator must be determined so that the same decision can be made at this participant Db2.

Contact the database administrator at the coordinator location 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, 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 at this (the participant) location to resolve the indoubt thread.