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

Microseconds portion in RESOLUTION_TIMESTAMP is always 0

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The microseconds portion of RESOLUTION_TIMESTAMP column in the 
output of COMPILATION_ENV TABLE function is always reported as 
0. For example -- 
 
$ SELECT VARCHAR(NAME, 30), VARCHAR(VALUE, 50) FROM 
TABLE(COMPILATION_ENV((SELECT COMP_ENV_DESC FROM 
TABLE(MON_GET_PKG_CACHE_STMT(NULL, 
x'00000001000000000000000000000001000000000002201307251355586770 
16', NULL, -1)) AS t))) AS s 
 
1                              2 
------------------------------ 
-------------------------------------------------- 
ISOLATION                      CS 
QUERY_OPTIMIZATION             5 
MIN_DEC_DIV_3                  NO 
DEGREE                         1 
SQLRULES                       DB2 
REFRESH_AGE                    +00000000000000.000000 
RESOLUTION_TIMESTAMP           2013-07-25-13.55.58.000000 
FEDERATED_ASYNCHRONY           0 
CURRENT TEMPORAL BUSINESS_TIME 0000-00-00-00.00.00.000000000000 
CURRENT TEMPORAL SYSTEM_TIME   0000-00-00-00.00.00.000000000000 
PATH 
"SYSIBM","SYSFUN","SYSPROC","SYSIBMADM","XXXXXXXX" 
MAINTAINED_TABLE_TYPE          SYSTEM 
 
  12 record(s) selected. 
 
In the above example, the microseconds part in the timestamp 
2013-07-25-13.55.58.000000 is all zeroes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommended to upgrade to DB2 for LUW v97 fixpack 9.         * 
****************************************************************
Local Fix:
available fix packs:
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
The fix is available from v97fp9 onwards.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.07.2013
01.12.2014
01.12.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList