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 177589 W

PWXEDM
177589
W

Excessive schema version entries bypassed for '
creator
.
table_name
' in dataset '
data_set_name
'.
During initialization, the DB2 ECCR tried to get schema version information for the specified table by reading the tablespace data set or partition data sets for the table. While processing the schema version information, the DB2 ECCR found too many schema versions. The maximum number of schema versions is 100.
The DB2 ECCR records information for only the 100 most recent schema versions for the table. If the ECCR encounters log records with an older schema version, it issues this message to warn of a potential problem in capturing data for the table.
This problem can occur only if you use DB2 Version 9.1 or later.
This message includes the fully-qualified table name and the name of the tablespace or partition data set that was being processed when the problem occurred.
If the ECCR encounters log records with older schema versions, it might not interpret the log data correctly. In this case, the ECCR issues message PWXEDM177456E or PWXEDM177460E and reacts in one of the following ways, depending on the setting of the EC PERMIL statement in the REPL2OPT DD data set:
  • If the EC PERMIL value is 0 or has been exceeded, the ECCR abends.
  • If the EC PERMIL value has not be exceeded, the ECCR discards the log records.
Normally, if you reorganized the tablespace or partition after making a schema change that incremented the schema version number, no rows in the table should been recorded with an older schema version.
If the ECCR encounters errors, follow the instructions in message PWXEDM177456E or PWXEDM177460E.
To prevent this problem from reoccurring in the future, reorganize the tablespace or partitions that contain this table. This action eliminates the older schema versions.

0 COMMENTS

We’d like to hear from you!