DB2 - Problem description
Problem IC69888 | Status: Closed |
MISMATCH BETWEEN UNICODEMGR AND CCSIDMGR DRDA LEVELS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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: | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
Solution | |
First fixed in DB2 Version 9.8, Fixpak 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.07.2010 04.08.2011 04.08.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.8. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.4 |