DB2 - Problem description
Problem IC62055 | Status: Closed |
TRY AND BUY LICENSE MAY INCORRECTLY GENERATE AN ERROR MESSAGE FOR SOME FEATURES DURING THE VALID PERIOD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
During the period that the Try and Buy license is valid, it may generate an error when certain features that require an additional license are used. An example of this is the storage optimization feature. Using this feature (Create table with COMPRESSION YES or a subsequent index on that compression enabled table) will result in a message in the db2diag.log. Example message: 2009-06-19-10.55.21.273637-240 E45159A1045 LEVEL: Error PID : 19444 TID : 154 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-2037 APPID: LOCAL.*.090619145520 AUTHID : DB2INST1 EDUID : 154 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:9 MESSAGE : ADM12024E A valid license key was not found for the requested function. The current license key for "DB2 Storage Optimization Feature" product does not allow the requested functionality. Purchase the license key for this function from your IBM representative or authorized dealer and update your license using the License Center or the db2licm command line utility. For more information on updating licenses refer to the Quick Beginnings manual for your platform. For more information on the db2licm utility, refer to the DB2 Command Reference. | |
Problem Summary: | |
Users Affected: Any using the Try and Buy license Problem Description: During a valid Try and Buy license period, some features may return a license error. Problem Summary: see above. | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 FixPak 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.07.2009 28.12.2009 28.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |