Table of Contents

Search

  1. Preface
  2. DTL0001 to DTL5008
  3. DTL58001 to DTL62569
  4. PWXEDM172000 to PWXEDM173002
  5. PWXEDM175000 to PWXEDM175050
  6. PWXEDM176400 to PWXEDM177699
  7. PWXEDM181200 to PWXEDM181599
  8. PWXEDM261000 to PWXEDM263999
  9. Abend, Return, and Reason Codes in PowerExchange Messages

Message Reference Volume 3

Message Reference Volume 3

PWXEDM 177564 W

PWXEDM
177564
W

Possible missing End Commit2 for
uowid
.
data_sharing_member_id
at
log_rba_or_lrsn
.
data_sharing_member_id
.
sequence_number
The DB2 ECCR was processing a UR record for a UOW when it detected that a different UOW was in a questionable state and might be missing the End Commit2 record. For the ECCR to detect this situation, the specified outstanding UOW that is in a questionable state must have begun commit processing. That is, the ECCR encountered the Begin Phase2 UR record or Phase 1/2 Transition UR record for the UOW. This situation occurs only when the ECCR is reading at the very “edge” of the DB2 log data.
Subsequent message PWXEDM177565W identifies the last operation type that was encountered for this UOW, along with the DB2 log location at which the problem occurred.
Processing continues.
This situation can occur when the DB2 data-sharing member that is specified as part of the UOWID is not busy. This message can persist for up to three DB2 checkpoint cycles for the data-sharing member. If the message persists after the DB2 data-sharing member becomes busy or has gone through three DB2 checkpoint cycles, collect the following types of diagnostic information:
  • An SVC dump for the DB2 ECCR and any started tasks for the DB2 subsystem or for data-sharing group members.
  • JES output from the DB2 ECCR and the DB2 subsystem.
  • Output from DB2 DSN1LOGP utility.
  • Copies of the archive logs that contain the log data where this problem was encountered.
Then contact Informatica Global Customer Support.

0 COMMENTS

We’d like to hear from you!