Database connection fails
Installing IBM® Security Guardium® Key Lifecycle Manager on a distributed system creates a user ID for IBM Security Guardium Key Lifecycle Manager with a password that expires according to the local policy on the system, which might set a short span of time, such as 90 days. If the user ID does not exist, the user ID is the same as the Db2® instance name.
CTGKM0506E Internal Database Operation error. CTGKM0900E Database connection failed on data source java:comp/env/jdbc/sklmDS
Use these steps if the Db2 password expires, or you want to reset the password for other reasons, such as a change of administrator:
- Verify that database server is up and running using the following:
set DB2INSTANCE=slkminstance db2start
Where, sklminstance is a value such as
sklmdb2.The database returns an informational message such as:
SQL1026N The database manager is already active.
- Change the password for the IBM Security Guardium Key Lifecycle Manager
- On Windows systems, click Start > Control Panel > Administrative Tools > Computer Management > System Tools > Local Users and Groups > Users.
- Change the password for the IBM Security Guardium Key Lifecycle Manager instance owner.
- Stop related services and change the password. For more information, Updating passwords in IBM Security Guardium Key Lifecycle Manager. On Windows systems, navigate to the services panel by clicking
. Stop the following services:
DB2 - DBSKLMV25 - SKLMDB2 DB2 Governor (DBSKLMV25) DB2 Remote Command Server (DBSKLMV25)
- Restart the instances that you stopped.
- Additionally, stop and restart these services, which run as a
local system account. You must not change their password.
DB2 License Server (DBSKLMV25) DB2 Management Service (DBSKLMV25)
- Log in to the IBM Security Guardium Key Lifecycle Manager graphical user interface and check whether the database status shows as connected.