DB2 - Problem description
Problem IT18611 | Status: Closed |
ACTIVATE DATABASE MIGHT HANG WHEN LOGARCHMETH1 IS TURNED OFF | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The database activation might hang when the following conditions occur at the same timing. - The db cfg LOGARCHMETH1/2 are turned off - An internal counter in LFH file is wrapped When this hang occur, db2agent is waiting for db2loggr as follows: thread_wait sqloWaitEDUWaitPost sqlpgint sqlpinit sqledint FirstConnect StartUsingLocalDatabase AppStartUsing AppLocalStart sqlelostWrp sqleUCengnInit sqleUCagentConnect ... db2loggr is waiting for db2logmgr, but db2logmgr does not exist since the database is now using circular logging: thread_wait sqloWaitEDUWaitPost sqlpgPostLogManager sqlpgInitRecoverable sqlpgLoggrInit sqlpgasn sqloEDUEntry This is a timing dependent problem. Users cannot check the internal counter value, but the IBM support can check it by formatting LFH files. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
To avoid the hang after the coditions are met, please set LOGARCHMETH1/2 once and activate the database. Once the activation is done, you can turn off LOGARHMETH1/2. | |
Solution | |
First fixed in DB2 10.1 Fix Pack 6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.12.2016 02.03.2017 02.03.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |