Table of Contents

Search

  1. Preface
  2. DTL0001 to DTL3004
  3. DTL58001 to DTL62591
  4. PWXEDM172000 to PWXEDM173002
  5. PWXEDM175000 to PWXEDM175648
  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 172781 E

PWXEDM
172781
E

Missing data at EOF on log
dataset archive.log.dataset.name
. Expected last RBA
eeeeeeeeeeee
, found RBA
ffffffffffff
The EDM Logger was processing data in an archive log data set, and encountered the end of the data set. However, the last log record read did not have the RBA value that was expected. The RBA range in each log data set is recorded in the Restart data sets, but the last log record read did not have the ending RBA recorded for this log data set. So, data that should have been found in the log data set is missing. The archive log data set in which this condition was found, the RBA that was expected to be found, and the RBA value that was found in the last record read, are all included in the message. This is most likely the result of an I/O error in reading or writing the archive log data set.
The following actions occur:
  1. Error message identified as PWXEDM172781E issued.
  2. The Logger task that encountered this error ends. If this was a task that was reading log data for a log reader process, this will cause the associated log reader process to terminate as well. If this occurs during initialization of the PowerExchange Logger, the PowerExchange Logger address space will terminate.
Examine the status of the log data set that had the error. Try reading the data set yourself to see if the error is permanent or temporary. If the error seems permanent, you may need to use the corresponding secondary log data set to recreate the failing primary log data set. You can then restart the log reader process that failed, or the PowerExchange Logger itself, if the failure occurred during Logger initialization. If you cannot correct the problem, contact Informatica Corporation Product Support.

0 COMMENTS

We’d like to hear from you!