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

Crash during crash recovery processing

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
During crash recovery, an RPC was not processed due to a 
programming error.  This resulted in a member inconsistency. 
 
A symptom of this issue is the following call stack during crash 
recovery 
014-01-23-18.58.57.684795-300 I233766201A3316      LEVEL: Severe 
PID     : 14614750             TID : 29834          KTID : 
78577759 
PROC    : db2sysc 1 
INSTANCE: eunicec2             NODE : 001           DB   : CORAL 
APPHDL  : 1-4414               APPID: *N1.DB2.140124010937 
HOSTNAME: coralpib126 
EDUID   : 29834                EDUNAME: db2agnti (CORAL   ) 1 
FUNCTION: DB2 UDB, data protection services, 
sqlpValLotch::verifyReturnedRc, probe:666 
MESSAGE : ZRC=0x852700AF=-2061041489=SQLE_SAL_CACHE_RAR_NODATA 
          "CA_CACHE_RAR_NODATA" 
DATA #1 : String, 28 bytes 
unexpected validity lotch rc 
DATA #2 : Hex integer, 4 bytes 
0xCFA20200 
DATA #3 : Codepath, 8 bytes 
10:30 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x0900000009638070 pdLog + 0x2D0 
  [1] 0x0900000009B39584 verifyReturnedRc__12sqlpValLotchFiUl + 
0x104 
  [2] 0x0900000009B46480 
getSDComplex__12sqlpValLotchFCUlT1CPCiCPCcT1 + 0x1840 
  [3] 0x090000000A9C6E98 getSD__12sqlpValLotchFCUlT1CPCiCPCcT1 + 
0x778 
  [4] 0x090000000A9C7290 get__12sqlpValLotchFCUlT1CPCiCPCcT1 + 
0x230 
  [5] 0x090000000A9C7358 get__12sqlpValLotchFCUlT1CPCcT1 + 0x38 
  [6] 0x090000000A9C73F0 get__12sqlpValLotchFCUlCPCcT1 + 0x30 
  [7] 0x090000000A9C7478 get__15sqleGSSValLotchFCUlCPCcT1 + 0x38 
  [8] 0x090000000A9C7E04 
sqleGSSAcquireLock__FPvCUlCP14SqlzDB2Version + 0x64 
  [9] 0x090000000A9CB3DC sqlbGetGssReadAccess__13SQLB_POOL_GSSFb 
+ 0x7C 
  [10] 0x090000000A9D31B8 refresh__16sqlbPoolDefLotchFUl + 0x38 
  [11] 0x0900000009B46238 
getSDComplex__12sqlpValLotchFCUlT1CPCiCPCcT1 + 0x15F8 
  [12] 0x090000001248DD78 getSD__12sqlpValLotchFCUlT1CPCiCPCcT1 
+ 0x778 
  [13] 0x090000001248E170 get__12sqlpValLotchFCUlT1CPCiCPCcT1 + 
0x230 
  [14] 0x090000001248E238 get__12sqlpValLotchFCUlT1CPCcT1 + 0x38 
  [15] 0x090000001248E2D0 get__12sqlpValLotchFCUlCPCcT1 + 0x30 
  [16] 0x09000000124934F8 
sqlbLatchPoolR_inline__FP12SQLB_POOL_CBibT2PCc + 0xF8 
  [17] 0x09000000124953F4 
sqlbCompleteCrashRecovery__FP12SQLB_GLOBALSUi + 0x274 
  [18] 0x0900000013E26884 
sqlpresr__FP8sqeAgentP16sqlpRecoveryTypePbP5sqlca + 0xDC4 
  [19] 0x0900000009DE28C0 
RecoverDatabase__16sqeLocalDatabaseFP8sqeAgentPbT2P5sqlca + 
0x6C0 
  [20] 0x0900000009DE6660 
RestartDatabase__16sqeLocalDatabaseFP14sqeApplicationP8sqeAgentP 
8SQLE_BWAP22SQLESRSU_STATUS_VECTORP5sqlca + 
 0x540 
  [21] 0x0900000009E9CE54 
InitEngineComponents__14sqeApplicationFcP8sqeAgentP8SQLE_BWAP5sq 
lcaP22SQLESRSU_STATUS_VECTORT1 + 0xB74 
  [22] 0x0900000009EA2938 
AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc 
+ 0x1018 
  [23] 0x0900000009EB23C0 
sqleSubAgentStartUsing__FP8sqeAgentP16SQLE_CLIENT_INFO + 0xC00 
  [24] 0x0900000009EB3B64 
AppSecondaryStartUsing__14sqeApplicationFP8sqeAgentP16SQLE_CLIEN 
T_INFOP5sqlca + 0x424 
  [25] 0x090000000BF52518 
sqleIndDBConnInit__FP8sqeAgentP16SQLE_CLIENT_INFOiP5sqlca + 
0x4F8 
  [26] 0x090000000BF52ED8 
sqleIndCoordInit__FP8sqeAgentiP5sqlcaT2 + 0x598 
  [27] 0x090000000BF5DCC8 
sqleIndCoordProcessRequest__FP8sqeAgent + 0x708 
  [28] 0x0900000009A927CC RunEDU__8sqeAgentFv + 0x3AC 
  [29] 0x0900000009A5017C EDUDriver__9sqzEDUObjFv + 0x23C 
  [30] 0x0900000009A504BC sqlzRunEDU__FPcUi + 0x3C 
  [31] 0x09000000097A0F34 sqloEDUEntry + 0x7B4 
  [32] 0x09000000007D9D30 _pthread_body + 0xF0 
  [33] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 pureScale                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4                              * 
****************************************************************
Local-Fix:
Upgrade to this fixpack.
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
The problem is first fixed in DB2 version 10.5.0.4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.04.2014
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList