JR33405: PROBLEM WITH ORACLE STAGE EXTRACTING CHAR(1) FIELD FROM AL32UTF8 DATABASE

APAR status

• Closed as program error.

Error description

• When extracting char type with NLS= UTF8, and
  NLS_LANG=American_America.AL32UTF8, we extract extra bytes for
  the char type.  For example, if the char type is defined as 1
  char or 1 byte.  We extract 2 bytes for the 1 char, and 3 bytes
  for the 1 byte.  So when loading, the extra byte in the data
  caused the load to fail.  When we set the
  NLS_LANG=American_America.WE8ISO8859P1, it'll still extract
  extra bytes.  Also, for multiple byte characters, in order to
  extract properly, the column length needs to be increased.
  

Local fix

• Change char type to varchar type on the extract stage. Or use
  DRS OCI stage.
  
  This fix is included in 8.0.1 fix pack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  user who is using CHAR and oracle OCI 9 extract stage
  extractingfrom oracle database
  ****************************************************************
  PROBLEM DESCRIPTION:
  When user extract data with column defined as CHAR, there will
  be extra space extracted when the NLS_LANG=.AL32UTF8 and
  datastage NLS mapping set to UTF8
  ****************************************************************
  RECOMMENDATION:
  user install the patch for JR33405
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• extra space is caused by when we pass in the buffer size to do
  the string translation is wrong.  It is too long.
  

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

• OCI
  

Fix information

• Fixed component name

  WIS QUALITYSTAG

• Fixed component ID

  5724Q36QS

Applicable component levels

• R801 PSN

     UP