DB2 - Problem description
Problem IC68778 | Status: Closed |
DATABASE CONNECT AND SNAPSHOT TIMES DEGRADE DUE TO TIMESTAMP GENERATION WHEN DATABASE IS SERIALIZED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On some platforms, the generation of a timestamp can be a relatively expensive operation to perform. Some timestamps are generated while the database is serialized when new connections are arriving or when a database snapshot is being performed. The timestamp generation can cause these serialization periods to last longer and lead to contention that can cause database applications to be delayed. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * On some platforms, the generation of a timestamp can be a * * relatively expensive operation to perform. Some timestamps * * are * * generated while the database is serialized when new * * connections * * are arriving or when a database snapshot is being performed. * * The * * timestamp generation can cause these serialization periods * * to * * last longer and lead to contention that can cause database * * applications to be delayed. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.05.2010 03.05.2011 03.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |