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

FEDERATED SERVER OPTION CONCURRENT_ACCESS_RESOLUTION='W' CAUSES CLI019E
INVALID ATTRIBUTE ERRORS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The Federated Server option CONCURRENT_ACCESS_RESOLUTION='W' is
required for Replication with DB2 (DRDA) data sources. In DB2
11.5.4 and DB2 11.5.5 this option no longer works correctly and
generates CLI019E Invalid attribute errors.

A CLI Trace will show:
SQLSetConnectAttr( hDbc=0:110,
fOption=SQL_ATTR_CONCURRENT_ACCESS_RESOLUTION,
pvParam=&00007ffe38ffae78, iStrLen=-6 )
    ---> Time elapsed - +4.876000E+005 seconds

SQLSetConnectAttr( )
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All users attempting to use Replication with Federated data  *
* sources                                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 11.5 Mod 5 Fixpack 1                          *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All users attempting to use Replication with Federated data  *
* sources                                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 11.5 Mod 5 Fixpack 1                          *
****************************************************************
Comment
Problem fixed in DB2 11.5 Mod 5 Fixpack 1
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.01.2021
25.03.2021
25.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)