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

Assertion failure and bad page error when rolling back insert that
specifies IGNORE DUPLICATES

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
An assertion failure and BAD PAGE error will occur in the
following scenario:

(1) Issue an INSERT statement with clause IGNORE DUPLICATES
where at least one of the inserted values is a duplicate key.
(The IGNORE DUPLICATES clause is allowed only when registry
variable DB2_WORKLOAD=SAP.)
(2) Roll back the above insert.

This will result in the following assertion failure and BAD PAGE
error reported in db2diag.log:

2019-04-09-17.19.10.184677-240 I280395E2815          LEVEL:
Severe
PID     : 20102                TID : 139927052347136 PROC :
db2sysc
INSTANCE: xxxxxxx              NODE : 000            DB   :
xxxxxxxx
APPHDL  : 0-7                  APPID:
*LOCAL.xxxxxxx.190409211736
AUTHID  : xxxxxxx              HOSTNAME: xxxxxxxxxxx
EDUID   : 24                   EDUNAME: db2agent (xxxxxxxx)
FUNCTION: DB2 UDB, CDE Data, Recovery::undoDeleteRows, probe:807
DATA #1 : String, 173 bytes
ASSERT_PAGE: condition=(actualTupleStateVal ==
expectedTupleStateVal): Additional info: Tuple state is not in
the expected state tupleIndex 3 actual 15 expected 1 LSN 235697
DATA #2 : Function name in Library, 46 bytes
bool ibm_cde::data::Recovery::undoDeleteRows()
DATA #3 : File name, 12 bytes
Recovery.cpp
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00007F435E041D5C
_ZN7ibm_cde8services6Tracer9traceDataENS0_11ComponentIDENS0_16Co
mmonTraceLevelENS1_10TraceEventEPKcmS6_PKvmRKSbIcSt11char_trait
+ 0x7BC
  [1] 0x00007F435E034516
_ZNK7ibm_cde8services20CdeTraceStringStream9traceDataEv + 0x196
  [2] 0x00007F435E7CF350
_ZN7ibm_cde4data8Recovery14undoDeleteRowsEv + 0xCD0
  [3] 0x00007F435E7CA510
_ZN7ibm_cde4data8Recovery11processUndoEP8sqeAgentPcP9SQLP_LSN8i
+ 0x570
  [4] 0x00007F435E88B3AA
_ZN7ibm_cde4data20cdeRecoveryInterface11processUndoEPbP8sqeAgent
PcP9SQLP_LSN8i + 0x6A
  [5] 0x00007F435DDA3DB3
_Z8sqldmundP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0x463
  [6] 0x00007F4363120F3E
_Z8sqlptudoP8sqeAgent12sqlpUndoTypeP15SQLD_RECOV_INFOP11SQLP_TEN
TRYP8SQLP_LRHPc + 0xA9E
  [7] 0x00007F436311F367 _Z8sqlptud1P8sqeAgentP11SQLP_TENTRYm +
0x757
  [8] 0x00007F43630FBD2D
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc
h + 0xC2D
  [9] 0x00007F43636A18D1
_Z12sqlrrbck_dpsP8sqlrr_cbiiiP15SQLXA_CALL_INFOP9SQLP_GXID +
0x2B1
  [10] 0x00007F43636A07B8
_Z8sqlrrbckP8sqlrr_cbiiiiP15SQLXA_CALL_INFO + 0x638
  [11] 0x00007F43636747B1 _Z14sqlrr_rollbackP14db2UCinterface +
0x171
  [12] 0x00007F43617C4043
_Z19sqljs_ddm_rdbrllbckP14db2UCinterfaceP13sqljDDMObject + 0x203
  [13] 0x00007F43617A4F5B
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0xCB
  [14] 0x00007F43617A605E
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x54E
  [15] 0x00007F4361798F3D
/home/xxxxxxx/sqllib/lib64/libdb2e.so.1 + 0x5C05F3D
  [16] 0x00007F436179F523
/home/xxxxxxx/sqllib/lib64/libdb2e.so.1 + 0x5C0C523
  [17] 0x00007F43617A01DF
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0x11F
  [18] 0x00007F43611C9113 _ZN8sqeAgent6RunEDUEv + 0xDE3
  [19] 0x00007F4364AEEA2E _ZN9sqzEDUObj9EDUDriverEv + 0x1BE
  [20] 0x00007F436301141A sqloEDUEntry + 0x57A
  [21] 0x00007F436ABAE806 /lib64/libpthread.so.0 + 0x7806
  [22] 0x00007F435A6FA64D clone + 0x6D

2019-04-09-17.19.10.214762-240 E283211E1014          LEVEL:
Critical
PID     : 20102                TID : 139927052347136 PROC :
db2sysc
INSTANCE: xxxxxxx              NODE : 000            DB   :
xxxxxxxx
APPHDL  : 0-7                  APPID:
*LOCAL.xxxxxxx.190409211736
AUTHID  : xxxxxxx              HOSTNAME: xxxxxxxxxxx
EDUID   : 24                   EDUNAME: db2agent (xxxxxxxx)
FUNCTION: DB2 UDB, CDE Data,
DatabaseTableAccessor::checkForBadPageAndRelease, probe:10
MESSAGE : ADM14001C  An unexpected and critical error has
occurred: "BadPage".
          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

"/home/xxxxxxx/sqllib/db2dump/FODC_BadPage_2019-04-09-17.19.10.2
14677
          _0000/". Please look in this directory for detailed
evidence about
          what happened and contact IBM support if necessary to
diagnose the
          problem.

2019-04-09-17.19.10.217772-240 I284226E635           LEVEL:
Severe
PID     : 20102                TID : 139927052347136 PROC :
db2sysc
INSTANCE: xxxxxxx              NODE : 000            DB   :
xxxxxxxx
APPHDL  : 0-7                  APPID:
*LOCAL.xxxxxxx.190409211736
AUTHID  : xxxxxxx              HOSTNAME: xxxxxxxxxxx
EDUID   : 24                   EDUNAME: db2agent (xxxxxxxx)
FUNCTION: DB2 UDB, CDE Data,
DatabaseTableAccessor::checkForBadPageAndRelease, probe:3075
RETCODE : ZRC=0x87DB0001=-2015690751=CDE_SEVERE_BADPAGE
          "Severe CDE bad page error"
          DIA8500C A data file error has occurred, record id is
"".
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2019
20.01.2020
20.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)