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

POSSIBLE DATABASE ABEND DURING DROP TABLE STATEMENT WHEN USING HIGH
PERFORMANCE UNLOADER ( DB2HPU )

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A database may abend during a drop table statement when db2hpu 
is being used. 
The db2diag.log will report : 
 
2009-09-29-14.45.49.862670+120 I136017A559        LEVEL: Severe 
PID     : 4371                 TID  : 105326      PROC : db2sysc 
0 
INSTANCE: db2inst1              NODE : 000         DB   : SAMPLE 
APPHDL  : 0-58083              APPID: 
12.43.240.6.56078.090911124103 
AUTHID  : db2inst1 
EDUID   : 105326               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data management, sqldDropObj, probe:415 
MESSAGE : TCB fix count != 1 when dropping data object! 
DATA #1 : Hexdump, 8 bytes 
0xC0000001A400EB60 : 0000 0000 0000 0003 
........ 
 
The problem may be alleviated when using the db2hpu lock=yes 
option as that prevents drop table statements whilst db2hpu is 
running.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 High Performance Unload users                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Dropping a table after unloading it with the DB2             * 
* HighPerformance Unload tool, can lead to an                  * 
* abnormaltermination.                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.7 Fix Pack 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
This problem was first fixed in V9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.02.2010
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList