After applying DB2 version 10.5.0.4, DB2 users might experience
performance degradation and dropped database connections due to
intermittent license errors in their application. The problem
occurs despite having a valid DB2 Server license. It is more
likely to occur with high number of concurrent connections. The
application may fail with SQL code SQL8001N or SQL8027N.
Administration messages ADM12008C and/or ADM12024E may be
written to the db2diag.log and the administration log.
The db2diag.log might include one or more of the of the
following messages:
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 Advanced
Workgroup Server Edition" 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 db2licm command.
OR
FUNCTION: DB2 UDB, base sys utilities,
sqeApplication::AppStartUsing, probe:10
RETCODE : ZRC=0xFFFFE0BF=-8001
SQL8001N An attempt to connect to the database failed
due to a product license problem.
OR
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:2
MESSAGE : ADM12008C The product "" does not have a valid
license key installed and the evaluation period has expired.
Functions specific to this product are not enabled. If you have
licensed this product, ensure the license key is properly
installed. You can install the license using the db2licm
command. The license file can be obtained from your licensed
product CD.
When applications receive an SQL8027N error with valid license,
the db2diag.log might not have any error messages. However, a
db2trc flow would show the following:
sqlnp_parser entry [eduid 4856 eduname db2agent]
| sqlnp_smactn mbt [Marker:PD_SQNP_REDUCTION ]
| | sqlnq_table_options entry [eduid 4856 eduname db2agent]
| | | sqloLicRequestAccess entry [eduid 4856 eduname db2agent]
| | | sqloLicRequestAccess data [probe 1]
| | | | sqllcRequestAccess entry [eduid 4856 eduname db2agent]
| | | | sqllcRequestAccess data [probe 1]
| | sqlnq_table_options exit [rc = 0xFFFFE0A5 = -8027]
Similarly for SQL8001N, the db2diag.log might not have any error
messages. However, a db2trc flow would show the following:
sqljsDrdaAsDriver entry [eduid 3571 eduname db2agent]
| sqljsDrdaAsInnerDriver entry [eduid 3571 eduname db2agent]
| | sqljsDriveRequests entry [eduid 3571 eduname db2agent]
| | | sqljsSqlam entry [eduid 3571 eduname db2agent]
| | | | sqljsParse entry [eduid 3571 eduname db2agent]
| | | | | sqljsParseConnect entry [eduid 3571 eduname db2agent]
| | | | | | sqljs_ddm_accsec entry [eduid 3571 eduname db2agent]
| | | | | | | sqljsConnectAttach entry [eduid 3571 eduname
db2agent]
| | | | | | | | sqleUCagentConnect entry [eduid 3571 eduname
db2agent]
| | | | | | | | | sqleUCengnInit entry [eduid 3571 eduname
db2agent]
| | | | | | | | | | sqeApplication::AppLocalStart entry [eduid
3571 eduname db2agent]
| | | | | | | | | | | sqleProcessConnectType entry [eduid 3571
eduname db2agent]
| | | | | | | | | | | | sqeApplication::AppStartUsing entry
[eduid 3571 eduname db2agent]
| | | | | | | | | | | | | sqleValidateLicence entry [eduid 3571
eduname db2agent]
| | | | | | | | | | | | | sqleValidateLicence exit [rc =
0xFFFFE0BF = -8001]
When applications are facing this issue they may see severe
performance degradation. Taking db2pd -latches during this time
will show several license latches like this:
0x0780000000465840 497056 151894 sqllcinit.C
1694 SQLO_LT_SqlcLickrcb__lic_change_latch 1 |
