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 IT23185 Status: Closed

MEMORY CORRUPTION DURING XA PROCESSING ON FEDERATED OBJECT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The corruption may happen during distributed transaction
processing while it rollbacks operation on federated object
(nickname).

Once it happens, following stack is logged to db2diag.log:


2017-11-14-15.34.55.008298-300 E2055403A2417        LEVEL:
Severe
PID     : 39781600             TID : 326331         PROC :
db2sysc 0
INSTANCE: ########             NODE : 000           DB   :
########
APPHDL  : 0-8317               APPDB:
xx.xx.xx.xx.xxxxx.171130050011
AUTHID  : STMTS                HOSTNAME: ########
EDUID   : 326331               EDUNAME: db2agent (########) 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:999
MESSAGE : Memory validation failure, diagnostic file dumped.
DATA #1 : String, 21 bytes
Invalid block header.
DATA #2 : File name, 35 bytes
39781600.326331.mem_diagnostics.txt
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x0900000032C40F54
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb +
0x444
  [1] 0x0900000032C4183C
@88@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0x754
  [2] 0x09000000346E6D94 sqlofmblkEx + 0x10
  [3] 0x0900000035644224
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc
h + 0x46CC
  [4] 0x0900000035641758
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc
h + 0x1C00
  [5] 0x0000000000000000 ?unknown + 0x0
  [6] 0x090000003560E48C
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc
h + 0x558
  [7] 0x0900000035610550
sqlrrbck_dps__FP8sqlrr_cbiN22P15SQLXA_CALL_INFOP9SQLP_GXID +
0xDE0
  [8] 0x0900000035613FD4
sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0x1998
  [9] 0x0900000033B30A34 sqlrr_xrollback__FP14db2UCinterface +
0x1D6C
  [10] 0x0900000030632F4C sqljsSyncRollback__FP14db2UCinterface
+ 0x6E0
  [11] 0x0900000033B95A70
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x9E30
  [12] 0x14F70E17B42CD369 ?unknown + 0x14F70E18B42CD36C
  [13] 0x0900000033BE4370
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x1108
  [14] 0x0900000033BE3F64
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xCFC
  [15] 0x09000000359C970C
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
  [16] 0x09000000359CA21C
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8
  [17] 0x090000003320E91C RunEDU__8sqeAgentFv + 0x4C7A8
  [18] 0x0900000033239AD4 RunEDU__8sqeAgentFv + 0x124
  [19] 0x0900000034763550 EDUDriver__9sqzEDUObjFv + 0x134
  [20] 0x0900000034CD6B80 sqloEDUEntry + 0x3A0
  [21] 0x0900000000567E10 _pthread_body + 0xF0
  [22] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* FEDERATED                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 Version 10.5 Fix Pack 10                      *
****************************************************************
Local Fix:
To workaround the issue, 2 phase commit should be set for
federated server:

ALTER SERVER SERVERNAME OPTIONS (ADD  DB2_TWO_PHASE_COMMIT  'Y')
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT24657 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.11.2017
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)