JR61141: OEM AMAZON REDSHIFT DRIVER RETURNS NON-NULLABLE COLUMN AS NULLABILITY UNKNOWN

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

• Incorrect nullability can cause RCP jobs to fail when a
  processing stage compares nullalibity with another source. (eg/
  When using the Change Capture)
  

Local fix

• Use Amazon's (Vendor Official) RedShift Driver.
  

Problem summary

• Redshift JDBC driver is not correctly reporting Nullability
  MetaData information.
  
    If a column 'c' is defined as 'integer' & 'not null', there is
  a discrepency in the way
    non-nullable columns are returned by the Amazon Redshift
  driver. A similar warning may
    appear in the job log:
  
    The link column c is defined as Integer Signed Not Nullable
  and the respective column
    in the JDBC data source is defined as INTEGER SIGNED NULLABLE
  UNKNOWN. To match the data
    source column definition the link column should be defined as
  Integer Signed Nullable.
  

Problem conclusion

• The issue is due to a bug in Redshift Drivers  not returning the
  expected values for ResultSetMetaData.isNullable().. The issue
  is resolved by them now and have delivered new set of fixed
  drivers.
  
  To enable this connection option, append
  ExtendedColumnMetaData=true to the
    URL connection string.
  
    Example:
  
  jdbc:ibm:redshift://<YourServer>:<portnumber>;DatabaseName=<name
  >;ExtendedColumnMetaData=true
  

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:

Modules/Macros

• JDBC
  

Fix information

• Fixed component name

  INFO SRVR PLATF

• Fixed component ID

  5724Q3612

Applicable component levels

• RB50 PSY

     UP