|
Problem IC82972
|
Status: Closed |
XA AES CONNECTION TO DB2 Z/OS SERVER GETS SQL30082N RC=17 |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
XA connection against DB2 z/os v9.1 CM
mode server with Advanced Encrpytion (AES) fail with.
SQL30082N rc=17. The issue can happen when client forces
reconnect through Syncpoint manager ( SPM).
Impacted release:v9.7.4,v9.7.5,v9.7.6 DB2 Connect Server |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Version 9.7 Fix pack 4 users *
****************************************************************
* PROBLEM DESCRIPTION: *
* On DB2 v9.7 FP5 making XA connection against DB2 z/os v9.1 *
* CM mode server with Advanced Encryption (AES) fail with *
* SQL30082N rc=17. This same XA connection works fine before *
* upgrading to v9.7 FP5. *
* *
* For XA connection, DB2 client forces reconnect to force spm *
* connection on gateway and it reuses the security manager *
* level that was returned by DB2 z/os v9.1 server. *
* *
* When security manager level returned by server is lower than *
* 9, then user will hit this problem. If the server has *
* security manager level 9 or higher, then it'll avoid this *
* problem. But note that DB2 z/os v9.1 server with security *
* manager level 9 or lower is supported with AES connection. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix pack 7 *
**************************************************************** |
| Local Fix: |
catalogging tcpip loop back or setting registry variable
DB2CONNECT_IN_APP_PROCESS=NO (then restart instance) |
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.7 Fix pack 7 |
| Workaround |
catalogging tcpip loop back or setting registry variable
DB2CONNECT_IN_APP_PROCESS=NO (then restart instance) |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC87891
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.04.2012
20.11.2012
20.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
