JR65076: THE DMLS ON NEW PARTITION ARE NOT REPLICATED AFTER READD TABLE IF THE SUB IS STARTED WHEN AT LEAST A SUB IS MIRRORING

APAR status

• Closed as program error.

Error description

• The DMLs on new partition are not replicated after readd table
  if the subscription containing the table in question was able to
  use single scrape staging store if it started after at least
  another subscription was already running in MIRROR
  

Local fix

• 1. Toggling replication methods (changing replication method
  from MIRROR to REFRESH and back to MIRROR), OR
  2. Ensure updating table definition for all the affected tables
  first, then start all the subscriptions together.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * You might be affected by this issue if you replicate         *
  * partitioned Oracle tables and single scrape is enabled.      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The single scrape log reader was not restarting after        *
  * re-adding a table definition after adding a partition, so    *
  * the partition ID was not tracked.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.4-5564 or newer for Oracle.            *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.4-5564 or newer for Oracle 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 ORACLE

• Fixed component ID

  5725E30OR

Applicable component levels