DSNL438I RESYNC STATUS PURGED FOR COORDINATOR location. LUWID=luwid, URID=urid, STATUS=s INFORMATION RECORDED IN TRACE RECORD WITH IFCID=235 and IFCID SEQUENCE NUMBER=seq-no

Explanation

The information related to resynchronization with the remote coordinator location for the logical unit of work identified by 'luwid', which is displayed in this message, is being purged by Db2. Automatic indoubt resolution responsibility for this distributed logical unit of work can no longer be performed.

This situation can arise in one of two ways;
  • A Db2 conditional restart (other than a Db2 cold start; that is, a Db2 conditional restart with STARTRBA=ENDRBA) is being performed.
  • An inconsistency in the Db2 log was detected during Db2 restart processing (indicated by a DSNL429I message).
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
luwid
The global logical unit of work id that identifies the logical unit of work.
urid
The unit of recovery identifier. This is the RBA on the Db2 recovery log of the log record that marks the beginning of the logical unit of work. This is the earliest RBA required to process the logical unit of work during restart.
s
Restart status of the logical unit of work. When Db2 came down, the logical unit of work was in one of these states:
A
INABORT: The logical unit of work was in the must-complete phase of abort, but abort has not yet completed.
C
INCOMMIT: The logical unit of work was in the must-complete phase of commit, but commit has not yet completed.
D
INDOUBT: The logical unit of work completed the first phase of commit, but Db2 has not yet received the commit or abort decision from the coordinator.
F
INFLIGHT: The logical unit of work has not yet completed the first phase of commit and should be backed out.
U
UNKNOWN: The status of the logical unit of work is not known to Db2 because of conditional restart.
seq-no
The IFCID sequence number associated with the trace record. The trace record is written to statistics class 4, which is started to SMF as a default during Db2 installation. Statistics class 4 must be started to a permanent destination (SMF or GTF) for the trace record to be accessible. The sequence number is printed in hexadecimal.

System action

Processing continues normally.

System programmer response

Call the database administrator.

Database Administrator Action: The resynchronization information that was purged by Db2 is recorded in this message. To determine the proper commit or abort decision made by the coordinator at 'location', use the status code as follows:
A
The correct decision is to abort the logical unit of work.
C
The correct decision is to commit the logical unit of work.
D
Contact the database administrator at 'location' to determine the correct decision.
F
The correct decision is to abort the logical unit of work.
U
Contact the database administrator at 'location' to determine the correct decision.