DB2 - Problembeschreibung
Problem IC97691 | Status: Geschlossen |
A DELETE TABLE STATEMENT ON A COLUMN ORGANIZED TABLE COULD BRING DOWN THE DATABASE WHEN RUNS INTO A CONDITIONAL LOCK CONFLICT. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
When a delete table statement is issued on a column organized table, in rare circumstances the statement runs into a conditional lock conflict while acquiring lock on the tuple. The statement then fails with a SQL0901N. The database however is also brought down with this failure. An example of the statement failing is shown here: ---------------------------------------------------------- db2 "delete from t1 where a=1" DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement or command failed because of a database system error. (Reason "unexpected error at BaseZrcErrorHandler.cpp:109".) SQLSTATE=58004 db2diag.log will contain messages similar to the below: --------------------------------------------------------------- +291706 2013-11-06-10.45.44.671790-300 I10925511A2597 LEVEL: Severe +291707 PID : 24052032 TID : 171684 PROC : db2sysc +291708 INSTANCE: svtdbm6 NODE : 000 DB : BLU1 +291709 APPHDL : 0-361 APPID: 9.23.4.206.45773.131106115814 +291710 AUTHID : SVTDBM6 HOSTNAME: largenode36 +291711 EDUID : 171684 EDUNAME: db2agntcol (BLU1) +291712 FUNCTION: DB2 UDB, CDE Data, DatabaseTableAccessor::upgradeTSNLockToX, probe:3680 +291713 MESSAGE : ZRC=0x80100079=-2146434951=SQLP_LCON "Conditional Conflict" +291714 DIA8132C Conditional lock error occurred, lock name was "". +291715 DATA #1 : String, 25 bytes +291716 Programming logic error. +291717 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) +291718 [0] 0x0900000011530A3C throwZrcException__Q3_7ibm_cde4data19BaseZrcErrorHandlerCFiUiUlT 1e + 0xDC +291719 [1] 0x090000001158DF00 upgradeTSNLockToX__Q3_7ibm_cde4data21DatabaseTableAccessorFPQ3_7 ibm_cde4data10TALockInfo + 0x380 +291720 [2] 0x09000000137E65DC findTSNsToDelete__Q3_7ibm_cde5query18DeleteRowEvaluatorFPQ3_7ibm _cde4data20ExclusivePageRequestPQ3_7ibm_cde4data23PageIteratorF + 0x8DC +291721 [3] 0x09000000137E4280 deleteTSNsOnPage__Q3_7ibm_cde5query18DeleteRowEvaluatorFRCQ3_7ib m_cde5query8WorkUnitRCQ3_7ibm_cde5types3TSNRQ3_7ibm_cde5types9B + 0x1A0 +291722 [4] 0x09000000137E0948 processInputsSynchronously__Q3_7ibm_cde5query18DeleteRowEvaluato rFv + 0x488 +291723 [5] 0x09000000122AFBE0 evaluate__Q3_7ibm_cde5query9EvaluatorFbT1RQ4_7ibm_cde5query9Eval uator21EvaluatorRestartStatePQ3_7ibm_cde5query19OptPredicateTra + 0xC80 +291724 [6] 0x090000001232F890 evaluate__Q3_7ibm_cde5query17EvaluationRoutineFUiP15sql_static_d ata + 0x270 +291725 [7] 0x09000000128AF8FC runThreadTask__Q3_7ibm_cde5query9SchedulerFPvPi + 0xC5C +291726 [8] 0x09000000128C0240 cdeEntryPointImpl__Q2_7ibm_cde5queryFP8sqeAgentPvT2 + 0xC0 +291727 [9] 0x0900000012A23C08 cdeEntryPoint__Q2_7ibm_cde5queryFP8sqeAgent + 0x188 +291728 [10] 0x090000000AD56544 sqlriInvokeCde__FP8sqlrr_cb + 0x9C +291729 [11] 0x0900000008D3D38C sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x180 +291730 [12] 0x0900000009325258 sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x52B0 +291731 [13] 0x09000000092BA784 sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xD7C +291732 [14] 0x09000000092BB30C @81@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x430 +291733 [15] 0x090000000834F160 RunEDU__8sqeAgentFv + 0x2E880 +291734 [16] 0x090000000838B83C RunEDU__8sqeAgentFv + 0xD8 +291735 [17] 0x090000000989D710 EDUDriver__9sqzEDUObjFv + 0x124 +291736 [18] 0x090000000872BC30 sqloEDUEntry + 0x38C +291737 [19] 0x0900000000836E10 _pthread_body + 0xF0 +291738 [20] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF +291739 +291740 2013-11-06-10.45.44.674107-300 I10928109A850 LEVEL: Error +291741 PID : 24052032 TID : 171684 PROC : db2sysc +291742 INSTANCE: svtdbm6 NODE : 000 DB : BLU1 +291743 APPHDL : 0-361 APPID: 9.23.4.206.45773.131106115814 +291744 AUTHID : SVTDBM6 HOSTNAME: largenode36 +291745 EDUID : 171684 EDUNAME: db2agntcol (BLU1) +291746 FUNCTION: DB2 UDB, CDE Data, DatabaseTableAccessor::upgradeTSNLockToX, probe:3680 +291747 DATA #1 : SQLP_LOCK_INFO, PD_TYPE_SQLP_LOCK_INFO, 144 bytes +291748 lockname 000A0008000000000004C01658 SQLP_TSN (obj={10;8}, tsn=311318) +291749 pLRB a00020016cc5700 prevIntent ..U curIntent ..U intent ..X duration 1 +291750 rlInFlags 0x00002021 rlOutFlags 0x00000000 rlTimeout 0xFFFFFFFE cursorBitmap 0x40000000 rrIIDin 0 rrIIDout 0 priority 2 +291751 rlUserData.insertRangeHWM.highWaterMark 18446744073709551614 +291752 dataPtr 0 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 BLU users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fixpack 3 * **************************************************************** | |
Local-Fix: | |
No local workaround available. If the database crashes due to this issue then restarting the database will bring the database back up. | |
verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem fixed fixed in DB2 Version 10.5 Fixpack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.11.2013 27.02.2014 27.02.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.3 | |
10.5.0.3 |