|
Problem IC95090
|
Status: Closed |
In rare circumstances, access to a column organized table may fail with a recurring -901 error. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In rare circumstances, access to a column organized table may
fail with a recurring -901 error.
You should see a message similar to the following in the
db2diag.log:
013-08-04-08.57.21.725233-240 I111583E3622 LEVEL: Error
PID : 20450 TID : 47646337132864 PROC :
db2sysc
INSTANCE: svtdbm2 NODE : 000 DB :
BLUDB
APPHDL : 0-483 APPID:
9.26.48.132.36148.130804130340
AUTHID : SVTDBM2 HOSTNAME: coralm225
EDUID : 228 EDUNAME: db2agntcol (BLUDB)
FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:286
DATA #1 : String, 675 bytes
AssertionFailedException: An assertion 'pageEndTSN >=
mCurrentTSN' failed. Additional info: skipTillEndOfPage is
called to move backwards:
pageEndTSN: 1441151880758558735
mCurrentTSN: 3891110078048108544
Table name: T3RI2.T346
Page header:
--- Begin dump of Page object at 1 ---
mCdePageType: 2
mCdePageFormatVersion: 1
mColGroupNumber: 1
mTupletCount: 16
mStartTSN: 1441151880758558720
(0x1400000000000000)
mPageAttributes: 0
mRegionCount: 1
mTotalDictSize: 0
mTupleMapOffset: 0
mVariableLengthBankOffset: 0
--- End dump of Page object at 1 -----
Thrown at TSNList.cpp : 286
DATA #2 : Function name in Library, 197 bytes
void
ibm_cde::types::TSNList::ConstIterator<SkipInvalidTSNs>::skipTil
lEndOfPage(ibm_cde::types::TSN, const ibm_cde::data::Page *,
const ibm_cde::data::TableAccessor *) [with SkipInvalidTSNs =
true]
DATA #3 : File name, 11 bytes
TSNList.cpp
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002B3FD13671C6
_ZN7ibm_cde8services6Tracer9traceDataENS0_11ComponentIDENS0_16Co
mmonTraceLevelENS1_10TraceEventEPKcmS6_PKvmRKSbIcSt11char_trait
+ 0x9C6
[1] 0x00002B3FD133B522
_ZNK7ibm_cde8services13BaseException14traceExceptionENS0_11Compo
nentIDEPKc + 0x202
[2] 0x00002B3FCCD61912
_ZN7ibm_cde5types7TSNList13ConstIteratorILb1EE17skipTillEndOfPag
eENS0_3TSNEPKNS_4data4PageEPKNS5_13TableAccessorE + 0x8B2
[3] 0x00002B3FCD1257DB
_ZN7ibm_cde4data23PageIteratorForTSNRangeILb0ELb0EE20readNextPag
eInternalILb0ELb0EEEPNS0_4PageEbRjRPNS0_11PageRequestERbSA_ +
0x1DB
[4] 0x00002B3FCD12468E
_ZN7ibm_cde4data23PageIteratorForTSNRangeILb0ELb0EE12readNextPag
eERj + 0x2E
[5] 0x00002B3FCDFDB834
_ZN7ibm_cde5query21LoadColValueEvaluator15processTSNRangeILNS0_3
OpTE331ENS_5types7IntegerIlLb0EEES6_EEvv + 0xBC4
[6] 0x00002B3FD182E6D1
_ZN7ibm_cde5query21LoadColValueEvaluator26processInputsSynchrono
uslyEv + 0x9F1
[7] 0x00002B3FD1810954
_ZN7ibm_cde5query9Evaluator8evaluateEbbRNS1_21EvaluatorRestartSt
ateEPNS0_19OptPredicateTrackerE + 0x954
[8] 0x00002B3FD17FE93A
_ZN7ibm_cde5query17EvaluationRoutine8evaluateEjP15sql_static_dat
a + 0x1AA
[9] 0x00002B3FD183EE5E
_ZN7ibm_cde5query9Scheduler13runThreadTaskEPvPi + 0x3AE
[10] 0x00002B3FD184C751
_ZN7ibm_cde5query17cdeEntryPointImplEP8sqeAgentPvS3_ + 0x71
[11] 0x00002B3FD18568AA
_ZN7ibm_cde5query13cdeEntryPointEP8sqeAgent + 0x7A
[12] 0x00002B3FD2CC8AB1 _Z14sqlriInvokeCdeP8sqlrr_cb + 0x41
[13] 0x00002B3FD36A25DE
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x1CE
[14] 0x00002B3FD295CAC0 _Z16sqlrr_smp_routerP8sqlrr_cb + 0x190
[15] 0x00002B3FD04A16A9
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x979
[16] 0x00002B3FCF4F2333
/home/svtdbm2/sqllib/lib64/libdb2e.so.1 + 0x3C0E333
[17] 0x00002B3FCF4F0D73 _Z21sqleProcessSubRequestP8sqeAgent +
0x2C3
[18] 0x00002B3FCF50C485 _ZN8sqeAgent6RunEDUEv + 0x795
[19] 0x00002B3FD0A74F34 _ZN9sqzEDUObj9EDUDriverEv + 0xF4
[20] 0x00002B3FD02CF2E7 sqloEDUEntry + 0x2F7
[21] 0x0000003FF8E0673D /lib64/libpthread.so.0 + 0x673D
[22] 0x0000003FF82D44BD clone + 0x6D
You may encounter this problem when the following sequence of
events occurs against a column organized table:
1. Updates or deletes that empty at least a full extent in the
table
2. Reorganization of the table using the RECLAIM EXTENTS option
(this is automatically done for column organized tables when
DB2_WORKLOAD=ANALYTICS is set and the database config parameters
auto_maint and auto_table_maint are set to ON)
3. A statement on the affected table that attempts to scan a
portion of the table that has been reclaimed
Recommended Actions:
Contact DB2 Support if you encounter this issue |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Column Organized Tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Contact DB2 Support if you encounter this issue *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
|
| Solution |
Contact DB2 Support if you encounter this issue |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.08.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
