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

SETTING HARD-STOP POLICY FOR EXPRESS-C HAS NO EFFECT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After setting hard-stop policy for Express-C,  features normally 
unavailable in Express-C such as "Row Level Compression" and 
"Multidimensional clustering" can still be used. 
 
Even though the features can be used in error,  they will still 
trigger license violations to be written to the license 
compliance 
report.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V9.7 FixPack 4 or below.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After setting hard-stop policy for Express-C,  features      * 
* normally                                                     * 
* unavailable in Express-C such as "Row Level Compression" and * 
*                                                              * 
* "Multidimensional clustering" can still be used.             * 
*                                                              * 
*                                                              * 
*                                                              * 
* Even though the features can be used in error,  they will    * 
* still                                                        * 
* trigger license violations to be written to the license      * 
*                                                              * 
* compliance                                                   * 
*                                                              * 
* report.                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FixPack 5 or higher.                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
Problem first fixed in DB2 V9.7 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2011
07.12.2011
07.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList