db2 connections are causing CPU usage spikes by the vasd. (4248909)

The db2 connections take between 9 and 30 seconds.

The vasd on the server is using up to 50% of the CPU ability.

The issue has become more noticeable as connection requests have increased.

Many connection requests per second from the same account.

See what is showing for db2set.

" db2set:
(/opt/udb/home/pdbin170) 132: db2set
DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
DB2_EVMON_STMT_FILTER=BPDS_BIIPODSP_0
DB2_ENABLE_AUTOCONFIG_DEFAULT=NO
DB2AUTH=OSAUTHDB
DB2_ALTERNATE_GROUP_LOOKUP=GETGRSET
DB2_EVALUNCOMMITTED=ON
DB2_SKIPDELETED=ON
DB2COMM=TCPIP
DB2_PARALLEL_IO=*
DB2AUTOSTART=NO

In this particular case adding the following resolved the issue:

db2set DB2_NUM_CKPW_DAEMONS=10:FORK

Use the DB2_NUM_CKPW_DAEMONS registry variable to start a configurable number of check password daemons. The daemons are created during db2start and handle check password requests when the default IBMOSauthserver security plugin is in use. Increasing the setting for DB2_NUM_CKPW_DAEMONS can decrease the time required to establish a database connection, but this is only effective in scenarios where many connections are being made simultaneously and where authentication is expensive.

Example:

db2set DB2_NUM_CKPW_DAEMONS=3:FORK