JR61902: DB2 CONNECTOR FAILS ON SCHEMA RECONCILIATION WHEN DIVERSE TABLES WITH THE SAME NAME EXIST IN VARIOUS SCHEMAS.

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 fails on schema reconciliation when diverse tables
  with the same name exist in various schemas.
  
  Job design is simple like "RowGene --> Trans --> DB2CC"
  
  There are two same name tables in different schema in database.
   create table user1.test1 (c1 integer, c2 char(5)
   create table db2inst1.test1 (c1 integer, c2 integer)
  
  Direct Insert mode in DB2CC is 'NO'.
  
  The job works coorrectly with the following setting.
   user : db2inst1
   table name : db2inst1.test1
  
  It aborts with the following setting.
   user : db2inst1
   table name : test1
  
  Error messages is below.
     Item #: 35
     Event ID: 34
     TimeStamp: 2020-01-24 13:28:20
     Type: Fatal
     User name: dsadm
     Message ID: IIS-CONN-DAAPI-00398
     Message: DB2_Connector_7: Schema reconciliation detected a
  size mismatch for column c2. When writing column INT32 into
  database column CHAR(min=5,max=5), truncation, loss of
  precision, data corruption or padding can occur.
  (CC_DBSchemaRules::reportSizeMismatch, file
  CC_DBSchemaRules.cpp, line 1,764)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DB2 Connector users having diverse tables with the same name in
  different schemas.
  ****************************************************************
  
  PROBLEM DESCRIPTION:
  DB2 Connector fetched column information for a table without
  specifying schema name, this caused failures on schema
  reconciliation, when diverse tables with the same name existed
  in various schemas in the same database.
  ****************************************************************
  RECOMMENDATION
  apply patch for JR61902
  ****************************************************************
  

Problem conclusion

• DB2 Connector code has been altered to fetch information about
  the table from CURRENT SCHEMA, if the table name provided in
  connector configuration does not include a schema name. This
  allows to pass schema reconciliation successfully in the
  problematic scenario.
  

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

• RB71 PSY

     UP