JR48339: DUPLICATE ROWS FOUND DURING REFRESH

Fix list for IBM InfoSphere Change Data Capture

APAR status

• Closed as program error.

Error description

• During refresh, if the source's SELECT does not have consistent
  read, the target may end up with duplicated rows. DB2 deletes
  the duplicated rows and CDC/DB2 treats refresh as failed. The
  following messages are seen in the target log:
  
  "Load API reported errors while loading file <load file>. Check
  LOADMSG file for more information"
  
  In the LOADMSG file, users can see:
  
  SQL3500W The utility is beginning the "DELETE" phase at time
  "10/10/2013
  18:44:15.875964".
  
  SQL3509W The utility has deleted "5" rows from the table.
  
  SQL3515W The utility has finished the "DELETE" phase at time
  "10/10/2013
  18:44:15.883909".
  

Local fix

• Users can try the following workaround:
  
  -Remove the unique constraint from the target(or change it to
  non-unique)
  -Start refresh(just refresh) and let refresh finish.
  -Start mirroring and then end mirroring with schedule end now.
  This should mirror all the changes that was done during refresh
  and address the duplicated rows.
  -Re-enable the unique constraint.
  

Problem summary

• During refresh, if the source's SELECT does not have consistent
  read, the target may end up with duplicated rows. DB2 deletes
  the duplicated rows and CDC/DB2 treats refresh as failed. The
  following messages are seen in the target log:
  
  "Load API reported errors while loading file <load file>. Check
  LOADMSG file for more information"
  
  In the LOADMSG file, users can see:
  
  SQL3500W The utility is beginning the "DELETE" phase at time
  "10/10/2013
  18:44:15.875964".
  
  SQL3509W The utility has deleted "5" rows from the table.
  
  SQL3515W The utility has finished the "DELETE" phase at time
  "10/10/2013 18:44:15"
  

Problem conclusion

• This issue is fixed by applying IIDR 10.2 Interim Fix 4 for DB2
  LUW.
  

Temporary fix

• Users can try the following workaround:
  
  -Remove the unique constraint from the target(or change it to
  non-unique)
  -Start refresh(just refresh) and let refresh finish.
  -Start mirroring and then end mirroring with schedule end now.
  This should mirror all the changes that was done during refresh
  and address the duplicated rows.
  -Re-enable the unique constraint.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IS CDC DB2 LUW

• Fixed component ID

  5725E30DL

Applicable component levels

• RA20 PSY

     UP