home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC72361 Status: Closed

SQL Queries accessing table WLM_EVENT may fail with an error SQL0443N"
SYSFUN.TIMESTAMPDIFF".

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
WLM functionalities related queries involving the table 
WLM_EVENT may fail with error in the function timestampdiff with 
message SYSFUN:07. This error can occur due to inconsistent 
values of timestamps between TIME_CREATED, TIME_STARTED and 
TIME_COMPLETED. 
 
We can see there two different behaviors : 
 
- 1. the microsecond part of one of columns TIME_COMPLETED, 
TIME_STARTED or TIME_CREATED is 000000 and one of the time 
intervals is too large or too short by 1 second, 
- 2. the value of TIME_STARTED is equal to the timestamp of the 
activation of the database by the first connect. 
 
In such cases, following error occurs: 
 
SQL0443N  Routine "SYSFUN.TIMESTAMPDIFF" (specific name 
 
"TIMESTAMPDIFF") has 
 
      returned an error SQLSTATE with diagnostic text 
"SYSFUN:07". 
SQLSTATE=38552 
 
 (State:38552, Native Code: FFFFFE45)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to DB2 V97 FP4.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL Queries accessing table WLM_EVENT may fail with an error * 
* SQL0443N" SYSFUN.TIMESTAMPDIFF".                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 to V97 FP4.                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 is first fixed in DB2 V97 FP4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.11.2010
09.05.2011
09.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 FixList