DSNL414E PROTOCOL ERROR DURING INDOUBT THREAD RESOLUTION WITH PARTICIPANT location LUWID=luwid=token INFORMATION RECORDED IN TRACE RECORD WITH IFCID=206 AND IFCID SEQUENCE NUMBER=seq-no
Explanation
Db2 has coordinator responsibility for the logical unit of work identified by 'luwid=token'. The Db2 thread associated with the logical unit of work is either committed or aborted. A protocol error occurred during indoubt resolution with the participant identified by 'location'.
- location
- The relational database name (location-name) of the participant.
- 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
Alert A003 is generated. A trace record whose IFCID=206 is written.
System programmer response
This is an APARable error, probably at the participant, but possibly at the Db2 coordinator. The Db2 documentation required is contained in the statistics class 4 trace record. Determine the destination of statistics class 4. Locate and print the trace record with SEQUENCE NUMBER='seq-no'.
Call the database administrator. The participant might need to manually resolve the indoubt thread.
Database Administrator Action: The Db2 coordinator maintains knowledge of the indoubt participant until it is purged with the RESET INDOUBT command. If the thread is indoubt at the participant, it must be manually (heuristically) resolved. The status of the thread at the local Db2 (the coordinator) can be determined with the DISPLAY THREAD command for type indoubt threads by including the LUWID('token') parameter in the command.
If the participant is another Db2, the RECOVER INDOUBT command can be used to resolve the indoubt thread.