JR57517: DB2 CONNECTOR ACCESS DIFFERENT TABLE THAT HAS THE IDENTICAL NAME IN DIFFERENT SCHEMA.

APAR status

• Closed as program error.

Error description

• When two tables have the identical name but belong to different
  schemas, DB2 Connector load data to another table that it does
  not expect to access.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users having table partitioning for tables with the same name
  but within multiple schemas.
  ****************************************************************
  PROBLEM DESCRIPTION:
  When DB2 Connector is used with DB2 for z/OS on a partitioned
  table it can return wrong partition count of the table.
  Connector returns the number of partitions of a table, but if
  there are other tables with the same name, but different schema,
  their partitions can be returned.
  ****************************************************************
  RECOMMENDATION:
  Apply patch JR57517.
  ****************************************************************
  

Problem conclusion

• Handling of that specific case has been fixed. When checking
  partition count of a table, a proper query is used. The query
  checks if DBNAME columns are equal for between the table
  SYSIBM.SYSTABLEPART and SYSIBM.SYSTABLES.
  

Temporary fix

• Renaming the affected table making sure they have unique names
  across all schemas.
  

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

• RB31 PSY

     UP

• RB50 PSY

     UP