|
Problem IC81639
|
Status: Closed |
ON LINUX PLATFORMS, DB2 FCM THREADS (DB2FMCS AND DB2FCMR) MAY HANG IN SELECT() SYSTEM CALL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On Linux Platforms, DB2 FCM threads (db2fmcs and db2fcmr) may
hang in select() system call due to possibly reaching file
descriptor limit . The symptom would be hard to confirm via a
stack trace of the FCM threads since the stack generation tools
(db2pd -stack, pstack, gstack, gcore) will all clear up the
hang.
With this APAR db2fcm (s and r) threads will have the ability
to use epoll() instead of select() since epoll() does not have
the file descriptor limit that select() has. This change will
not be by default but instead enabled via a registry variable -
DB2_FCM_FDPOLL. The default for this registry variable will be
FALSE on Linux. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Users in Linux DPF environments *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fixpack 6 or later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem has been fixed in DB2 Version 9.7 Fixpack 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC81657 IC84433
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.02.2012
27.06.2012
27.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
