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 IC69888 Status: Geschlossen

MISMATCH BETWEEN UNICODEMGR AND CCSIDMGR DRDA LEVELS

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An application making a connection to a DB2 v9.7 FP2 or DB2  * 
* v9.8 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.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8, Fixpak 4                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Lösung
First fixed in DB2 Version 9.8, Fixpak 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.07.2010
04.08.2011
04.08.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.
Problem behoben lt. FixList in der Version
9.8.0.4 FixList