DB2 - Problem description
Problem IC73551 | Status: Closed |
DB2 MAY FREQUENTLY GET DUPLICATED CURRENT TIMESTAMP VALUES WITH FIXPAK 3 ON SOLARISPLATFORM | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
DB2 may frequently get duplicated current timestamp values with v9.7 FixPak 3 on Solaris platform, especially on a busy multiple CPU system. It can cause failure (sql0803n) of inserting into table with unique timestamp column, for example, failure of inserting into explain_instance table. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Solaris platform * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 may frequently get duplicated current timestamp values * * with v9.7 FixPak 3 on Solaris platform, especially on a busy * * multipleCPU system. It can cause failure (sql0803n) of * * inserting into table with unique timestamp column, for * * example, failure of inserting into explain_instance table. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 9.7 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
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 : | 28.12.2010 02.05.2011 02.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 |