DB2 - Problem description
Problem IC76890 | Status: Closed |
First db2start may fail with SQL1042 after reboot on RHEL6 system | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On Linux RHEL6 64b machine , db2start might fail with SQL1042 . The inspection of db2diag.log shows up the following error messages: 2011-03-16-08.33.34.866971-240 I9773E357 LEVEL: Severe PID : 31293 TID : 140328380831520PROC : db2star2 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:580 MESSAGE : ECF=0x900003DE=-1879047202=ECF_TRCAPI_MUTEX_LOCK_ERROR Trace facility mutex unexpected lock error Additional background about the error: The problem occurs because RHEL6 has low default IPC kernel parameters. During starting an instance, on Linux db2 increases the required IPC kernel parameters , but this increase occurs relatively late in the startup cycle and doesn't affect all created IPC resources . The second attempt to start an instance uses the new increased the IPC kernel parameters and it fixes the issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Linux 64b only , RHEL6 in particular * **************************************************************** * PROBLEM DESCRIPTION: * * On Linux RHEL6 64b machine , db2start might fail with * * SQL1042 . * **************************************************************** * RECOMMENDATION: * * The second attempt to start the instance should fix the * * issue * **************************************************************** | |
Local Fix: | |
Several fixes are possible: a. Before starting up an instance , preset SHMMAX kernel parameter to 256MB b. A second attempt of db2start would fix the issue | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC76895 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.06.2011 27.03.2012 27.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |