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

SUPPORT THE COMBINATION OF SERVER ON CLIENT AND SERVER_ENCRYPT ON GATEWAY.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The combination of SERVER on client and SERVER_ENCRYPT on 
gateway was supported before V9.1 Fix Pack 9. This APAR adds a 
 
registry variable called "DB2_CONNECT_GWY_AUTH_SUPP", which 
allows to revert to old behavior. 
The fix is a temporary solution to give customer time to correct 
their business model to use the matching authentication type 
between clients and gateway and the gateway to server.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.7 FP 2 or below are affected                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The error SQL30082 RC=17 gets returned if client             * 
* applications require different authentication types to       * 
* connect to a database server, and are not allowed to change  * 
* the authentication, but only the DB2 Gateway is allowed to   * 
* change the type.                                             * 
* DB2 V8 and V9.1 releases had the DB2_CONNECT_GWY_AUTH_SUPP   * 
* db2 registry keyword available.                              * 
* However, V9.5 Fix Pack 5 or below, and V9.7 Fix Pack 2 or    * 
* below did not include it anymore.                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 3 or above.                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Download DB2 V9.7 Fix Pack 3 or above.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2010
11.11.2010
11.11.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList