|
Problem IT36461
|
Status: Closed |
ACTIVATE DATABASE ON ONE MEMBER IN PURESCALE HUNG WHEN ANOTHER MEMBER IS EXECUTING CREATE INDEX ON HADR PRIMARY DATABASE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
This problem only affects HADR database in pureScale
environment.
One of the member X in the HADR primary cluster is shut down due
to planned or unplanned outage. The primary database is
functioning normally on another member Y, with a CREATE INDEX
operation is executing.
The activation of database on member X might hang, with the
following stack:
0x090000000EE2C634
sqlplWaitOnWP__FCP9sqeBsuEduCP14SQLP_LOCK_INFOCP8SQLP_LRBCP15SQL
P_LTRN_CHAINCbN25 + 0x4EF4
0x0900000015D2F36C
sqlplMakeNewRequestSD__FP9sqeBsuEduP14SQLP_LOCK_INFOP11SQLP_TENT
RYRP8SQLP_LRBP8SQLP_LRBP15SQLP_LTRN_CHAINbT7CbN29 + 0x316C
0x090000000EDA7590 sqlplrq__FP9sqeBsuEduP14SQLP_LOCK_INFO +
0x2AD0
0x0900000014762A98
sqlpInitLogStreamLock__FP8sqeAgentP9SQLP_DBCBP5sqlca + 0x298
0x090000001476400C sqlpInitLockingComponents__FP8sqeAgentP5sqlca
+ 0x16C
0x0900000014765640
sqlpinit__FP8sqeAgentP16sqeLocalDatabaseP5sqlcaUl + 0x640
0x090000000ED172BC
sqledint__FP8sqeAgentP16sqeLocalDatabaseP5sqlcacPciPbUl + 0xE9C
0x090000000ED24B24
FirstConnect__16sqeLocalDatabaseFP8SQLE_BWARcP8sqeAgentP8sqlo_gm
tiT5Pb + 0x3F64
0x090000000F216B70
StartUsingLocalDatabase__8sqeDBMgrFP8SQLE_BWAP8sqeAgentRccP8sqlo
_gmtPb + 0x3F30
0x090000000F969200
AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc
+ 0xF80
0x090000000F988264
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x30A4
0x090000000F1F7404 sqlelostWrp__FP14db2UCinterface + 0x44
The following stack can be seen on member Y that is the cause of
of the hang on member X:
0x0900000015F51C98 sqloXlatchConflict + 0x8F8
0x09000000168E1020
registerLocalView__19sqlpDbcbsGlobalViewFP15sqlpDbcbsHandleP9sqe
BsuEduPvCUiCl + 0x820
0x09000000168E450C
createLocalView__15sqlpDbcbsHandleFP9sqeBsuEduCUiPvCl + 0x42C
0x0900000017AC83BC
sqlpLogStreamReclaimLock__FP9sqeBsuEduP24SQLP_LLM_NEGOTIATE_ENTR
YPb + 0xFC
0x090000001D208C88
sqlpLLMNegotiateThread__FP9sqpLLMEduP9SQLP_DBCBP8SQLP_LCB +
0x3748
0x0900000016617940 RunEDU__9sqpLLMEduFv + 0x3C0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* AIX/LINUX *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v115m6fp0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* AIX/LINUX *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v115m6fp0 *
**************************************************************** |
| Comment |
Upgrade to db2_v115m6fp0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.04.2021
09.06.2021
09.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
