JR51256: ENHANCE THE DETECTION OF DDL THAT ISSUES "IBM INFOSPHERE CHANGE DATA CAPTURE DETECTED THAT THE MICROSOFT SQL SERVER INTERNALMETA

APAR status

• Closed as program error.

Error description

• IBM InfoSphere Change Data Capture encountered an error while
  processing data for table with id {0} and name {1}. 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 a format for
  sequenced variable length columns. This could be the result of
  a structural change to the table, such as a DDL statement,
  having occurred.
  The select
   SELECT pc.partition_id,
         p.partition_number,
         name =(SELECT name FROM sys.columns sc WHERE
  sc.object_id = p.object_id AND sc.column_id =
  pc.partition_column_id ),
         pc.leaf_offset,
         pc.leaf_null_bit,
         pc.leaf_bit_position,
         pc.max_inrow_length,
         system_type_id = case when pc.max_length = -1 then
  pc.system_type_id + 1 ELSE pc.system_type_id end,
         data_type = t.[name],
         pc.precision,
         pc.scale,
         codepage = CAST(COLLATIONPROPERTY(pc.collation_name,
  'CodePage') AS int),
         is_dropped,
         is_uniqueifier
  FROM sys.system_internals_partition_columns pc
         INNER JOIN sys.partitions p ON pc.partition_id =
  p.partition_id
         INNER JOIN sys.types t ON t.system_type_id =
  pc.system_type_id
                AND t.user_type_id = pc.system_type_id
  WHERE p.object_id = {object_id}
         AND p.index_id <= 1
  returns column names sorted in alphabetical order
  

Local fix

Problem summary

• IIDR 10.2 for Microsoft SQL Server fails with the following
  event:
  IBM InfoSphere Change Data Capture encountered an error while
  processing data for table with id {0}and name "{1}. 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.
  even though there was no DDL performed on the table.
  
  This issue affects users running IIDR Interim Fix 10 for
  Microsoft SQL Server (and below).
  

Problem conclusion

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

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 SQL

• Fixed component ID

  5725E30SQ

Applicable component levels

• RA20 PSY

     UP