home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC82972 Status: Geschlossen

XA AES CONNECTION TO DB2 Z/OS SERVER GETS SQL30082N RC=17

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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)
verfügbare FixPacks:
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

Lösung
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-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC87891 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.04.2012
20.11.2012
20.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList