|
Problem IC67014
|
Status: Geschlossen |
A REDISTRIBUTE CONTINUE/ABORT OPERATION ON COMPRESSED TABLES MIGHT CORRUPT DISK PAGES OR BUFFERPOOL MEMORY |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
This is a problem that can only occur during a REDISTRIBUTE
CONTINUE/ABORT operation on compressed tables where the
dictionary is not created by REORG utility. During the recovery
part of an operation an internal free space control record
(FSCR) can be errornously deleted, causing later updates to the
FSCR to write invalid date to other parts of different pages in
memory. The pages with the invalid data might be written to the
disk or redistribute might fail with a db2diag.log error similar
to:
2010-02-13-03.07.51.812113-300 I20989616A448 LEVEL: Severe
PID : 336288 TID : 7717 PROC : db2sysc
17
INSTANCE: fepinstp NODE : 017 DB : TESTDB
APPHDL : 0-99 APPID: *N0.fepinstp.100213051502
AUTHID : FEPINSTP
EDUID : 7717 EDUNAME: db2rcont 17
FUNCTION: DB2 UDB, data protection services, sqlpflog, probe:50
MESSAGE : Error -2028994531, reqlsn 0000BC1FBC1FBC1F
2010-02-13-03.07.51.814102-300 I20990065A543 LEVEL: Error
PID : 336288 TID : 7717 PROC : db2sysc
17
INSTANCE: fepinstp NODE : 017 DB : TESTDB
APPHDL : 0-99 APPID: *N0.fepinstp.100213051502
AUTHID : FEPINSTP
EDUID : 7717 EDUNAME: db2rcont 17
FUNCTION: DB2 UDB, buffer pool services,
sqlbSplatProcessDStacks, probe:13
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
DIA8526C A fatal error occurred in data protection
services |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Any user running DB2 v9.5 FP5 or lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* This is a problem that can only occur during a REDISTRIBUTE *
* CONTINUE/ABORT operation on compressed tables where the *
* dictionary is not created by REORG utility. db2daig.log will *
* show errors similar to: *
* *
* 2010-02-13-03.07.51.812113-300 I20989616A448 LEVEL: *
* Severe *
* PID : 336288 TID : 7717 PROC : *
* db2sysc *
* 17 *
* *
* INSTANCE: fepinstp NODE : 017 DB : TESTDB *
* APPHDL : 0-99 APPID: *
* *N0.fepinstp.100213051502 *
* AUTHID : FEPINSTP *
* *
* EDUID : 7717 EDUNAME: db2rcont 17 *
* FUNCTION: DB2 UDB, data protection services, sqlpflog, *
* probe:50 *
* MESSAGE : Error -2028994531, reqlsn 0000BC1FBC1FBC1F *
****************************************************************
* RECOMMENDATION: *
* Customer should upgrade to DB2 v9.5 FP6 or higher *
**************************************************************** |
| Local-Fix: |
Workaround
There are two workarounds:
1) The issue only occurs during the recovery part of
REDISTRIBUTE performed during a REDISTRIBUTE CONTINUE or
REDISTRIBUTE ABORT operation. If the REDISTRIBUTE operation
fails and the user suspects they might be susceptible to this
problem, they can restore their database to a backup taken prior
to the redistribute operation.
2) Prior to beginning the original redistribute operation, use
the following select statement to identify tables whose
dictionary was not created by REORG utility:
select tabschema, tabname from SYSIBMADM.ADMINTABCOMPRESSINFO
where tabschema not in ('SYSIBM','SYSTOOLS') and dict_builder
not in ('REORG','NOT BUILT')
Then run offline REORG to re-create the dictionary. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.03.2010
12.07.2010
12.07.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
