home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT06270 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The event monitor creates tables with compression by default 
even when the license is not there for 
DB2_STORAGE_OPTIMIZATION_FEATURE.
Problem-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
The customer should upgrade to DB2 V10.1 FP5 to avail the fix.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.12.2014
29.07.2015
29.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList