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

DB2 REORG RECLAIM EXTENTS ON ITC TABLES MIGHT DEADLOCK WITH AN APPLICATION

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The first application is running a reorg reclaim but is waiting 
for a latch: 
 
Application handle                         = 1 
Application status                         = UOW Executing 
Status change time                         = 01/18/2019 
17:10:35.327817 
Application code page                      = 819 
Application country/region code            = 1 
DUOW correlation token                     = 
*LOCAL.db2jkl.190118160509 
Application name                           = db2bp 
Application ID                             = 
*LOCAL.db2jkl.190118160509 
Sequence number                            = 00001 
 
Agent process/thread ID                    = 101 
 
 
Stack of this EDU: 
 
thread_wait 
SQLO_SLATCH_CAS64::getConflictComplex 
SQLO_SLATCH_CAS64::getConflict 
get 
sqldDoCleanupLogEndMovePhase 
sqldbPerformItcOlrRowMovement 
sqldOnlineTableReorg 
sqlrreorg_table 
sqlrreorg_sendinfo 
sqlerKnownProcedure 
 
The second application is holding that latch but is waiting for 
a lock that the 
first application has acquired: 
 
Application handle                         = 2 
Application status                         = Lock-wait 
Status change time                         = 01/18/2019 
17:16:02.030054 
Application code page                      = 819 
Application country/region code            = 1 
DUOW correlation token                     = 
192.168.2.1.51249.190118095507 
Application name                           = disp+work 
Application ID                             = 
192.168.2.1.51249.190118095507 
Sequence number                            = 00705 
 
Agent process/thread ID                    = 102 
... 
ID of agent holding lock                 = 1 
Application ID holding lock              = 
*LOCAL.db2jkl.190118160509 
Lock name                                = 
0x000B000600000001000000006A 
Lock attributes                          = 0x00000000 
Release flags                            = 0x00000000 
Lock object type                         = Inplace Reorg Lock 
Lock mode                                = Share with Intention 
Exclusive Lock (SIX) 
Lock mode requested                      = Share Lock (S) 
Name of tablespace holding lock          = TABLESPACE1 
Schema of table holding lock             = SAPR3 
Name of table holding lock               = TABLE1 
Data Partition Id of table holding lock  = 0 
Lock wait start timestamp                = 01/18/2019 
17:16:02.030055 
 
The second application is running the following stack: 
 
thread_wait 
sqloWaitEDUWaitPost 
sqlplWaitOnWP 
sqlplWaitOnWP 
sqlplrq 
sqlplrq 
sqldOLRScanState 
sqldScanOpen 
sqldScanOpen 
sqlritaSimplePerm 
sqlriSectInvoke 
sqlriSectInvoke 
sqlrr_process_fetch_request 
sqlrr_open 
sqljsParseRdbAccessed 
 
These two application are waiting for each other. The reorg will 
not show any 
progress.
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
First fixed in Db2 11.1 Mod 4 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2020
11.02.2020
11.02.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)