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 IC67679 Status: Geschlossen

SQL0802 - FMOD() RETURNS NAN ON WINDOWS PLATFORM

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
On Windows platform, sometimes query can hit sql0802 because 
fmod() returns NaN though data is in valid range, and re-run the 
query may not hit the error. Analysis shows Intel compiler links 
fmod() from Microscoft's library instead of Intel's libmmds.lib.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows platform                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL0802 - FMOD() RETURNS NAN ON WINDOWS PLATFORM             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.5 Fix Pack  6                   * 
****************************************************************
Local-Fix:
Re-run query
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.5 Fix Pack 6
Workaround
see LOCAL FIX
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67731 IC67732 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.04.2010
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.,
9.5.FP6
Problem behoben lt. FixList in der Version