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

DB2 WSE : DB2LICM -G OUTPUT SHOULD DISPLAY A VIOLATION WHEN COMPRESSION IS
USED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
With DB2 Worgroup Server Edition, index and table compression 
are 
not allowed but if you have your enforcement policy set to 
soft-stop and create an index or a table with compress on, the 
compliance report generated with the command db2licm -g output 
doesn't show the violation
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Workgroup Server Edition                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP9 or later                              * 
****************************************************************
Local Fix:
available fix packs:
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 was first fixed in 9.7 FP9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96361 IC96686 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.05.2013
23.12.2013
23.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList