Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC61978 Status: Geschlossen

THE INSTANCE CAN CRASH BY AN ACCESS VIOLATION DURING THE INDEX ANDING
OPERATION WITH OVER 4G SHARED SORT HEAP

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 FixPack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.07.2009
24.06.2010
27.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList