JR34863: ROLLUP OF CHANGES MADE TO DB2 EE STAGE IN DS 7.5.1.A (SINCE PATC H_E118136)

APAR status

• Closed as program error.

Error description

• Fixes added:
  
  Ecases:
  ----------
  e97195  - DB2 Upsert of table in checking pending state does
  not abort
  e131403 - Data is garbled (nulls are inserted) during
  extraction from a table having a column of type vargraphic
  e116933 - DB2 stage CLOSE COMMAND returns fatal error on empty
  table when it should be warning message
  e133594 - Job log reports multiple LOAD v8 API warnings.
  e118215 - When loading into DB2 table with partition key column
  of double type, the job fails with a essage "Row found on
  wrong partition".
  e118424 - When loading hangul data to a DB2 table with
  partition key column of char or varchar, the loading fails
  with a message "Row found on wrong partition".
  e124621 - DB2 Upsert cannot handle CHAR FOR BIT DATA column
  type
  e129988 - DB2 Upsert throws an error of the form "Failed to
  bind the parameter number 5: c_type = ****, paramType =
  ***,colSize = 0, data_size = 0."
  e119499 - DB2 EE cannot "real" values into a table with a
  column of type REAL
  
  APARs
  ---------
  JR30784 - DB2 EE Load job fails when "Cleanup on Failuire"
  property is set to True
  JR30505 - The DB2 EE Stage using LOAD TRUNCATE with 0 rows,
  does not execute the command.
  JR29511 - The DB2 EE Sparse lookup failswith the following
  error message:
  Sequential_File_42: Error when checking operator: Could not
  find input field "A".
  JR33486 - The DB2 EE stage receives the following error in
  Write mode:
  The file
  `/home/dsadm/remote_db2config/maxinst1/sqllib/db2nodes.cfg'
  must exist and be readable by all users!
  even though it is present on the ETL server.
  JR32948 - DB2 EE job fails when using stage property 'USE
  DEFAULT SERVER = TRUE'
  

Local fix

• This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  The rollup is available for 7.5.3, 8.0.1 and 8.1
  ****************************************************************
  PROBLEM DESCRIPTION:
  Rollup of fixes since ecase 118136
  ****************************************************************
  RECOMMENDATION:
  Install patch_JR34863
  ****************************************************************
  

Problem conclusion

• The list of fixes is as follows:
  
  Ecases
  -------
  e97193 - db2upsert does not give Warning messages for failed
  rows
  e97195 - db2upsert job does not abort for generic database
  errors.
  e131403 - During extraction from a DB2 table field of VARGRAPHIC
  into a nvarchar field; null characters are inserted after the
  data
  e116933 - DB2 stage CLOSE COMMAND returns fatal error on empty
  table when it should be warning message
  e133594 - Warnings of the form "LOAD v8 API warning" are
  thrown by DB2 EE Load jobs
  e118215 - When loading data to DB2 table which has partition key
  column of double type, the job fails with a message "Row found
  on wrong partition".
  e118424 - When loading hangul data to a DB2 table with partition
  key column of char or varchar, the loading fails with a message
  "Row found on wrong
  partition".
  e108273 - DB2 partitioner seems to fail to load rows to the
  correct partitions when certain values are seen in the
  partitioning key.
  e124621 - db2upsert cannot handle FOR BIT DATA
  e118136 - Support for parallel execution against range
  partitioned tables
  e129988 - When using DB2EE stage with "Write Method" as
  "Upsert" and "Upsert Mode" as "User-defined Undate &
  Insert", in case the length of the value of a varchar or char
  field
  in condition of the user-define update statement is not the same
  as max-length for varchar field or length of char field, a
  warning message like "Table_name: When checking
  operator: When binding input interface field
  "source_column_name" to field "target_column_name": Implicit
  conversion from source type "string[max=nn]" to result type
  "string
  [max=mm]": Possible truncation of variable length string." is
  given, even the field in db2 table is defined correctly. If the
  target table is empty, the record of that varchar
  or char field is truncated to length of mm.
  e119499 - DB2 EE Write fails to insert REAL data
  e112194 - DB2EE is padding varchar datatype with
  APT_STRING_PADCHAR set
  e116012 - Sparse lookup does not support type Vargraphic or CLOB
  
  
  APARS
  --------
  JR29415 -  SQL Codes not shown in reject log during upsert
  operation of DB2 Enterprise stage.
  JR33178 - DB2 ENTERPRISE Edition Stage generates resource bundle
  warning messages.
  JR30784 - CLEANUP ON FAILURE OPTION ON DB2 ENTERPRISE LOAD, NOT
  WORKING AS EXPECTED
  JR30505 - After applying the patch for APAR IZ24442_IZ29235 the
  DB2 EE Stage using LOAD TRUNCATE with 0 rows, does not execute
  the
  command.
  JR29511 - The customer gets the following error message from the
  lookup stage w/ DB2 EE stage:
  Sequential_File_42: Error when checking operator: Could not find
  input field "A".
  
  JR33486 - DB2 ENTERPRISE EDITION STAGE RECEIVE ERROR MESSAGE
  ABOUT DB2NODES.CFG
  JR32948 - DB2 ENTERPRISE STAGE ISSUE WHEN USING STAGE PROPERTIES
  USE DEFAULT SERVER = TRUE RESULTS IN JOB FAILURE
  

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

• R753 PSN

     UP