|
Problem IC96361
|
Status: Closed |
DB2 WSE : DB2LICM -G OUTPUT SHOULD DISPLAY A VIOLATION WHEN COMPRESSION IS USED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
With DB2 Worgroup Server Edition, index and table compression is
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 WSE *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
19.09.2014
19.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
