Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(3 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

DB2 z/OS Change Data Capture data integrity and  stabilty issue introduced by DB2 V10 support
Content

PowerExchange 9.1.0 HotFix 2 added DB2 V10 Change Data Capture support for DB10 V10. The changes in DB2 V10 include:

  • Changes to the content and layout of DB2 log records 
  • Changes to the way Reordered Row formatting is handled
  • Enhanced schema versioning   
  • Changes to the IFI 306 API PowerExchange calls to retrieve the DB2 log records
The DB2 V10 Change Data Capture support has introduced some issues. These errors cause multiple symptoms including the skipping of row changes on the DB2 log and ECCR failures, some of which cannot be recovered without risk of impacting data integrity.
 
The failures in the PowerExchange Change Data Capture ECCR are a result of issues with the ECCR changes that were made to incorporate the changes in DB2 V10. The ECCR processing errors can be encountered while processing both DB2 V9 and DB2 V10. 
 
To avoid these issue, upgrade PowerExchange and the DB2 Change Data Capture to a level of maintenance that includes fixes for the known failures.
This can be done by upgrading to V910_HF6, V951 or V951_HF1 and an appropriate set of EBF patches on top of each level. Each maintenance level includes all of the fixes that are part of previous levels.   
 
For more information about the additional EBF patches read the knowledge base articles listed below. Contact GCS for assistance to upgrade the ECCR from other levels of maintenance.


More Information

 

HotFix Patch & Description




Impact 


HF3 P574573 : PWXEDM177443E PROCESSING SYSCOPY CLR RECS

DB2 log processing error
HF3 P577758: PWXEDM177432/3/4/5 INVALID LENGTH OF SYSXXX COLUMN VALUE
DB2 log processing error
HF4 P581430: PWXEDM177588E V9 SYSCOPY ACCESS POST-513905

DB2 log processing error
HF4 P540265: PWXEDM177442E W/DB2 ECCR REFRESH, PWX177430E W/WARM START W/DDL DB2 log processing error
HF5 P594619: PWXEDM177443E PROCESSING SYSCOPY CLR RECS AFTER P574573
DB2 log processing error
HF5 P585696 : ALLOW USER TO SKIP DECOMPRESSION ERRORS


Feature


HF5 P595652: PWXEDM172801E POINT FAILED RC8/RSN18


Reordered Row Processing Error
HF5 P590843: PERSISTENT PWXEDM177564W CLEARED ON RESTART

Possible  missed change records
HF6  & V951 P623214 : SQLCODE-180 INSERT TCAPTABLEPART W/P572551

DB2 log processing error
HF6  & V951 P624886 : PWXEDM177582E OR 177608E POST-P572551


DB2 log processing error
HF6  & V951 P612166: PWXEDM177456E W/NO SCHEMA MISMATCH WHEN PROCESSING BACKOUT
Reordered Row Processing Error
HF6  & V951 P572551: IMPROVE ROW VERSION TRACKING



Reordered Row Processing Error
HF6  & V951 P613676: PERSISTENT PWXEDM177564 POST-P590843


Possible  missed change records
HF6  & V951 P606434: PWXEDM177430E AFTER REFRESH REPEATS DDL


Change Data Capture repository corruption 
HF6  & V951 P613674: PWXEDM177430E W/DDL AFTER SYSCOPY UPDATE


Change Data Capture repository corruption 
post HF6  & V951 P629129 : PWXEDM177588E ACCESSING SYSIBM.SYSCOPY  

DB2 log processing error
post HF6  & V951 P626776 : CORRECT VERSFIX SAMPLIB MEMBER                                 DB2 log processing error
post HF6  & V951 P627674: IMPROVE DDL PROCESSING                                                Reordered Row Processing Error
post HF6  & V951 P634743: ABENDS0C4 IN EDITPROC PROCESSING RRF ROWS 

Reordered Row Processing Error
post HF6  & V951 P631833: PWXEDM177536W POST-P613676 (2)                                    Possible  missed change records
post HF6  & V951 P633648: PWXEDM177599E after  P572551 or V910_HF6   

Version processing Error

 

 


Reference


Attachments


Applies To
Product: PowerExchange
Problem Type:
User Type:
Project Phase:
Product Version: PowerExchange 9.1.0; PowerExchange 9.5; PowerExchange 9.5.1; PowerExchange 9.5.1 HotFix 1
Database:
Operating System:
Other Software:

Last Modified Date: 8/12/2013 7:44 PM ID: 148595
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)