APAR status
Closed as program error.
Error 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.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * ****************************************************************
Problem conclusion
First fixed in Db2 11.1 Mod 4 Fixpack 5
Temporary fix
Comments
APAR Information
APAR number
IT27940
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-31
Closed date
2020-01-16
Last modified date
2020-01-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 FOR LUW
Fixed component ID
DB2FORLUW
Applicable component levels
RB10 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
16 January 2020