|
Problem IC72892
|
Status: Closed |
CONNECT ERROR DB21018E TO Z/OS MACHINE from a DB2 Client due to license verification issue. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Having more then 20 Z/OS data sources cataloged on a client may
cause connection to fail with error DB21018E due to a license
verification issue. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CONNECT ERROR DB21018E TO Z/OS MACHINE from a DB2 Client due *
* to *
* license verification issue. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Having more then 20 Z/OS data sources cataloged on a client *
* may *
* cause connection to fail with error DB21018E due to a *
* license *
* verification issue. *
****************************************************************
* RECOMMENDATION: *
* First fixed in fix pack 4 of v9.7 *
**************************************************************** |
| Local Fix: |
1) Catalog less then 20 Z/OS data sources on the client.
2) If there are more than 20 catalog entries, but cached value
is less then 20 you will not see DB21018E error.
In order to clear the entries in cache so that there are only 20
connections, you can remove conlic.bin file from
~/sqllib/cfgcache to clean the connect license cache. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in fix pack 4 of v9.7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.11.2010
05.04.2011
07.04.2011 |
| 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.4
|
 |
