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

"DB2LICM -L" DOES NOT REPORT THE DATABASE PARTITIONING LICENSE
EVEN AFTER THAT LICENSE HAS BEEN APPLIED (USING DB2DPF.LIC)

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When you run the command "db2licm -l" the output ought to say 
what DB2 licenses have been applied. 
But because of this defect the output does not report the DB2 
Database Partitioning license even after that license has been 
applied (using the license file db2dpf.lic). 
 
With this APAR fix, after the DB2 Database Partitioning license 
has been applied and you run the command "db2licm -l" the output 
will include the line: 
 DB2 Database Partitioning:        "Licensed" 
 
(The DB2 Database Partitioning Feature is sometimes called DPF 
for short.)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 10.1 Fix Pack 3 
At a minimum, this fix should be applied on the server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList