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

CRASH RECOVERY OR ROLL FORWARD OPERATION MIGHT FAIL WHEN CERTAIN LOG
RECORDS ARE REPLAYED ON A TABLE WITH COMPRESSION ENABLED

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During a crash recovery or roll forward operation, a table with 
compression enabled for both relational and XML data might 
become corrupted when a log record is replayed against that 
table as the result of a TRUNCATE TABLE or LOAD REPLACE command. 
The compression dictionary might be damaged and as a result, the 
table data might become inaccessible. If this happens, during 
the crash recovery operation you might see the connection to the 
server failing with SQL1042C error message. 
 
"db2 => CONNECT TO XMLDB 
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004" 
 
and You might also see a message similar to the following one in 
the db2diag log file: 
 
2011-03-23-08.46.38.358819-240 E13646500A485      LEVEL: Error 
PID     : 17703                TID  : 8           PROC : db2sysc 
INSTANCE: sample          NODE : 000         DB   : XMLDB 
APPHDL  : 0-7                  APPID: 
*LOCAL.regress3.110323124629 
AUTHID  : DBUSER 
EDUID   : 8                    EDUNAME: db2agent (XMLDB) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::RecoverDatabase, probe:60 
MESSAGE : ADM1532E  Crash recovery has failed with SQLCODE 
"-1042".
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of table compression                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the most recent fix pack.                         * 
****************************************************************
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
Problem is first fixed in DB2 UDB version 9.7 fix pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.04.2012
06.06.2012
06.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList