JR64571: LOG READER HANDLING FOR CREATE PARTITION DDL IS SLOW AND GENERATES EXCESSIVE TRACE LINES

APAR status

• Closed as program error.

Error description

• The client frequently adds range partitions, and most of them
  are to out-of-scope tables. They see many trace lines that
  "Table with table id xxx was not found in the system catalog."
  When this occurs, they observed that CDC appeared to stop
  mirroring data although the status of mappings are "mirror
  continuous". However, in a few hours, it will start mirroring
  again with no recovery steps done by the customer. The client
  says this occurs when they are adding range partitions. Here is
  one of the trace lines :
  
  481 2021-11-09 11:24:16.830 SHAREDSCRAPE LOG READER FOR NODE
  0{139} com.datamirror.ts.scrapers.db2udbscraper.RecordReader
  addTableToScope() Table with table id 736 was not found in the
  system catalog. The table must have been dropped. The create
  table or undo of drop table will be ignored.
  

Local fix

• Setting the system property
  mirror_head_of_log_sleep_milliseconds to a
  small value, such as 25. This should reduce the delay for each
  add partition DDL from 5 seconds to 1/4 second.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue might affect you if you are using IDR             *
  * 11.4.0.4-5622 or earlier for Db2 LUW as a source engine.     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Performance when handling "create partition" was not         *
  * optimal.                                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.4-5625 or newer for Db2 LUW.           *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.4-5625 or newer for Db2 LUW resolves the
  issue.
  

Temporary fix

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