|
Problem IT23130
|
Status: Closed |
POSSIBLE HANG BETWEEN 3 EDUS INVOLVING SQLO_LT_SQELOCALDATABASE__DBLATCH AND ANOTHER UNTRACKED LATCH
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Possible hang caused by 3 EDUs.
Most EDUs will be waiting for the
SQLO_LT_sqeLocalDatabase__dblatch.
1 EDU will be waiting for a cleanup agent to be created with the
TOP stack looking like this:
0x00007F9F906DEFFA semtimedop + 0x000a
0x00007F9F9884950F sqloWaitEDUWaitPost + 0x03bf
0x00007F9F96C5A4D4 sqeIcoordCB::WaitForSanityCheck + 0x0044
0x00007F9F96C5B697 sqeIcoordCB::DispatchIndependentDBAgent +
0x0b17
0x00007F9F9301CF03 ABPIcoordAgent::spawnIcoordAgent + 0x00c3
0x00007F9F93016FA2 ABPDispatcher::spawnAgent + 0x0152
0x00007F9F93013F88 ABPDispatcher::activateTaskProContexts +
0x0268
0x00007F9F9301BB4F abpActivateTaskProContexts + 0x004f
0x00007F9F9304B818 pdCreateDumpCleanupTask + 0x01c8
0x00007F9F934DA419 pdLogInternal
0x00007F9F934EE0E4 pdOSSeLoggingCallback + 0x0394
0x00007F9F91690BA1 ossLog + 0x00a1
0x00007F9F9169AB1D OSSHIPCSemaphoreEx::create + 0x01bd
The db latch holder will be waiting for the latch that the EDU
above is holding:
0x00007F9F9FAE8BDD __nanosleep + 0x002d
0x00007F9F98835EF7 sqloSpinLockConflict + 0x05d7
0x00007F9F98854BBB SqloOSResourcePosixSemSlotManager::search +
0x009b
0x00007F9F9886CA86 sqloNLCKInit + 0x0366
0x00007F9F989F1188 SQLP_GLFH_CB::lock + 0x0438
0x00007F9F989CAB4A sqlpgOpenGLFH + 0x018a
0x00007F9F989CE329 sqlpgReadGLFHFromDiskAndMigrate + 0x09d9
0x00007F9F96B3A5F9 sqeTopologyInfo::load + 0x0079
0x00007F9F96ED56E6 sqleGetTopologyInfo + 0x0056
0x00007F9F96C0FAE0 sqeApplication::CreateDbMemberTopologyView
+ 0x0300
0x00007F9F96D0405B sqeLocalDatabase::RegisterApp + 0x009b
0x00007F9F96D18C70 sqeLocalDatabase::SubsequentConnect +
0x1d30
0x00007F9F96CDFF8E sqeDBMgr::StartUsingLocalDatabase + 0x10fe
0x00007F9F96C0772E sqeApplication::AppStartUsing + 0x05ee
0x00007F9F96C0C297 sqleSubAgentStartUsing + 0x0567
0x00007F9F96C0B137 sqeApplication::AppSecondaryStartUsing +
0x0a17
And the new agent that has been created for cleaning up will be
waiting for the db latch. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 10 or higher *
**************************************************************** |
| Local Fix: |
Disable rotating diag log by setting DIAGSIZE to 0 |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2017
19.07.2018
19.07.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
