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

OCISESSIONBEGIN FAILS WITH OCI_STMT_CACHE MODE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
OCISessionBegin() function call returns an error -1 if 
OCI_STMT_CACHE option is specified even though it works well 
with OCI_DEFAULT option as below. 
 
  rc = OCISessionBegin (svch, errh, usrh, OCI_CRED_RDBMS, 
OCI_STMT_CACHE); 
  printf ("OCISessionBegin %d\n", rc); 
  ==> 
  OCISessionBegin -1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2ci users                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fixpack 3                        * 
****************************************************************
Local Fix:
Specify OCI_DEFAULT mode on OCISessionBegin call instead of 
OCI_STMT_CACHE
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
Problem was first fixed in DB2 version 10.5 fixpack 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