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

CRASH/TRAP/CORE IN OCISESSIONGET() WHEN A CONNECTION IS ACTIVATED FROM THE
IDLE SESSION POOL

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If program uses OCICreateSessionPool() then it might generate a 
core dump in OCISessionGet() as soon as the total number of busy 
connection is higher than the minimum specified in 
OCICreateSessionPool(). 
 
The typical stack for this is as follows: 
 
  #1  0x7f896b5c in OCISessionGet () from 
/export/home/db2inst1/sqllib/lib32/libdb2ci.so.1 
  #2  0x7f801c90 in OCI_ConnectionLogon (con=0x1c7488, 
new_pwd=0x5 <Address 0x5 out of bounds>, tag=0x0) at 
connection.c:638 
  #3  0x7f80ee54 in OCI_PoolGetConnection (pool=0x1c5288, 
tag=0x0) at pool.c:546 
  #4  0x7f942b6c in OraLogOn (oradb_ptr=0x73378, 
data=0x78ff5910, errmsg=0x7902bba0 "") at ora8.c:314 
  #5  0x7f943f08 in OradbPing (oradb_ptr=0x73378, 
errmsg=0x7902bba0 "") at ora8.c:638 
  #6  0x7f944054 in dbKeepAlive (sd=0x73378) at ora8.c:663 
  #7  0x7f72a9d0 in _lwp_start () from /lib/libc.so.1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local Fix:
No workaround, please upgrade the fixpack.
Solution
First fixed in Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.03.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList