home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC98734 Status: Geschlossen

ON A COLUMN-ORGANIZED TABLE, QUERIES RUNNING AT THE SAME TIME AS REORG
RECLAIM EXTENTS MAY FAIL WITH SQL0901N

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
On a column-organized table, a query running at the same time 
as a REORG TABLE ... RECLAIM EXTENTS may occasionally 
fail with an SQLCODE SQL0901N complaining of a failed 
assertion and an FODC AppErr. 
 
In 10.5 GA, the assertion text in the diagnostic log will be of 
a form similar to: 
 
AssertionFailedException: An assertion 'pageEndTSN >= 
mCurrentTSN' failed. Additional info: skipTillEndOfPage 
is called to move backwards: 
pageEndTSN: 144115188075859982 
mCurrentTSN: 144115188075859983 
TSNList.mStartTSN: 144115188075859981 
TSNList.mEndTSN: 144115188075892749 
Table name: TABLE16 
Page header: 
--- Begin dump of Page object at 0x0a00030006690030 --- 
mCdePageType:              2 
mCdePageFormatVersion:     1 
mColGroupNumber:           1 
mTupletCount:              4111 
mStartTSN:                 144115188075855872 
(0x0200000000000000) 
mPageAttributes:           0 
mRegionCount:              2 
mTotalDictSize:            0 
mTupleMapOffset:           15600 
mVariableLengthBankOffset: 0 
--- End dump of Page object at 0x0a00030006690030 ----- 
Thrown at TSNList.cpp : 288 
 
In DB2 10.5 FP1 through DB2 10.5 FP3, the assertion text in the 
diagnostic log will be of a form similar to: 
 
AssertionFailedException: An assertion 
'(InsertRange::isUnspecifiedHWM(mRangeIndex, 
mInsertRangeCachedHWMs[ mRangeIndex ]) == true || 
mCurrentStartTSN <= mInsertRangeCachedHWMs[ mRangeIndex ])' 
failed. Additional info: 
CurrentStartTSN greater than CachedHWM. 
mCurrentStartTSN: 144115188075856241 
mRangeIndex: 1 
mInsertRangeCachedHWMs[ mRangeIndex ]: 144115188075856219 
Table: TABLE16 
Thrown at TSNRangeIterator.cpp : 292 
 
The assertion thrown in the DB2 10.5 GA level is more generic 
and could potentially indicate some other problem.  The 
assertion 
thrown in DB2 10.5 FP1 through DB2 10.5 FP3 is more specific to 
this problem scenario. 
 
An example of the error message returned to a command line 
processor session in DB2 10.5 FP1 through DB2 10.5 FP3: 
 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason "unexpected error at 
TSNRangeIterator.cpp:292".) 
SQLSTATE=58004
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 for Linux, UNIX, and Windows version 10.5.0.4 * 
****************************************************************
Local-Fix:
The problem occurs rarely and has no permanent effect on the 
database.  Until a fix is available, the workaround is to retry 
the failing query.  The problem may be avoided by not running 
queries concurrently with REORG TABLE ... RECLAIM EXTENTS 
operations.
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in DB2 for Linux, UNIX, and Windows 
version 10.5 fix pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.01.2014
06.02.2014
06.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList