DB2 - Problem description
Problem IC61978 | Status: Closed |
THE INSTANCE CAN CRASH BY AN ACCESS VIOLATION DURING THE INDEX ANDING OPERATION WITH OVER 4G SHARED SORT HEAP | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On systems with more then 4GB availabe SortHeap instance can trap with this stack: sqlriBFSetBuildFilter sqlri_BFBandP sqliScanLeaf2NoLocking or sqliScanLeaf2 sqlifnxt sqlirdk sqldIndexFetch sqldRowFetch | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * database configured with over 4G-byte shared sort heap * **************************************************************** * PROBLEM DESCRIPTION: * * The access violation exception or SIGSEGV signal trap * * canbemade during the index anding operation with * * over4G-byteshared sort heap.This can be made because the * * indexanding buffer sizemismatches with the allocated * * size.Thefollowing stack is an eye-catcher of * * thisissue.sqlriBFSetBuildFiltersqlri_BFBandPsqliScanLeaf2NoLoc * sqliScanLeaf2sqlifnxtsqlirdksqldIndexFetchsqldRowFetch * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 Version 9.7 FixPack 2 * **************************************************************** | |
Local Fix: | |
The followings can be a workaround for this issue. - To make a plan which contains no index anding operators - To tune up SORTHEAP, SHEAPTHRES_SHR, SHEAPTHRES db configuration value to make less size of the shared sort heap than 4G-byte | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 FixPack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.07.2009 24.06.2010 27.07.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |