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 IT07770 Status: Geschlossen

QUERY ON COLUMN-ORGANIZED TABLE MIGHT FAIL WITH -901: UNEXPECTED ERROR AT
PAGEITERATORFORTSNRANGE.CPP

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Under a specific timing condition, when two (or more) queries 
access the same page of a column-organized table and at least 
one of them modifies it, the other one might fail with: 
-901: unexpected error at PageIteratorForTSNRange.cpp:512 
Error including message "pageReadCount < 100 failed" will be 
logged to db2diag: 
 
2015-01-01-00.00.00.219919+060 I132875604A3390      LEVEL: 
Severe 
PID     : 19399340             TID : 164092         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-20009              APPID: *LOCAL.app.150101000000 
AUTHID  : DB2INST1             HOSTNAME: db2blu 
EDUID   : 164092               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:512 
MESSAGE : SQL0901N  The SQL statement or command failed because 
of a database 
          system error. (Reason "".) 
DATA #1 : <preformatted> 
'pageReadCount < 100' failed. Info:Unable to access target page 
from page map: 
   ExclusivePageAccess:      FALSE 
   mColumnGroupIndex:        4 
   pageReadCount:            100 
   mCurrentPageID:           313333 
   pageDesc.mStartTSN:       1152921504610043238 
   pageDesc.mEndTSN:         1297036692682702847 
   page.pgColGroupNumber:    4 
   page.pgStartTSN:          0 
   currentTSN:               1152921504610046638 
   mTableAccessor.tableName: WM_G_CON 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x09000000448C4084 pdLogPrintf + 0x28 
  [1] 0x0900000049033610 
done__Q3_7ibm_cde8services24AssertionFailedExceptionFv + 0x118C 
  [2] 0x090000004B51697C 
constructAndThrow__Q3_7ibm_cde8services24AssertionFailedExceptio 
nFCQ3_7ibm_cde8services11ComponentIDCPCcCUlN22RCQ3_7ibm_cde8ser 
+ 0x204 
 
... 
2015-01-01-00.00.00.319919+060 I132880366A907       LEVEL: 
Severe 
PID     : 19399340             TID : 164092         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-20009              APPID: *LOCAL.app.150101000000 
AUTHID  : DB2INST1             HOSTNAME: db2blu 
EDUID   : 164092               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 51 
 sqlerrmc: unexpected error at PageIteratorForTSNRange.cpp:512 
 sqlerrp : SQLCT001 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFE00      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of column-organized tables                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 7 or higher.            * 
****************************************************************
Local-Fix:
Retry failed query
Lösung
Fixed in DB2 version 10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.03.2015
28.01.2016
28.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList