JR61337: NETEZZA CONNECTOR REPORTS NEGATIVE NUMBER OF ROWS IN JOB LOG

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

• Netezza connector reports incorrect, sometimes negative, number
  of read or written rows when the number of processed rows
  exceeds 2147483647.
  
  After reading 3790392806 rows of data from the database the
  connector reports -504574490 rows read.
  
  Log message:
  
  Netezza_Connector_0,0: Number of rows read: -504.574.490
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Netezza connector users
  ****************************************************************
  PROBLEM DESCRIPTION:
  Netezza connector reports incorrect, sometimes negative, number
  of read or written rows when the number of processed rows
  exceeds 2147483647.
  The incorrect row count depends on the actual number of
  processed rows and the platform DataStage is running on.
  
  For example after reading 3790392806 rows of data from the
  database the connector reports -504574490 rows read on Unix.
  The log message is:
  Netezza_Connector_0,0: Number of rows read: -504,574,490
  
  On Windows after reading 2147483647 or more rows the connector
  always reports 2147483647 rows read.
  ****************************************************************
  RECOMMENDATION
  Install patch JR61337
  ****************************************************************
  

Problem conclusion

• The problem root cause is the use of a data type incapable of
  storing integer numbers bigger than 2147483647 for manipulating
  the number of processed rows.
  The data type has been changed to a type compatible with ODBC
  SQLLEN data type to accommodate all possible values returned by
  ODBC function SQLGetRowCount.
  
  On Windows the problem root cause are limitations of 32-bit ODBC
  drivers, therefore the APAR patch does not correct the
  problematic behavior.
  

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