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

UNICODEMGR AND CCSIDMGR CONFLICT ERROR

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 9.7 fixpack 6.                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
The problem was first fixed by V97 FP6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.08.2011
12.06.2012
12.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList