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

OCISESSIONBEGIN FAILS WITH OCI_STMT_CACHE MODE

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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.1 FixPack 3                        * 
****************************************************************
Local Fix:
Specify OCI_DEFAULT mode on OCISessionBegin call instead of 
OCI_STMT_CACHE
available fix packs:
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
Problem was first fixed in Version 10.1 FixPack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95293 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.05.2013
03.10.2013
03.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList