DB2 - Problembeschreibung
Problem IC86439 | Status: Geschlossen |
DB2LICM -L OUTPUT IS NOT LISTING THE DB2 STORAGE OPTIMIZATION FEATURE LICENSE FOR RESTRICTED SERVER EDITIONS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
For DB2 restricted Server Editions, eventhough the DB2 Storage Optimization feature license(db2so.lic) gets added successfully, its not showing up in db2licm -l output. As of V9.7 FP3a, customers who are entitled to a limited-use copy of DB2 through other IBM software can also purchase the Storage Optimization Feature. They no longer have to first purchase a full use edition of DB2. Example: ---------- C:\Program Files\IBM\SQLLIB\BIN>db2licm -l show detail Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "10.1" Features: DB2 pureScale: "Not licensed" Product identifier: "db2dsf" Expiry date: "Expired" C:\Program Files\IBM\SQLLIB\BIN>db2licm -a db2so.lic LIC1402I License added successfully. C:\Program Files\IBM\SQLLIB\BIN>db2licm -l show detail Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "10.1" Features: DB2 pureScale: "Not licensed" Product identifier: "db2dsf" Expiry date: "Expired" | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 10.1 FP3 or later * **************************************************************** | |
Local-Fix: | |
Lösung | |
Upgrade to 10.1 FP3 or later | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.09.2012 10.10.2017 10.10.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |