IBM Support

JR62477: SUBSEQUENT DML AFTER A DB2 ALTER TABLE RENAME COLUMN OPERATION IS REPLICATED STILL USES OLD COLUMN NAME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • With DDL replication enabled from Db2 -> Db2, CDC successfully
    replicates an alter table rename column operation to the
    target, and the target column name is renamed. But for any
    subsequent DML that is replicated CDC continues to use the old
    column name, so the DML fails to be applied.
    
    Expected behavior
    DML is replicated successfully after an Alter table rename
    column operation is replicated.
    

Local fix

  • After renaming a column, stop the subscription.
    
    You could just wait until the DML fails to be applied and then
    CDC will stop the subscription (due to this bug).
    
    Then manually update the table definition, re-assign and
    re-describe the table. Then restart the subscription.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue may affect you if you are using CDC for Db2 as    *
    * both source and target and you have rules-based              *
    * subscriptions configured.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a column was renamed on a source table, CDC attempted   *
    * to apply row changes that followed by using the original     *
    * column name. This would cause subscriptions to end           *
    * replication on error.                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.3-5566 or newer for Db2 resolves this
    issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62477

  • Reported component name

    IS CDC DB2 LUW

  • Reported component ID

    5725E30DL

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-25

  • Closed date

    2020-08-25

  • Last modified date

    2020-08-25

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B40","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
26 August 2020