DSNL433I DDF IS PARTICIPANT FOR nnnn INDOUBT THREADS WITH mmmm REMOTE PARTNERS
Explanation
- nnnn
- The number of indoubt threads for which Db2 is the participant
- mmmm
- The number of remote partners that have coordinator responsibility
System action
Processing continues normally.
Operator response
If the message was issued as a result of DDF starting, no action is necessary. If the message was issued as a result of DDF stopping, contact the database administrator.
Database Administrator Action: If the message was issued as a result of stopping DDF, then Db2 maintained all information necessary to perform automatic resynchronization with partner locations and resolve all indoubt units of work. Issue the START DDF command to initiate this process.
If you do not want to perform automatic resynchronization, you can still resolve the indoubt units of work for which Db2 is a participant and which hold database resources locked. Use the DISPLAY THREAD command for type indoubt threads to produce a display that lists these threads. Then use the RECOVER INDOUBT command to either commit or abort these units of work.
To avoid data inconsistency, coordinate this manual resolution with the database administrators at the locations that have coordinator responsibility for each indoubt unit of work. If any of the indoubt units of work at Db2 also have coordinator responsibility for participant locations, then you should notify the database administrators at the participant locations of the commit or abort decision so they can make the same decision.