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

THE -332 ERROR CAUSES MANY MESSAGES IN DB2DIAG.LOG AND GENERATES A DUMP
FILE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When customer uses a third party JDBC driver called DataDirect 
to access a database and it is not using Latin-1 codepage:1252, 
the "codepage conversion error" messages are logged in 
db2diag.log and a dump file is generated for each connection. 
This causes customer's disk consumption problem. 
 
Error messages and dumps: 
 
2010-09-29-16.55.13.075984+540 I14746A602         LEVEL: Severe 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (B) 0 
 
FUNCTION: DB2 UDB, base sys utilities, 
sqeApplication::SetupCodePageInfo, probe:200 
RETCODE : ZRC=0x800F005B=-2146500517=SQLO_NOTABLE "No conversion 
table exists". DIA8102C Conversion table not loaded. Source code 
page "", Target code page "", method "", handle "". 
 
 
2010-09-29-16.55.13.076432+540 I15349A502         LEVEL: Warning 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (B) 0 
 
FUNCTION: DB2 UDB, base sys utilities, 
sqeApplication::SetupCodePageInfo, probe:200 
MESSAGE : Conversion table not available. Source code page = 
1252, Target code page = 897. 
 
2010-09-29-16.55.13.076751+540 I15852A491         LEVEL: Severe 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (B) 0 
 
FUNCTION: DB2 UDB, base sys utilities, 
sqeApplication::AppStartUsing, probe:20 
DATA #1 : Hexdump, 4 bytes 
0x0700000005BE0F30 : FFFF FEB4 
.... 
 
2010-09-29-16.55.13.774695+540 E16344A448         LEVEL: Event 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (idle) 0 
 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::TermDbConnect, probe:2000 
STOP    : DATABASE: B        : DEACTIVATED: NO 
 
2010-09-29-16.55.13.775432+540 E16793A784         LEVEL: Error 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (idle) 0 
 
FUNCTION: DB2 UDB, DRDA Application Server, 
sqljsPostProcessingConnectAttach, probe:649 
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected. 
The diagnostic data returned is (SRVDGN): "FUNCTION ID = 0012 , 
PROBE POINT = 0649 , TRACE POINT = 0150 , SUBCODE1 = 
FFFFFFFF8005006D, 
SUBCODE2 = FFFFFFFFFFFFFEB4, SUBCODE3 = 0000000000000000, ERROR 
MSG = 
SQLAM: CONNECT failed. CCSID specified on ACCRDB not supported". 
 
 
2010-09-29-16.55.13.775897+540 I17578A470         LEVEL: Error 
PID     : 9502764              TID  : 10909       PROC : db2sysc 
0 
INSTANCE: db97fp2              NODE : 000         DB   : B 
APPHDL  : 0-35488              APPID: 
AUTHID  : DB97FP2 
EDUID   : 10909                EDUNAME: db2agent (idle) 0 
 
FUNCTION: DB2 UDB, DRDA Application Server, 
sqljsPostProcessingConnectAttach, probe:150 
MESSAGE : ZRC=0x804B0095=-2142568299=SQLJS_VALNSP "VALUE ERROR" 
 
2010-09-29-16.55.13.776241+540 I18049A187         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** DRDA ASCB **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.787703+540 I18237A192         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** DRDA CMNMGR CB **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.788016+540 I18430A189         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** DSS SEGMENT **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.788292+540 I18620A192         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** RECEIVE BUFFER **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.788563+540 I18813A190         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** SEND BUFFERS **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.788917+540 I19004A195         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** CONNECTION HANDLE 
**** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.789255+540 I19200A193         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** DRDA ATTRIBUTES **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin 
 
2010-09-29-16.55.13.789598+540 I19394A192         LEVEL: Error 
PID:9502764 TID:10909 NODE:000 Title: **** AS UCINTERFACE **** 
Dump 
File:/home/db97fp2/sqllib/db2dump/9502764.10909.000.dump.bin
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DataDirect JDBC Driver Users                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When customer uses a third party JDBC driver called          * 
* DataDirect to access a database and it is not using Latin-1  * 
* codepage:1252, the "codepage conversion error" messages are  * 
* logged in db2diag.log and a dump file is generated for each  * 
* connection.                                                  * 
* This causes customer's disk consumption problem.             * 
*                                                              * 
* You can see the following error messages and code in         * 
* db2diag.log:                                                 * 
*                                                              * 
* FUNCTION: DB2 UDB, base sys utilities,                       * 
* sqeApplication::SetupCodePageInfo, probe:200                 * 
* RETCODE : ZRC=0x800F005B=-2146500517=SQLO_NOTABLE "No        * 
* conversion table exists".                                    * 
* DIA8102C Conversion table not loaded. Source codepage "",    * 
* Target code page "", method "", handle "".                   * 
*                                                              * 
*                                                              * 
* FUNCTION: DB2 UDB, base sys utilities,                       * 
* sqeApplication::SetupCodePageInfo, probe:200                 * 
* MESSAGE : Conversion table not available. Source code page = * 
* 1252, Target code page = 897.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 4                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 4
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC72519 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.11.2010
13.05.2011
13.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList