JR30272: USER MAY OBSERVE INCORRECT SCAN RESULT WHEN QUERYING GRAPHIC TYPE COLUMNS

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Index Manager fails to properly initialize a structure that
  containing codepage member passed to the graphic keypart
  comparison routines. As a result trailing blanks in graphic
  strings are not treated as proper codepage data. This results in
  incorrect comparison which in turn causes incorrect index scan
  result. The query ends up not returning the rows containing the
  trailing blanks even tough they satisfy the query conditions.
  This only happens when the IDENTITY collating sequence is used.
  

Local fix

• Change the IDENTITY collating sequence to the others
  

Problem summary

• ERROR DESCRIPTION:
  Index Manager fails to properly initialize a structure that
  containing codepage member passed to the graphic keypart
  comparison routines. As a result trailing blanks in graphic
  strings are not treated as proper codepage data. This results in
  incorrect comparison which in turn causes incorrect index scan
  result. The query ends up not returning the rows containing the
  trailing blanks even tough they satisfy the query conditions.
  This only happens when the IDENTITY collating sequence is used.
  
  LOCAL FIX:
  Change the IDENTITY collating sequence to the others
  
  Users affected:
  Users who set IDENTITY collating sequence
  

Problem conclusion

• Problem was first fixed in DB2 UDB Version 9.5 Fix Pak 3
  

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:

  IC65192

Fix information

• Fixed component name

  DB2 UDB EXE WIN

• Fixed component ID

  5724E4901

Applicable component levels

• R950 PSY

     UP