IBM Support

IT38969: WRONG STRING COMPARISON FOR THAI NLSCHAR DATABASE COULD HAPPEN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the database created with this codepage and collation
    NLSCHAR:
    create db <dbname> USING CODESET TIS620-1 TERRITORY TH COLLATE
    USING NLSCHAR
    
    Incorrect comparison between char strings could happen.
    It can also lead to bad order.
    Indexes could be affected. Please use 'db2dart <dbname>' to
    identify any
    affected indexes.
    After this fix is installed all affected indexes need to be
    recreated.  Indexes can also be rebuilt using REORG INDEXES.
    
    Example of the problem issue:
    create table test1 (c1 char(50),c2 char(50));
    
    insert into test1 values
    (
    x'E0202020202020202020202020202020202020202020202020202020202020
    20202020202020202020202020202020202020',
    x'E0FB2020202020202020202020202020202020202020202020202020202020
    20202020202020202020202020202020202020'
    );
    insert into test1 values
    (
    x'E0FB2020202020202020202020202020202020202020202020202020202020
    20202020202020202020202020202020202020',
    x'E0202020202020202020202020202020202020202020202020202020202020
    20202020202020202020202020202020202020'
    );
    
    and one see different ordering with c1 and c2:
    
    db2 "select hex(c1) from test1 order by c1"
    
    1
    
    ----------------------------------------------------------------
    ------------------------------------
    E020202020202020202020202020202020202020202020202020202020202020
    202020202020202020202020202020202020
    E0FB202020202020202020202020202020202020202020202020202020202020
    202020202020202020202020202020202020
    
      2 record(s) selected.
    
    db2 "select hex(c2) from test1 order by c2"
    
    1
    
    ----------------------------------------------------------------
    ------------------------------------
    E0FB202020202020202020202020202020202020202020202020202020202020
    202020202020202020202020202020202020
    E020202020202020202020202020202020202020202020202020202020202020
    202020202020202020202020202020202020
    
      2 record(s) selected.
    

Local fix

  • N/A
    Please, install this fix and re-create indexes affected.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * THAI NLSCHAR DATABASE only                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description, install this fix                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to 11.1.4.7                                          *
    ****************************************************************
    

Problem conclusion

  • Upgrade to 11.1.4.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT38969

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-04

  • Closed date

    2022-04-17

  • Last modified date

    2022-04-20

  • APAR is sysrouted FROM one or more of the following:

    IT38536

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022