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

HANG BETWEEN STOP HADR, SET WRITE SUSPEND AND ARCHIVE LOG COMMANDS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Running STOP HADR, SET WRITE SUSPEND and ARCHIVE LOG commands at
the same time may result in circular dependencies causing these
commands to hang.

You might see the following stacks.

(1) An agent executing STOP HADR is waiting for
suspendIOCBLatch, holding glfhLotch.


-------Frame------ ------Function + Offset------
0x0900000000113014 thread_wait + 0x94
0x090000001A7A89F0 getConflictComplex__17SQLO_SLATCH_CAS64FCUl +
0x298
0x0900000019E25BD8 getConflict__17SQLO_SLATCH_CAS64FCUl + 0xB8
0x090000001B0FAE64
getSuspendIOCBLatchAndCheckState__18sqlpSuspendIOGuardFv + 0x6A0
0x090000001AD0E35C sqlpgUpdateGLFH__FP9SQLP_GLFHP12SQLP_GLFH_CB
+ 0x70
0x090000001B264808 sqlpgOpenAndUpdateGLFH__14sqlpMasterDbcbFv +
0xB8
0x090000001B264540 writeNew__16sqlpGLFHValLotchFv + 0x80
0x09000000162E8910 hdrSetDbRoleAndDbType__FP9SQLP_DBCBCUiT2 +
0x1CC4
0x090000001BBDAA84 hdrPerformStop__FP8sqeAgentP5sqlca + 0x9A8
0x0900000019546284
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x3D36C
0x090000001944FD18
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0xF70
0x0900000019463A58 sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo +
0x5FC
0x090000001A1DDD74
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x734
0x090000001A1F8260 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x1174
0x090000001A1F8260 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x1174
0x090000001A1F7E54 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0xD68
0x090000001B705B90
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
0x090000001B7066A0
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8
0x09000000198B35AC RunEDU__8sqeAgentFv + 0x48C38
0x0900000019831240 RunEDU__8sqeAgentFv + 0x124
0x090000001AD4BDFC EDUDriver__9sqzEDUObjFv + 0x130
0x0900000019DBC664 sqloEDUEntry + 0x390

.....

Waiting on latch type:
(SQLO_LT_sqeSuspendIOCB__m_suspendIOCBLatch) - Address:
(0x780000002b17d08), Line: 221, File: sqlpSuspendIOGuard.C
Holding Latch type: (SQLO_LT_HADR_SHARED__hshShutdownLatch) -
Address: (0xa000300ee46c120), Line: 386, File:
/view/db2_v105fp5_aix64_s141128/vbs/engn/include/hdrShared.h
HoldCount: 1
Holding Latch type: (SQLO_LT_SQLP_GLFH_VALLOTCH__glfhLotch) -
Address: (0xa000300000758b8), Line: 1103, File: hdr.C HoldCount:
1



(2) The suspendIOCBLatch is held by an agent executing SET WRITE
SUSPEND, which is waiting for a tranEntryLatch.


-------Frame------ ------Function + Offset------
0x090000001A90965C sqloXlatchConflict + 0x46C
0x0900000019CE5618
sqlpWriteLRSingularTran__FP8sqeAgentUlN42P14SQLP_LREC_PARTPUlP9S
QLP_LSN8bN28 + 0xEA4
0x0900000018A95FB0 sqleDoMemberSuspendProcessing__FP9sqeBsuEdu +
0xCAC
0x0900000018A917A0 sqleDoMemberSuspendProcessing__FP9sqeBsuEdu +
0xC64
0x09000000191CFBE4 sqleSetWriteSuspend__FP5sqlcaP9sqeBsuEduCUl +
0x7A40
0x0900000019570F90
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0x68078
0x090000001944FD18
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5
sqlca + 0xF70
0x0900000019463A58 sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo +
0x5FC
0x090000001A1DDD74
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x734
0x090000001A1F8260 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x1174
0x090000001A1F8260 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0x1174
0x090000001A1F7E54 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0xD68
0x090000001B705B90
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
0x090000001B7066A0
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8
0x09000000198B35AC RunEDU__8sqeAgentFv + 0x48C38
0x0900000019831240 RunEDU__8sqeAgentFv + 0x124
0x090000001AD4BDFC EDUDriver__9sqzEDUObjFv + 0x130
0x0900000019DBC664 sqloEDUEntry + 0x390

.....

Waiting on latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) -
Address: (0xa00030000fb7f58), Line: 1366, File:
/view/db2_v105fp5_aix64_s141128/vbs/engn/include/sqlpt_inlines.h
Holding Latch type: (SQLO_LT_preventSuspendIOLotch) - Address:
(0x780000002b17c48), Line: 4595, File: sqleSuspend.C HoldCount:
1
Holding Latch type: (SQLO_LT_sqlpMasterDbcb__suspendLogSem) -
Address: (0xa0003000006f888), Line: 3591, File:
/view/db2_v105fp5_aix64_s141128/vbs/engn/include/sqlpdbcb.h
HoldCount: 1
Holding Latch type: (SQLO_LT_sqeSuspendIOCB__m_suspendIOCBLatch)
- Address: (0x780000002b17d08), Line: 4336, File: sqleSuspend.C
HoldCount: 1
Holding Latch type:
(SQLO_LT_sqeSuspendIOCB__m_pauseRuntimeCleanersLotch) - Address:
(0x780000002b17ce0), Line: 4994, File: sqleSuspend.C HoldCount:
1



(3) The tranEntryLatch is held by another agent executing
ARCHIVE LOG, which is waiting for db2loggw thread to write
log data to disk.


-------Frame------ ------Function + Offset------
0x0900000000113014 thread_wait + 0x94
0x090000001A7A6BCC sqloWaitThreshold + 0x264
0x090000001A7A75E8 sqlpgild__FP9sqeBsuEduP14sqlpMasterDbcbUl +
0x49C
0x090000001A2B3E6C
sqlpWriteToLog__FP8sqeAgentUlN22P14SQLP_LREC_PARTP9SQLP_LSN8PUl
+ 0x197C
0x090000001A2B7E34
sqlpWriteLR__FP8sqeAgentUlN42P14SQLP_LREC_PARTT2P9SQLP_LSN8PUl +
0x19BC
0x0900000019CE8AB4
sqlpWriteLRSingularTran__FP8sqeAgentUlN42P14SQLP_LREC_PARTPUlP9S
QLP_LSN8bN28 + 0xFE8
0x0900000019CE54F8
sqlpWriteLRSingularTran__FP8sqeAgentUlN42P14SQLP_LREC_PARTPUlP9S
QLP_LSN8bN28 + 0xD84
0x0900000016443458
sqlpArchiveLog__FP8sqeAgentP14sqlpMasterDbcbP5sqlca + 0x490

Nested signal handlers detected
.....

Holding Latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) -
Address: (0xa00030000fb7f58), Line: 1366, File:
/view/db2_v105fp5_aix64_s141128/vbs/engn/include/sqlpt_inlines.h
HoldCount: 1



(4) The db2loggw is waiting for glfhLotch held by STOP HADR.
->Back to (1)


-------Frame------ ------Function + Offset------
0x0900000000113014 thread_wait + 0x94
0x090000001A7A89F0 getConflictComplex__17SQLO_SLATCH_CAS64FCUl +
0x298
0x0900000019E25BD8 getConflict__17SQLO_SLATCH_CAS64FCUl + 0xB8
0x090000001A7B69BC
sqlpgWriteToDisk__FP9SQLP_DBCBP9SQLP_LFPBUlbT4T3 + 0x1264
0x090000001A7AC6D4 sqlpgPingPong__FP9SQLP_DBCBP9SQLP_LFPBUlbT3 +
0x400
0x090000001A7AA970 sqlpgwlp__FP9SQLP_DBCBUlT2PC9SQLP_LSN8T2 +
0x384
0x090000001A7A41D8 sqlpLoggwMain__11sqpLoggwEduFv + 0x878
0x090000001B0C2EBC RunEDU__11sqpLoggwEduFv + 0x34
0x090000001AD4C0BC EDUDriver__9sqzEDUObjFv + 0x3F0
0x0900000019DBC664 sqloEDUEntry + 0x390


.....

Waiting on latch type: (SQLO_LT_SQLP_GLFH_VALLOTCH__glfhLotch) -
Address: (0xa000300000758b8), Line: 1653, File: sqlpgwlp.C
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.6.0                              *
****************************************************************
Local Fix:
Do not run these commands at the same time.  In particular,
issue STOP HADR after completing split mirror backup, i.e. after
SET WRITE RESUME.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.6.0                              *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2020
07.07.2021
07.07.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)