|
Problem IC65650
|
Status: Closed |
LOAD INTO A TABLE WITH COMPRESSION ENABLED BUT NO DICTIONARY CAN CRASH WITH MEMORY CORRUPTION ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the Load utility is invoked into a table that is
compression enabled, but
no dictionary exists yet, the utility will execute Automatic
Dictionary Creation logic.
A flaw in this logic may cause the Load to crash with a memory
corruption error.
A db2diag.log error from the db2ltsc EDU, in function
sqloDiagnoseFreeBlockFailure
is a signature of this problem.
2009-11-20-08.05.21.048714-300 E112615E946 LEVEL:
Critical
PID : 1234 TID : 46913982294336PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
MYDB
APPHDL : 0-99 APPID:
*N0.regress9.091120130422
AUTHID : DB2INST1
EDUID : 429 EDUNAME: db2ltsc 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic".
The instance may have been shutdown as a result.
"Automatic" FODC
(First Occurrence Data Capture) has been invoked
and diagnostic
information has been recorded in directory
"/home/db2inst1/sqllib/db2dump/FODC_Panic_2009-11-20-08.05.21.04
8539/
". Please look in this directory for detailed
evidence about what
happened and contact IBM support if necessary to
diagnose the
problem. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* LOAD INTO A TABLE WITH COMPRESSION ENABLED BUT NO *
* DICTIONARYCANCRASH WITH MEMORY CORRUPTION ERROR *
****************************************************************
* RECOMMENDATION: *
* Upgrade to FixPak 2 or later *
**************************************************************** |
| Local Fix: |
Avoid the Load ADC(Automatic Dictionary Creation) by manually
creating compression
dictionary for the table using REORG or INSPECT if possible. |
| available fix packs: |
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
|
| Solution |
First fixed in V9.7 FixPak 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.01.2010
10.06.2010
24.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
