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

UNEXPECTED SQLP_LTIMEOUT ERROR CAN CAUSE ABNORMAL DATABASE SHUTDOWN.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Error Description

Abnormal database shutdown is seen after the following message
in db2diag.log:

2019-02-06-11.54.17.652495+060 I43829055E798        LEVEL:
Severe
PID     : 68357                TID : 17723710959968 PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 004           DB   :
SAMPLE
APPHDL  : 0-6383               APPID: xxxxxxxxxxxxxxx
AUTHID  : xxxxxxxxxxxx         HOSTNAME: node0102-fab
EDUID   : 53117                EDUNAME: db2agnta (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldCriticalSectionEnd,
probe:128
CALLED  : DB2 UDB, data management, sqldProtectPendAct
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT
          "LockTimeOut - tran rollback Reason code 68"
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x0000000000000000 ?unknown + 0x0
  [1] 0x0000000000000000 ?unknown + 0x0

This issue only occurs when a lock wait event monitor is being
used.

Another symptom is panic causing abnormal shutdown of DB2 during
online REORG

2019-01-01-22.13.29.584101-240 I520089A1024         LEVEL:
Severe

PID     : 31064496             TID : 9200           PROC :
db2sysc 0

INSTANCE: db2inst1             NODE : 000           DB   :
SAMPLE

APPHDL  : 0-26770              APPID: xxxxxx

AUTHID  : DB2UDB               HOSTNAME: test

EDUID   : 990                 EDUNAME: db2reorg (SAMPLE) 0

FUNCTION: DB2 UDB, data management, sqldChangeToCleanupPhase,
probe:10

MESSAGE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT

          "LockTimeOut - tran rollback Reason code 68"

DATA #1 : String, 18 bytes

upgrade cleanLock:

DATA #2 : SQLP_LOCK_INFO, PD_TYPE_SQLP_LOCK_INFO, 144 bytes

lockname 00021A0100000001000000006A SQLP_ONLINEREORG
(obj={2;6657;1})

pLRB a000300198e9980 prevIntent .IN curIntent .IN intent .IX
duration 1

rlInFlags 0x00001100 rlOutFlags 0x00000000 rlTimeout NO_TIMEOUT
cursorBitmap 0x40000000 rrIIDin 0 rrIIDout 0 priority 2
pEHLState 0000000000000000
rlUserData.UNKNOWN 0000 0000 0000 0000
........



dataPtr 0

With function stack:

pthread_kill
sqloDumpEDU
sqle_panic
IPRA.$sqldChangeToCleanupPhase
sqldDoCleanupLogEndMovePhase
sqldPerformOlrRowMovement
sqldOnlineTableReorg
sqldOLRInvoke
sqleIndCoordProcessRequest
RunEDU
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Disable the use of lock wait event monitor.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.02.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)