Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC94387 Status: Geschlossen

Microseconds portion in RESOLUTION_TIMESTAMP is always 0

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommended to upgrade to DB2 for LUW v10.1 FP3.             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Fix first available from v10.1 fixpack 3 onwards.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC94396 IC94397 IC95500 IC95543 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.07.2013
27.09.2013
27.09.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList