DB2 - Problem description
Problem IC80198 | Status: Closed |
System controller EDU (DB2SYSC) held up due to contention for th e FCM dynamic update latch causes apparent performance slowdown. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
Multiple logical nodes on the same machine share the same FCM resource pools. The system controller EDU (db2sysc) on each logical node wakes up periodically to determine if FCM resource tuning is necessary. The system controller EDUs contend for the FCM dynamic update latch(m_dynUpdateLatch) in order to perform the tuning. The remaining system controller EDUs and agent EDUs can end up waiting for the latch until tuning completes and the latch is released. This can lead to performance slowdowns. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DPF, MPP * **************************************************************** * PROBLEM DESCRIPTION: * * Multiple logical nodes on the same machine share the same * * FCM resource pools. The system controller EDU (db2sysc) on * * each logical node wakes up periodically to determine if FCM * * resource tuning is necessary. The system controller EDUs * * contend for the FCM dynamic update latch(m_dynUpdateLatch) * * in order to perform the tuning. The remaining system * * controller EDUs and agent EDUs can end up waiting for the * * latch until tuning completes and the latch is released. This * * can lead to performance slowdowns. * **************************************************************** * RECOMMENDATION: * * Update to version 9.1 fixpack 12 or later fixpacks. * **************************************************************** | |
Local Fix: | |
Solution | |
This problem is first fixed in version 9.1 fixpack 12. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.12.2011 17.07.2012 17.07.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP12 | |
Problem solved according to the fixlist(s) of the following version(s) |