JR61073: DB2 CONNECTOR FAILS TO READ XML COLUMNS USING RUNTIME COLUMN PROPAGATION

IBM InfoSphere Information Server, Version 11.7.1.1 (Fix Pack 1)
IBM InfoSphere Information Server, Version 11.7.1.1 for AIX
IBM InfoSphere Information Server, Version 11.7.1.1 for Windows
IBM InfoSphere Information Server, Version 11.7.1.1 for Linux

APAR status

• Closed as program error.

Error description

• DB2 connector reading data from a table with XML column using
  runtime column propagation reports the following error:
  Design schema field: <XML_COLUMN_NAME> cannot be unbounded.
  Maximum length must be specified
  (CC_DB2MetadataHelper::negotiateDataFields, file
  CC_DB2MetadataHelper.cpp, line 4,494)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DB2 connector users using RCP when reading data from tables with
  XML type columns.
  ****************************************************************
  PROBLEM DESCRIPTION:
  DB2 connector reading data from a table with XML column using
  runtime
  column propagation reports the following error:
    Design schema field: <XML_COLUMN_NAME> cannot be unbounded.
  Maximum
    length must be specified
  (CC_DB2MetadataHelper::negotiateDataFields,
    file CC_DB2MetadataHelper.cpp, line 4,494)
  
  The problem is caused by the fact that DB2 connector processes
  XML columns
  as VARCHAR internally and expects the column length to be
  specified in the
  link column design, because it is not possible to determine the
  XML column
  length from database table metadata.
  Currently this requirement applies also when runtime column
  propagation
  is enabled for a link.
  
  ****************************************************************
  RECOMMENDATION
  Install patch for this APAR.
  ****************************************************************
  

Problem conclusion

• DB2 connector has been modified to treat XML columns like DBCLOB
   columns
  internally, when runtime column propagation is enabled. This way
  of
  processing XML columns removes the need to specify the column
  length,
  but implies the Array size to be set to '1', similarly to other
  LOB
  column types.
  It is still possible to treat the XML column as VARCHAR by
  specifying
  the column design only for the XML columns on the link.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• RB50 PSY

     UP

• RB70 PSY

     UP

• RB71 PSY

     UP