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 IC79485 Status: Closed

THE DBMS_UTILITY.GET_CPU_TIME() FUNCTION RETURNS INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The function DBMS_UTILITY.GET_CPU_TIME() returns invalid results 
on the Unix and Linux platforms
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Unix/Linux platforms                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The function DBMS_UTILITY.GET_CPU_TIME() returns invalid     * 
* results                                                      * 
* on the Unix and Linux platforms                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the fix pack V97FP6                               * 
****************************************************************
Local Fix:
Use the OS tools to get the cpu time
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
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.10.2011
07.06.2012
07.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 FixList