DB2 - Problem description
Problem IT22604 | Status: Closed |
DB2START MIGHT HANG IN TRCATTACHSHARED() ON THE SYSTEM WITH LOW SHARED MEMORY SEGMENT SIZE LIMIT (SHMMAX) | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
On the system where shared memory segment size limit is low, DB2 start might hang trying to allocate the DB2 trace memory segment. db2star2 (executed as a part of db2start) will get stuck in: #0 in semop () #1 in sharedMutexLock(int) #2 in sharedAttach(TRC_SHARED_IPC_INFO_T*, bool) #3 in trcAttachShared () #4 in internalProcessTraceInit #5 in sqltinit () #6 in DB2StartMain () #7 in main () Issue might happen when the size of default trace buffer (32 MB on Linux, 128 MB on AIX, can be overridden up to 1024 MB using DB2TRC_DEF_BUFFSIZE variable) is more than 8x higher than current limit for shared memory segment size (shmmax). Problem is most likely to happen on Linux. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
Interrupt db2start, remove all IPC resources owned by DB2 instance owner: $ ipcrm -s Adjust shared memory limits, e.g on Linux: $ sysctl -w kernel.shmmax= (details for other platforms in DB2 documentation) and run db2start again. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16315 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.10.2017 24.10.2017 24.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |