Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC74434 Status: Closed

CONNECT REQUEST CAN GET AUTHORIZATION FAILURE GOING THROUGH DB2 CONNECT
SERVER

product:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problem description:
If connection pooling is enabled DB2 Connect Server (aka 
gateway), connect request to database can receive authentication 
error even though correct credentials are provided. The error is 
reported if application uses authentication type server_encrypt 
( using AES encryption) or Kerberos. The error happens when DB2 
Connect Server tries to recover from stale TCP/IP connection. 
 
As an example, you can get the following error if your JCC 
application is using AES encyption : 
"Connection authorization failure occurred.  Reason: Encryption 
Algorithm is not supported. ERRORCODE=-4214" 
or 
"Unable to authentication because of system error" if you are 
using Kerberos authentication.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CONNECT REQUEST CAN GET AUTHORIZATION FAILURE GOING THROUGH  * 
* DB2                                                          * 
* CONNECT SERVER                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The connect request fails because DB2 Connect server sends   * 
*                                                              * 
* incorrect encryption type to recover from connection loss if * 
* AES                                                          * 
* encryption is used.                                          * 
*                                                              * 
* For authentication type Kerberos, DB2 connect gateway was    * 
*                                                              * 
*                                                              * 
*                                                              * 
* incorrectly reporting the error.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in fix pack 8 of v9.5                            * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in fix pack 8 of v9.5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC75231 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2011
13.07.2011
13.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.,
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.