DB2 - Problem description
| Problem IC78263 | Status: Closed |
UNICODEMGR AND CCSIDMGR CONFLICT ERROR | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
UNICODEMGR and CCSIDMGR conflict errors and dump files generated
frequently.
APAR applies to v9.7fp1 and above / to v9.8 servers/gateways.
The first EXCSAT with setting UNICODEMGR level 1208 succeeds.
Then client sends empty EXCSAT (no attribute data)
intermittently.
When there is neither UNICODEMGR nor CCSIDMGR information in
EXCSAT, DRDA assumes CCSIDMGR 500 as a default value.
The next EXCSAT with UNICODEMGR level 1208 gets the error
because the information of CCSIDMGR 500 is not reset.
db2diag.log shows following messages:
2011-08-09-18.37.56.160413+540 E1895A803 LEVEL: Error
PID : 11337926 TID : 86525 PROC : db2sysc 0
INSTANCE: xxxinst NODE : 000 DB : xxxDB
APPHDL : 0-9159 APPID:x.y.z.z.59917.110809093743
AUTHID : xxxUSER
EDUID : 86525 EDUNAME: db2agent (xxxDB) 0
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsValidateMangerLevels, probe:429
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".
2011-08-09-18.37.56.161069+540 I2699A537 LEVEL: Error
PID : 11337926 TID : 86525 PROC : db2sysc 0
INSTANCE: xxxinst NODE : 000 DB : xxxDB
APPHDL : 0-9159 APPID:x.y.z.z.59917.110809093743
AUTHID : xxxUSER
EDUID : 86525 EDUNAME: db2agent (xxxDB) 0
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsValidateMangerLevels, probe:10
MESSAGE : ZRC=0x804B0085=-2142568315=SQLJS_MGRLVL
"SERVER AND REQUESTER MANAGER LEVELS INCOMPATIBLE"
Empty EXCSAT can be seen in the db2 server side trace:
EXCSAT RQSDSS (ASCII)
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
0000 000AD00100010004 1041 .........A
JCC client receives -4499 error at that time.
Non-java / Db2 client receives:
SQL30020N Execution of the command or SQL statement failed
because of a syntax error in the communication data stream that
will affect the successful execution of subsequent commands and
SQL statements: Reason Code "0x124C"("020B")"". SQLSTATE=58009 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 9.7 fixpack 6. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
The problem was first fixed by V97 FP6. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.08.2011 12.06.2012 12.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|