|
Problem IC84131
|
Status: Geschlossen |
IF A LOG FULL IS HIT BY LOAD, BLANK PAGES COULD REMAIN IN BUFFER POOL CAUSING DATABASE TO BE MARKED BAD IF REUSED BY LOAD RESTART |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
If LOAD operation hits log full situation, it can leave some
blank data pages in bufferpool after it rollback transaction.
When subsequent LOAD RESTART operation reuses them, bad data
page is encountered and database is marked as bad. The
db2diag.log can have the following message showing blank PAGE
HEADER:
2010-12-01-23.02.24.150848-300 I1136373424E540 LEVEL: Severe
PID : 24000 TID : 47390123878720PROC :
db2sysc 2
INSTANCE: panipuri NODE : 002 DB : SAMPLE
APPHDL : 1-10058 APPID:
10.184.12.205.2202.101202040221
AUTHID : DB2INST
EDUID : 67082 EDUNAME: db2linit 2
FUNCTION: DB2 UDB, data management, sqldReadTableInfo,
probe:9416
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
Page"
DIA8500C A data file error has occurred, record id is
"".
..................
2010-12-01-23.02.24.185266-300 I1136381157E631 LEVEL: Severe
PID : 24000 TID : 47390123878720PROC :
db2sysc 2
INSTANCE: panipuri NODE : 002 DB : SAMPLE
APPHDL : 1-10058 APPID:
10.184.12.205.2202.101202040221
AUTHID : DB2INST
EDUID : 67082 EDUNAME: db2linit 2
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : SQD PAGE HEADER
DATA #1 : Hexdump, 22 bytes
0x00002B16758DC030 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00002B16758DC040 : 0000 0000 0000
......
............. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1 *
**************************************************************** |
| Local-Fix: |
The page is only corrupted in bufferpool and not on disk.
Terminating all connections to the database, deactivating, and
reactivating the database should make the problem go away. |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in Version 10.1 Fix Pack 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 12.06.2012
10.12.2012
10.12.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
