DB2 FOR LUW / DB2FORLUW / 970 - DB2

An application making a connection to a DB2 v9.7 FP2 server can 
fail with the following exception: 
 
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected. 
The diagnostic data returned is (SRVDGN):  "FUNCTION ID = 0365 , 
PROBE POINT = 0429 , TRACE POINT = 0010 , SUBCODE1 = 
FFFFFFFF804B0085, SUBCODE2 = 0000000000000000, SUBCODE3 = 
0000000000000000, ERROR MSG = Parser:  UNICODEMGR and CCSIDMGR 
should be mutually exclusive". 
 
 
The problem occurs when using a 'gateway' connection on the 
server.   This can happen if there are two gateways, or if the 
gateway is making a loop back connection to the server, or it 
can happen if the database server is using the Data Partitioning 
Feature (DPF) and the application connects to a non-catalog 
partition. 
 
The problem would also only occur if the client is running at 
v9.1 or v9.5. 
 
 
A symptom of the problem is an application running both CLI and 
administrative API calls like db2CfgGet would fail with a 
CLI0106E - "Connection is Closed" error.   The underlying 
problem is that a call to db2CfgGet would fail with an SQL1224N 
error (due to the DRDA mismatch exception) and CLI would reset 
the connection handle, causing any CLI API that uses the 
connection handle to fail with a CLI0106E error.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An application making a connection to a DB2 v9.7 FP2         * 
* servercan fail with the following exception:."MESSAGE :      * 
* DIA5000C A DRDA AS token "RECOVERABLE" wasdetected.The       * 
* diagnostic data returned is (SRVDGN): "FUNCTION ID =0365,    * 
* PROBE POINT = 0429 , TRACE POINT = 0010 ,                    * 
* SUBCODE1=FFFFFFFF804B0085, SUBCODE2 = 0000000000000000,      * 
* SUBCODE3=0000000000000000, ERROR MSG = Parser: UNICODEMGR    * 
* andCCSIDMGR should be mutually exclusive.".The problem       * 
* occurs when using a 'gateway' connection on theserver.  This * 
* can happen if there are two gateways, or ifthe gateway is    * 
* making a loop back connection to the server,or it can happen * 
* if the database server is using the DataPartitioning Feature * 
* (DPF) and the application connects to anon-catalog           * 
* partition..The problem would also only occur if the client   * 
* is runningat v9.1 or v9.5..A symptom of the problem is an    * 
* application running both CLIand administrative API calls     * 
* like db2CfgGet would fail witha CLI0106E - "Connection is    * 
* Closed" error.  The underlyingproblem is that a call to      * 
* db2CfgGet would fail with anSQL1224N error (due to the DRDA  * 
* mismatch exception) and CLIwould reset the connection        * 
* handle, causing any CLI API thatuses the connection handle   * 
* to fail with a CLI0106E error.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7, Fixpak 3                                * 
****************************************************************

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 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
 

First fixed in DB2 UDB Version 9.7, Fixpak 3

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC69888 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

12.07.2010
07.10.2010
16.08.2011

9.7.