Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-10195: How to enable Centrify DB2 plugin caching?

19 April,18 at 11:49 PM

Question:

Centrify DB2 plugin can be configured to use the in-process memory CAPI cache which would greatly improve performance with Active Directory user and group lookups.  But how do we enable the CAPI cache?

Answer:

To enable the CAPI cache, set  the following parameter to 'true' in /etc/centrifydc/centrifydc.conf file.  Default is disabled, 'false'

capi.cache.enabled: true

There are a few more parameters that can be configured to further tune the DB2 plugin CAPI cache.  The listed values are the defaults.

This configuration parameter specifies the number of seconds that a positive cached object remains in the in-memory CAPI cache before it is refreshed. This parameter takes effect only if the inmemory CAPI cache is enabled.

capi.cache.ttl: 3600

This configuration parameter specifies the number of seconds that a negative cached object remains in the in-memory CAPI cache
before it is refreshed. This parameter takes effect only if the in-memory CAPI SID cache is enabled.

capi.cache.negative.ttl: 3600

This configuration parameter specifies the maximum number of objects that are kept in the in-memory CAPI cache if the cache is
enabled. If the number is exceeded, cached objects that are the oldest are replaced with new objects.

capi.cache.max.objects: 10000

This configuration parameter specifies the number of hash map buckets that are allocated if the in-memory CAPI cache is enabled.

capi.cache.hash.table.size: 769

Please note that after a change to any of the above parameters, DB2 instance needs to be restarted to take effect.
 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-6191: Centrify DB2 plug-in compatibility with DB2 10.5.x version articleKB-0547: How to Collect Debug Logs from a DB2 server with the Centrify App Server Plug-in articleKB-3925: How to add Centrify parameter to a group policy articleKB-5877:Unable to access DB2 database with TOAD after installing Centrify DB2 module articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-4343: Could not load module /usr/share/centrifydc/kerberos/lib64/libgssapi_krb5.a(shr. o.2.2) articleKB-8905: Significantly slow DB2 transaction times when using the Centrify DB2 plugin articleKB-1956: SQL30082N Security processing failed with reason "15" ("Processing Failure"). articleKB-4633: Using Centrify and Kerberos keytabs to authenticate a script or to DB2 without a password