home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87695 Status: Closed

INSTANCE TRAP IN SQLVPUTD WHEN RUNNING SQL WITH CHAR(DATE())

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If an sql statement is invoked from a client that has a 
different country code than the server, and if this sql 
statement features a date to character conversion, then there is 
a chance that it may cause a crash/trap as noted in the 
following stack traceback:Database server crash with trap file: 
 
 
sqlvputd + 0x0383  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
 0x00007F0FE2648A83 : 8B04F08D78FF83FF 
</POFDisassembly> 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00007F0FE003A65A 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x020a 
  (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F0FE003A3EB ossDumpStackTraceV98 + 0x002b 
  (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F0FE0035313 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x0103 
  (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F0FE383D2C7 sqlo_trce + 0x0407 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE3886957 sqloEDUCodeTrapHandler + 0x0277 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE79FA4A0 address: 0x00007F0FE79FA4A0 ; dladdress: 
0x00007F0FE79EB000 ; offset in lib: 0x000000000000F4A0 ; 
  (/lib64/libpthread.so.0) 
0x00007F0FE2648A83 sqlvputd + 0x0383 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE3CCD6E3 _Z15sqlrichar2_dateP8sqlrr_cb + 0x0093 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE23E8A0D _Z8sqlrisetP8sqlrr_cb + 0x01dd 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE46FC0CD _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x01ad 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE22BB995 
_Z27sqlrr_process_fetch_requestP14db2UCinterface + 0x01b5 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE22B7262 
_Z10sqlrr_openP14db2UCinterfaceP15db2UCCursorInfo + 0x0632 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE198234E 
_Z16sqljs_ddm_opnqryP14db2UCinterfaceP13sqljDDMObject + 0x040e 
  (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F0FE4596856 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x0376
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix pack 2                       * 
****************************************************************
Local Fix:
Change client machine country code to be the same as database on 
server
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix pack 2
Workaround
Change client machine country code to be the same as database on 
server
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.10.2012
10.01.2013
10.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList