IBM Support

IZ16974: DB2 CORRECT THE HANDLING FOR SWEDISH LOCALE "SV" ON SOLARIS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On the Solaris OS you can set locale values like LC_CTYPE to
    "sv" for Sweden. With DB2 V9 this can cause problems as there
    is an internal mapping conflict for "sv". The string "sv" is
    also used as the territory code for El Salvador (es_SV) so that
    the DB2 client may incorrectly map the locale to "es_Lat".
    
    This may cause DB2 to abort with error SQL1034C  "The database
    is damaged." and in db2diag.log the following is dumped:
    
    2007-11-30-14.47.40.101609+060 I1498A511          LEVEL: Error
    PID     : 20340                TID  : 133         PROC : db2sysc
    0
    INSTANCE: t126                 NODE : 000         DB   : MYDB
    APPHDL  : 0-28                 APPID: *LOCAL.t126.071130134739
    AUTHID  : T126
    EDUID   : 133                  EDUNAME: db2agent (MYDB) 0
    FUNCTION: DB2 UDB, SW- query graph, sqlnq_set_locale, probe:20
    RETCODE : ZRC=0x800F0060=-2146500512=SQLO_BADCC "Invalid
    country-code." DIA8107C Invalid country code "".
    
    2007-11-30-14.47.40.102541+060 I2010A538          LEVEL: Error
    PID     : 20340                TID  : 133         PROC : db2sysc
    0
    INSTANCE: t126                 NODE : 000         DB   : MYDB
    APPHDL  : 0-28                 APPID: *LOCAL.t126.071130134739
    AUTHID  : T126
    EDUID   : 133                  EDUNAME: db2agent (MYDB) 0
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
    logging func, probe:0
    MESSAGE : Input locale
    DATA #1 : Hexdump, 6 bytes
    0xFFFFFFFF703F28B4 : 6573 5F4C 6174                es_Lat
    

Local fix

  • use locale "sv_SE" instead of "sv"
    

Problem summary

  • sers Affected: ALL
    
    Problem Description:
    
    On the Solaris OS you can set locale values like LC_CTYPE to
    "sv" for Sweden. With DB2 V9 this can cause problems as there
    is an internal mapping conflict for "sv". The string "sv" is
    also used as the territory code for El Salvador (es_SV) so that
    the DB2 client may incorrectly map the locale to "es_Lat".
    
    This may cause DB2 to abort with error SQL1034C  "The database
    is damaged." and in db2diag.log the following is dumped:
    
    2007-11-30-14.47.40.101609+060 I1498A511          LEVEL: Error
    PID     : 20340                TID  : 133         PROC : db2sysc
    0
    INSTANCE: t126                 NODE : 000         DB   : MYDB
    APPHDL  : 0-28                 APPID: *LOCAL.t126.071130134739
    AUTHID  : T126
    EDUID   : 133                  EDUNAME: db2agent (MYDB) 0
    FUNCTION: DB2 UDB, SW- query graph, sqlnq_set_locale, probe:20
    RETCODE : ZRC=0x800F0060=-2146500512=SQLO_BADCC "Invalid
    country-code." DIA8107C Invalid country code "".
    
    2007-11-30-14.47.40.102541+060 I2010A538          LEVEL: Error
    PID     : 20340                TID  : 133         PROC : db2sysc
    0
    INSTANCE: t126                 NODE : 000         DB   : MYDB
    APPHDL  : 0-28                 APPID: *LOCAL.t126.071130134739
    AUTHID  : T126
    EDUID   : 133                  EDUNAME: db2agent (MYDB) 0
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
    logging func, probe:0
    MESSAGE : Input locale
    DATA #1 : Hexdump, 6 bytes
    0xFFFFFFFF703F28B4 : 6573 5F4C 6174                es_Lat
    
    Problem Summary:  See Problem Description.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 6 (build s081007)
    

Temporary fix

  • see LOCAL FIX.
    

Comments

APAR Information

  • APAR number

    IZ16974

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-03-05

  • Closed date

    2008-11-03

  • Last modified date

    2008-11-03

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

    IZ16595

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

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"910"}]

Document Information

Modified date:
03 October 2021