|
Problem IT05596
|
Status: Geschlossen |
DATABASE HANG DURING CONCURRENT INSERT, MERGE AND DELETE STATEMENTS AGAINST ITC TABLE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
You might encounter a database hang during concurrent INSERT,
MERGE and DELETE statements against an ITC (insert time
clustering) table.
Neither a FORCE APPLICATIONS nor a db2stop force will help to
release the hang situation.
Using the db2pd -latches output you will see EDUs waiting for
SQLO_LT_SQLD_PAGE_CACHE__pageCacheLatch. This latch in return
will be held by the inserting EDU which is waiting for
SQLO_LT_SQLB_BPD__bpdLatch_SX latch itself.
The stack of the inserting EDU will look like:
SQLO_SLATCH_CAS64::getConflictComplex
SQLO_SLATCH_CAS64::getConflict
sqlbGetAndMonitorPageLatch
sqlbfix
sqldb_blkMapScanPagesFwd
sqldb_searchMap
sqldb_blkMapSearch
sqldb_findNewBlock
sqldb_findNewBlockAndInsert
sqldCreateAppendCachePagesForMDCTable
sqldCreateNewAppendCache
sqldExtendAppendCache
sqldSearchPageCache
sqldb_insertITCRow
sqldRowInsert
sqlrinsr
sqlriisr
sqlriSectInvoke
The stack for the deleting EDU will look like:
SQLO_SLATCH_CAS64::getConflictComplex
SQLO_SLATCH_CAS64::getConflict
sqloltch_ns_track
sqldb_isBlockInAppendCache
sqldb_updateBlkOnPage
sqldb_updateBitsForBlockNum
sqldb_freeBlock
sqldRowDelete
sqlridel
sqlriSectInvoke |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.5. *
**************************************************************** |
| Local-Fix: |
|
| Lösung |
The problem is first fixed in DB2 version 10.1.0.5. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 17.11.2014
10.07.2015
10.07.2015 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.5
|
 |
