|
Problem IC64333
|
Status: Closed |
A FAILED DPF LOAD WITH STATISTICS USE PROFILE OPTION MAY CORRUPT SYSTEM CATALOG TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If you run a LOAD with STATISTICS USE PROFILE option on a DPF
system, and the LOAD fails for some reason (e.g. tablespace
full), the rollback processing may corrupt some system catalog
tables such as SYSIBM.SYSCOLDIST. Later on when other
operations access those tables, DB2 will detect the problem, the
database will be marked bad, and you will find a message like
this in db2diag.log:
2009-07-06-16.15.58.578729-240 I16140672A555 LEVEL: Severe
PID : 1171562 TID : 19609 PROC : db2sysc10
INSTANCE: svtdbm5 NODE : 010 DB : SLEEMANS
APPHDL : 5-19233 APPID: *N5.svtdbm5.090706234511
AUTHID : SVTDBM5
EDUID : 19609 EDUNAME: db2agntp (SLEEMANS) 10
FUNCTION: DB2 UDB, data management, sqldDataFetch, probe:4465
MESSAGE : Row not found on data fetch from index!
DATA #1 : Hexdump, 8 bytes
0x0700000010387558 : 0000 5C89 0000 0011 ..\..... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users running LOAD with STATISTICS USE PROFILE on DPF *
* system *
****************************************************************
* PROBLEM DESCRIPTION: *
* If you run a LOAD with STATISTICS USE PROFILE option on a *
* DPF *
* system, and the LOAD fails for some reason (e.g. tablespace *
* *
* full), the rollback processing may corrupt some system *
* catalog *
* tables such as SYSIBM.SYSCOLDIST. Later on when other *
* *
* operations access those tables, DB2 will detect the problem, *
* thedatabase will be marked bad, and you will find a message *
* like *
* this in db2diag.log: *
* *
* 2009-07-06-16.15.58.578729-240 I16140672A555 LEVEL: Severe *
* *
* PID : 1171562 TID : 19609 PROC : db2sysc10 *
* INSTANCE: svtdbm5 NODE : 010 DB : SLEEMANS *
* APPHDL : 5-19233 APPID: *N5.svtdbm5.090706234511 *
* AUTHID : SVTDBM5 *
* EDUID : 19609 EDUNAME: db2agntp (SLEEMANS) 10 *
* FUNCTION: DB2 UDB, data management, sqldDataFetch, *
* probe:4465 *
* MESSAGE : Row not found on data fetch from index! *
* DATA #1 : Hexdump, 8 bytes *
* 0x0700000010387558 : 0000 5C89 0000 0011 ..\..... *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
do not use STATISTICS USE PROFILE option when running LOAD;
perform RUNSTATS after LOAD instead |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1. At a
minimum, this fix should be applied on the server. |
| Workaround |
see LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.11.2009
15.01.2010
15.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
