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

DB2 MIGHT TRAP DURING ROLLBACK OF TRUNCATE TABLE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
During a rollback of a truncate table operation, Db2 might trap
in the following stack:

sqldTruncateDataPart
sqldFastTruncateTable
sqldTableInit
sqldWriteTableInitLR

leaving behind the following db2diag.log message:

2018-02-01-14.21.29.739199+060 I14761003E3066        LEVEL:
Severe
PID     : 32764                TID : 140476837521152 PROC :
db2sysc 4
INSTANCE: db2jkl               NODE : 004            DB   : JKL
APPHDL  : 0-26500              APPID:
10.0.0.1.23031.180201131033
AUTHID  : SAPR3                HOSTNAME: hostname
EDUID   : 24075                EDUNAME: db2agntp (JKL) 4
FUNCTION: DB2 UDB, data management,
sqldVerifyTruncOperationForObj, probe:2617
MESSAGE : Object had invalid lifeLSN after truncation
DATA #1 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
0000007F5BDC8706
DATA #2 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
000000835FBCBA72
DATA #3 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 104 bytes
    Obj: {pool:26;obj:165;type:0} Parent={26;165}
    lifeLSN:       0000007F5BDC8706
    tid:           0 0  0
    extentAnchor:              595922
    initEmpPages:                   0
    poolPage0:                      0
    poolflags:   0x              3122
    objectState: 0x             80027
    lastSMP:                        0
  pageSize:                   16384
  extentSize:                     2
  bufferPoolID:                   1
  partialHash:             10813466
  objDescAttributes:                  0
  objDescEHLState: 0x00007fc875be3fa8
  bufferPool:    0x00007fc4151ccf00
  pdef:          0x00007fc4152a4f00
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00007FC971AC7CAA
_Z30sqldVerifyTruncOperationForObjP8sqeAgentP11SQLB_OBJECTP9SQLP
_LSN8S4_P15SQLD_RECOV_INFO + 0x22A
  [1] 0x00007FC971AC7F6C /db2/db2pb3/sqllib/lib64/libdb2e.so.1 +
0x51D3F6C
  [2] 0x00007FC96DCD53FF
_Z10sqldomUndoP8sqeAgentP10SQLDOM_LRHP9SQLP_LSN8sP15SQLD_RECOV_I
NFO + 0x7DF
  [3] 0x00007FC96DCCE3C6
_Z8sqldmundP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0x626
  [4] 0x00007FC970A7E5A8
_Z8sqlptudoP8sqeAgent12sqlpUndoTypePmP15SQLD_RECOV_INFOP11SQLP_T
ENTRYP8SQLP_LRHPc + 0x1D8
  [5] 0x00007FC970A7D8AB _Z8sqlptud1P8sqeAgentm + 0x27B
  [6] 0x00007FC970A68A32 _Z8sqlpSpRbP8sqeAgent11SQLP_SPTYPEm +
0x1B2
  [7] 0x00007FC971A744DF /db2/db2pb3/sqllib/lib64/libdb2e.so.1 +
0x51804DF
  [8] 0x00007FC971A74E9F
_Z17sqldTableTruncateP8sqeAgenttthtPciS1_i + 0xFF
  [9] 0x00007FC9732F7E29
_Z8sqlrltt0P8sqlrr_cbhttPhsS1_sjP8sqlrg_idhht + 0x139
  [10] 0x00007FC9732F7BA5
_Z8sqlrlttcP8sqlrr_cbP23SQLKD_RQST_REPLY_FORMATiP13SQLR_RPC_DCIX
+ 0x165
  [11] 0x00007FC970F4F0E9
_Z20sqlrl_rpc_dms_routerP8sqlrr_cbP23SQLKD_RQST_REPLY_FORMATiP15
SQLR_RPCMESSAGE + 0x8B9
  [12] 0x00007FC970C34EB3 _Z16sqlrr_rpc_routerP8sqlrr_cb + 0x203
  [13] 0x00007FC970C33CAB
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0xB0B
  [14] 0x00007FC96FA4DC3D /db2/db2pb3/sqllib/lib64/libdb2e.so.1
+ 0x3159C3D
  [15] 0x00007FC96FA4C6DB _Z21sqleProcessSubRequestP8sqeAgent +
0x30B
  [16] 0x00007FC96FA67B7F _ZN8sqeAgent6RunEDUEv + 0x48F
  [17] 0x00007FC97127F537 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
  [18] 0x00007FC970A37B03 sqloEDUEntry + 0x303
  [19] 0x00007FC977E23DC5 /lib64/libpthread.so.0 + 0x7DC5
  [20] 0x00007FC96B68CCED clone + 0x6D

This APAR will avoid the trap but will leave the table in status
Drop Pending. Additionally, it introduces further output in the
code in case of an occurrence of the issue.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT24104 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.02.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)