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

ADDED SEAMLESS FAILOVER SUPPORT FOR INSERT CHAIN AND INSERT WITH LOB
STREAM(SQLPARAMDATA) FOR DB2 Z/OS

product:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problem description:
Scenario 1: CLI NON-Seamless failover for INSERT chain 
 
CLI driver is failing with -30108(non seamless failover) error, 
when executing SQL_ATTR_CHAINING_BEGIN as first sql in the 
transaction after the connection is successfully rerouted to 
next available member 
 
Scenario 2:CLI NON-Seamless failover for INSERT with LOB stream 
 
CLI driver is failing with -30108(non seamless failover) error, 
when executing SQLParamData()(Lob stream) as first sql in the 
transaction  after the connection is successfully rerouted to 
next available member. 
Applicable only when SQL_ATTR_INTERLEAVED_PUTDATA is enabled.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7                       * 
****************************************************************
Local Fix:
Solution
First fixed in Version 10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.07.2015
04.02.2016
04.02.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList