|
Problem IC96702
|
Status: Closed |
UPDATING LOGARCHMETH1 DATABASE CONFIGURATION PARAMETER WHILE A DATABASE IS BEING ACTIVATED CAN CAUSE DB2 TO HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Updating LOGARCHMETH1 database configuration parameter while a
database is being activated can cause DB2 to hang. db2pd -latch
reports deadlatch between latches
SQLO_LT_SQLE_KRCB__cfg_change_latch and
SQLO_LT_sqeDBMgr__dbMgrLatch.
Here are stack trace examples:
sqloXlatchConflict
sqlpglhu
sqlfgtlp
sqlfVerifyLogArchMeth
sqlf_upd_parm
sqlf_upd_parm
sqlfUpdateDbCfg
sqlfDispatchDbCfgUpdate
sqlfudb_backend
sqlfudb_backend
sqlesrvr
sqleMappingFnServer
sqlerKnownProcedure
sqlerCallDL
..(snip)..
<LatchInformation>
Waiting on latch type: (SQLO_LT_sqeDBMgr__dbMgrLatch) - Address:
(7800000005701e8), Line: 395, File: sqlpglhu.C
Holding Latch type: (SQLO_LT_SQLE_KRCB__cfg_change_latch) -
Address: (7800000002a65a0), Line: 3227, File: sqlf_db_op.C
HoldCount: 1
</LatchInformation>
sqloXlatchConflict
sqlfUpdateDbCfg
FirstConnect
StartUsingLocalDatabase
AppStartUsing
AppLocalStart
sqlelostWrp
sqleUCengnInit
sqleUCagentConnect
sqljsConnectAttach
..(snip)..
<LatchInformation>
Waiting on latch type: (SQLO_LT_SQLE_KRCB__cfg_change_latch) -
Address: (7800000002a65a0), Line: 3227, File: sqlf_db_op.C
Holding Latch type: (SQLO_LT_sqeDBMgr__dbMgrLatch) - Address:
(7800000005701e8), Line: 670, File: sqle_database_services.C
HoldCount: 1
</LatchInformation> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
