IBM Support

JR46899: INCORRECT DDL DETECTION ON TABLES CONTAINING VARIABLE LENGTH COLUMNS PREVENTS MIRRORING DATA IN SUCH TABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An error message is issued during mirroring and the subscription
    stops.
    
    
    
    The error message logged to the event log is:
    
    IBM InfoSphere Change Data Capture encountered an error while
    processing data for table with id {id} and name {name}. The
    error could be related to DDL done on the table recently or in
    the past. Please rebuild the table and refresh to reposition
    past the current log position. Please review Microsoft
    documentation possible options to rebuild the table
    IBM InfoSphere Change Data Capture detected that the Microsoft
    SQL Server internal metadata does not contain sequenced variable
    length columns format. The metadata can be in such a state when
    DDL have been performed on the table .
    
    Users Affected :
    Users replicating tables with:
    1. Users replicating partitioned tables that contain:
    1.1. Variable length columns or
    1.2 non unique clustered indexes
    1.3 a combination of the above
    

Local fix

  • Do not use partitioned tables
    

Problem summary

  • An error message is issued during mirroring and the subscription
     stops.
    
    The error message logged to the event log is:
    
    IBM InfoSphere Change Data Capture encountered an error while
    processing data for table with id {id} and name {name}. The
    error could be related to DDL done on the table recently or in
    the past. Please rebuild the table and refresh to reposition
    past the current log position. Please review Microsoft
    documentation possible options to rebuild the table
    IBM InfoSphere Change Data Capture detected that the Microsoft
    SQL Server internal metadata does not contain sequenced variable
    length columns format. The metadata can be in such a state when
    DDL have been performed on the table .
    
    This issue affect users running IIDR 10.2 for Microsoft SQL
    Server replicating partitioned tables containing:
    1. Variable length columns or
    2. Non unique clustered indexes
    3. A combination of the above
    

Problem conclusion

  • This issue is fixed by applying IIDR 10.2 Interim Fix 1 for
    Microsoft SQL Server.
    

Temporary fix

  • Do not use partitioned tables.
    

Comments

APAR Information

  • APAR number

    JR46899

  • Reported component name

    IS CDD MS SQL S

  • Reported component ID

    5725E30SQ

  • Reported release

    A20

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-07

  • Closed date

    2013-06-07

  • Last modified date

    2013-06-07

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

    JR46323

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

Fix information

  • Fixed component name

    IS CDD MS SQL S

  • Fixed component ID

    5725E30SQ

Applicable component levels

  • RA20 PSY

       UP

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

Document Information

Modified date:
12 October 2021