suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT24955 Status: Closed

DB2 CRASH IN DPF + SMP AFTER INTERNAL INTERRUPT (SQL0952N)

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
IN DPF+SMP environment traps Could happen with the following
stacks:

sqloCrashOnCriticalMemoryValidationFailure
diagnoseMemoryCorruptionAndCrash
sqloDiagnoseFreeBlockFailure
sqlofmblk
sqlristm
sqlra_sqlW_mem_free_sibling_list

db2diag.log Could have the following :


FUNCTION: DB2 UDB, base sys utilities,
sqeAgentServices::RequestAgentForAppl, probe:1808
MESSAGE : Appl failed to start up on this node. Interrupt rqst =
DATA #1 : Hexdump, 4 bytes
0x0A0000004DFFD204 : 0000 0000
....

FUNCTION: DB2 UDB, buffer dist serv, sqlkdDispatchRequest,
probe:205
RETCODE : ZRC=0xFFFFFC48=-952
          SQL0952N  Processing was cancelled due to an
interrupt.

...
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:10
MESSAGE : Possible memory corruption detected.
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
0x820F0002
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8
bytes
0x0a0001000859f1b0
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x0A0001000859F198 : 0000 FF0C 0000 0000 0A00 0100 0859 F9E8
.............Y..
0x0A0001000859F1A8 : 0A00 0100 0859 EE80
.....Y..
code: 0xff0c
curSize: 0
SMemBlkFileId: 167772416
SMemBlkLOC: 2137
SMemBlkNum: 63976
CodedCSG: a0001000859ee80
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x0A0001000859F1B0 : 5441 4F42 0000 0000 0001 F348 0000 0000
TAOB.......H....
0x0A0001000859F1C0 : 0000 0000 0000 0000 0000 0000 FF00 0001
................
0x0A0001000859F1D0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x090000000C685BB4
@88@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0xF8
  [1] 0x090000000E3ACC74 sqlofmblkEx + 0xC
  [2] 0x090000000E323404 sqlridrp__FP8sqlrr_cbP9sqlri_tao +
0x1B0
  [3] 0x090000000E305EEC sqlridrp__FP8sqlrr_cbP9sqlri_tao + 0x80
  [4] 0x090000000E305C90
sqlridrp__FP8sqlrr_cbP9sqlri_tao@glue2D4 + 0x3C
  [5] 0x090000000EB9CEB4 sqlricls_complex__FP8sqlrr_cbilN23 +
0xE24
  [6] 0x090000000F8D85C8
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x1B34
  [7] 0x090000000F8D7E30
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x139C
  [8] 0x090000000CB95DAC
@82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x1850
  [9] 0x090000000F4F358C RunEDU__8sqeAgentFv + 0x35A4C
  [10] 0x090000000F473738 RunEDU__8sqeAgentFv + 0x124
  [11] 0x090000000E288AE4 EDUDriver__9sqzEDUObjFv + 0x130
  [12] 0x090000000DF1A2D4 sqloEDUEntry + 0x3A0
  [13] 0x09000000011C8E10 _pthread_body + 0xF0
  [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF

.....
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:10
MESSAGE : ADM14001C  An unexpected and critical error has
occurred: "Panic".
          The instance may have been shutdown as a result.
"Automatic" FODC
          (First Occurrence Data Capture) has been invoked and
diagnostic
          information has been recorded in directory

....
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Turn of SMP if possible.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT24299 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2018
27.11.2018
27.11.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)