DB2 - Problem description
Problem IC96996 | Status: Closed |
IN DB2 GATEWAY, WHEN REMOTE NODE IS CATALOGED WITH SSL ENABLED, MEMORY FOOTPRINT PER CONNECTION IS IMPACTED BY KEY DATABASE SIZE | |
product: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problem description: | |
In DB2 Gateway, when SSL is enabled (SECURITY SSL) for communication with remote node, memory footprint per connection is impacted by key database size. You may verify that by checking security type in node directory (LIST NODE DIRECTORY) and size of key database (SSL_CLNT_KEYDB) in database manager configuration. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 Fix Pack 10 or higher. * **************************************************************** | |
Local Fix: | |
In order to reduce the key database size, verification of certificates stored there may be considered. It can be done by issuing: $DB2_HOME/gskit/bin/gsk8capicmd_64 -cert -list all -db <patch_to_key_db> Removal of those, which are not required in given environment, can be done with the same command using the -delete switch . By default GSKit version 7 populates created database with a number of predefined trusted CA certificates (in version 8 you need to specify -populate switch), | |
Solution | |
Fixed in DB2 version 9.7 Fix Pack 10. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC97236 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.10.2013 10.11.2014 10.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |