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

DATABASE WAS MARKED BAD THE FOLLOWING STEP, IF THE CLIENT SEND BAD BUFFER.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DATABASE was MARKED BAD the following step, if the client send 
bad buffer. 
 
From db2diag.log 
2009-11-07-09.27.17.114687+540 I11711164A443      LEVEL: Severe 
PID     : 1232938              TID  : 1           PROC : 
db2agent (XXXX) 0 
INSTANCE: db2inst1                 NODE : 000         DB   : 
XXXX 
APPHDL  : 0-1605               APPID: 
XXX.XXX.XXX.XXX.5380.091106234124 
AUTHID  : XXXX 
FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45 
DATA #2 : Hexdump, 4 bytes 
0x0FFFFFFFFFFEEF88 : 8736 0009 
.6.. 
 
2009-11-07-09.27.17.162175+540 I11711608A439      LEVEL: Severe 
PID     : 1232938              TID  : 1           PROC : 
db2agent (XXXX) 0 
INSTANCE: db2inst1                 NODE : 000         DB   : 
XXXX 
APPHDL  : 0-1605               APPID: 
XXX.XXX.XXX.XXX.5380.091106234124 
AUTHID  : XXXX 
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler, 
probe:50 
MESSAGE : DIA0505I Execution of a component signal handling 
function has begun. 
 
... snip ... 
 
2009-11-07-09.27.17.213713+540 I11730442A485      LEVEL: Severe 
PID     : 1232938              TID  : 1           PROC : 
db2agent (XXXX) 0 
INSTANCE: db2inst1                 NODE : 000         DB   : 
XXXX 
APPHDL  : 0-1605               APPID: 
XXX.XXX.XXX.XXX.5380.091106234124 
AUTHID  : XXXX 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20 
RETCODE : ZRC=0x87360009=-2026504183=SQLJC_ERROR_BEOF "DATA DOES 
NOT EXIST" 
          DIA8506C Unexpected end of file was reached. 
 
... snip ... 
 
2009-11-07-09.27.17.214189+540 I11730928A769      LEVEL: Severe 
PID     : 1232938              TID  : 1           PROC : 
db2agent (XXXX) 0 
INSTANCE: db2inst1                 NODE : 000         DB   : 
XXXX 
APPHDL  : 0-1605               APPID: 
XXX.XXX.XXX.XXX.5380.091106234124 
AUTHID  : XXXX 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 1 
 sqlerrmc: 9 
 sqlerrp : SQLRI1EC 
 sqlerrd : (1) 0x87360009      (2) 0x00000009      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFE0C      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2009-11-07-09.27.17.304362+540 E11786942A394      LEVEL: Severe 
PID     : 1232938              TID  : 1           PROC : 
db2agent (XXXX) 0 
INSTANCE: db2inst1                 NODE : 000         DB   : 
XXXX 
APPHDL  : 0-1605               APPID: 
XXX.XXX.XXX.XXX.5380.091106234124 
AUTHID  : XXXX 
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10 
MESSAGE : ADM7518C  "XXXX    " marked bad.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Server may trap.                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See the APAR description.                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 2.                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 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 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.12.2009
14.05.2010
14.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList