IV68351: DB2IUPDT TRIGGERED APPLYING ESE BASE LICENSE UNEXPECTEDLY AND RESULT IN LICENSE INFORMATION LOST IN PURESCALE ENVIRONMENT

DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 10 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 11 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• When calling db2iupdt to operate remote host, it will apply ESE
  base license unexpectedly and result in the following output:
  
  db2licm -l
  Product name: "DB2 Enterprise Server Edition"
  License type: "License not registered"
  Expiry date: "License not registered"
  Product identifier: "db2ese"
  Version information: "10.5"
  
  In fact, a valid AESE license was already applied before that:
  
  db2licm -l
  Product name:                     "DB2 Advanced Enterprise
  Server Edition"
  License type:                     "CPU Option"
  Expiry date:                      "Permanent"
  Product identifier:               "db2aese"
  Version information:              "10.5"
  Enforcement policy:               "Soft Stop"
  
  This issue happens in purescale environment where a special
  build is applied.
  

Local fix

• 1) apply the valid AESE license again
  or
  2) before installing special build, copy the valid AESE license
  file e.g. db2aese_c.lic into
  <special_build_image>/server/db2/license and rename it as
  db2ese.lic.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * User who use db2 v10.5 with purescale feature                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to db2 v10.5 fp6 or above                            *
  ****************************************************************
  

Problem conclusion

• The problem is first fixed in v10.5 fp6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 PURESCALE F

• Fixed component ID

  5724Y6900

Applicable component levels