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

THE DB2 EVENT MONITOR TABLES REPORTS VIOLATION FOR "DB2 STORAGE
OPTIMIZATION" EVEN THOUGH THERE IS NO LICENSE FOR DB2_STORAGE_OP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The event monitor creates tables with compression by default 
even when the license is not there for 
DB2_STORAGE_OPTIMIZATION_FEATURE.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on DB2 LUW GA -FP4                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* As a work around, run the below command to disable the       * 
* compression:                                                 * 
* db2 alter table <tabname> compress no and then, reset the    * 
* license with db2licm -x to generate a compliance report.     * 
****************************************************************
Local Fix:
Run the below command to disable the compression: 
db2 alter table <tabname> compress no and then, reset the 
license with db2licm -x to generate a compliance report.
Solution
The customer should upgrade to DB2 V10.1 FP5 to avail the fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.12.2014
29.07.2015
29.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList