JR34813: JAPANESE CHARACTERS IN GRAPHIC DATA TYPE ARE GARBLE WHEN GETTING THEM FROM DB2 EE STAGE.

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• [Summary]
  Japanese characters in GRAPHIC data type are garble when getting
  them from DB2 EE stage.
  
  [Detail]
  Customer's environment is
  - Default locale of the customer's AIX box is SJIS.
  - DB2's database for this is SJIS.
  - NLS map of stages in a reproducible job is
  SJIS(ASCL_SHIFT-JIS).
  
  He made a parallel job like 'DB2EE --> Copy --> Seq' and DB2EE
  stage has a varchar column and a graphic column.
  These columns in DB2's table has japanese multi-byte characters.
  
  Only data in a column of graphic data type is garble (data in a
  column of varchar data type is not garble).
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DB2 Enterprise Stage
  ****************************************************************
  PROBLEM DESCRIPTION:
  Japanese characters in GRAPHIC data type are garble when getting
  them from DB2 EE stage.
  ****************************************************************
  RECOMMENDATION:
  Determine GRAPHIC data type encodings based on the job NLS
  settings.
  ****************************************************************
  

Problem conclusion

• This is because that GRAPHIC data type were mapped to UTF-16BE
  encpdings, while it actually depends on CLIENT side encodings.
  

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

• PXDB2
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSN

     UP