Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2003
    Posts
    1,605

    Unanswered: Severe error in db2diag - how to debug what is cause of it?

    In "DB2/Linux 10.1 fixpack 1 Enterprise Server Edition" in db2diag.log I see bellow error every few minutes. Both "Severe" errors appear one after another.
    How to debug what this error is and what is cause of it?


    Code:
    2016-05-10-16.21.32.034468+120 I577563505A663       LEVEL: Severe
    PID     : 14389                TID : 4383643265296  PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   : ISQ
    APPHDL  : 0-31154              APPID: *LOCAL.db2inst1.160513072121
    AUTHID  : DB2INST1             HOSTNAME: pdb2v10
    EDUID   : 498                  EDUNAME: db2agent (ISQ) 0
    FUNCTION: DB2 UDB, base sys utilities, sqeApplication::SetupCodePageInfo, probe:200
    RETCODE : ZRC=0x800F005B=-2146500517=SQLO_NOTABLE "No conversion table exists"
              DIA8102C Conversion table not loaded. Source code page "819", Target
              code page "912", method "", handle "".
    
    2016-05-10-16.21.32.034700+120 I577564169A546       LEVEL: Severe
    PID     : 14389                TID : 4383643265296  PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   : ISQ
    APPHDL  : 0-31154              APPID: *LOCAL.db2inst1.160513072121
    AUTHID  : DB2INST1             HOSTNAME: pdb2v10
    EDUID   : 498                  EDUNAME: db2agent (ISQ) 0
    FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppStartUsing, probe:20
    DATA #1 : Hexdump, 4 bytes
    0x000003FCA57FBF50 : FFFF FEB4

  2. #2
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Supported territory codes and code pages
    db2inst1 user has a locale with 819 code page (S-1 group) while your database ISQ has code page 912 (S-2 group).
    There is no code page conversion between these 2 code pages.

    You should set some locale with compatible code page in an appropriate login script for the db2inst1 user (see Table 14).
    Or just export the DB2CODEPAGE env variable in the application session/login script like this:
    export DB2CODEPAGE=912
    Regards,
    Mark.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •