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 IC95226 Status: Closed

COMPILED ROUTINE CAN CAUSE INSTANCE TRAP IN SQLRXCON_SIMPLE() AFTER
UPDATE/UPGRADE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Instance trap with below stack: 
 
<POFDisassembly> 
 __intel_new_memset + 0x003e  (db2sysc 0) 
 
 0x000000000042078E : 41FFE3C200006666 
</POFDisassembly> 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00007F0AABF13D2A 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x020a 
  (/db_config/userid/sqllib/lib64/libdb2osse.so.1) 
0x00007F0AABF13ABB ossDumpStackTraceV98 + 0x002b 
  (/db_config/userid/sqllib/lib64/libdb2osse.so.1) 
0x00007F0AABF0E9E3 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x0103 
  (/db_config/userid/sqllib/lib64/libdb2osse.so.1) 
0x00007F0AAF7A7327 sqlo_trce + 0x0407 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAF7F2517 sqloEDUCodeTrapHandler + 0x0277 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x000000334C60F4A0 address: 0x000000334C60F4A0 ; dladdress: 
0x000000334C600000 ; offset in lib: 0x000000000000F4A0 ; 
  (/lib64/libpthread.so.0) 
0x000000000042078E __intel_new_memset + 0x003e 
  (db2sysc 0) 
0x000000000041DA36 _intel_fast_memset.J + 0x0006 
  (db2sysc 0) 
0x00007F0AAD3D3440 _Z15sqlrxcon_simpleP8SQLRXNLSP10sqlz_valueS2_ 
+ 0x00a0 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3CC285 _ZN3PVM8copyDataEP10sqlz_valueS1_mb + 0x03d5 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3CBDBF _ZN3PVM13loadImmediateEjj + 0x00ff 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3C950C _ZN3PVM3runEv + 0x1dcc 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3D50B4 pvm_entry + 0x0224 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAE04B8DA sqloInvokeFnArgs + 0x00ba 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAE325BB5 
_Z19sqlriInvokerTrustedP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0x0785 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAE321E7C _Z18sqlriInvokeInvokerP10sqlri_ufobb + 0x0bbc 
 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAE32083B _Z9sqlricallP8sqlrr_cb + 0x012b 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AB06921BD _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x01ad 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AB06685FC _Z29sqlrr_process_execute_requestP8sqlrr_cbib 
+ 0x085c 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AB0666872 _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo 
+ 0x0262 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3C878F _ZN3PVM3runEv + 0x104f 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAD3D50B4 pvm_entry + 0x0224 
  (/db_config/userid/sqllib/lib64/libdb2e.so.1) 
0x00007F0AAE04B8DA sqloInvokeFnArgs + 0x00ba 
 
 
The problem will occur with a compiled SQL routine under the 
following circumstances: 
 
- The routine was created under Version 10.1.0 or 10.1.1, and is 
being run on 10.1.2, 10.5.0, or 10.5.1. 
 
- The routine assigns a zero-length string literal to a CHAR 
(not VARCHAR) variable; 
 
- The routine subsequently assigns a string literal of non-zero 
length to the same variable. 
 
The second assignment will cause DB2 to terminate abnormally, 
with a dump.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.5 Fix Pack 3.                       * 
****************************************************************
Local Fix:
Recreating affected routines under DB2 Version 10.5.0 
or later appears to circumvent the issue.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
This problem is fixed in DB2 Version 10.5 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList