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

SQL0802 - FMOD() RETURNS NAN ON WINDOWS PLATFORM

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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
available fix packs:
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

Solution
Problem was first fixed in Version 9.5 Fix Pack 6
Workaround
see LOCAL FIX
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67731 IC67732 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.04.2010
10.06.2010
10.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.,
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)