Operating system of the IBM Security Guardium Key Lifecycle Manager primary master server fails to start
When the operating system of the IBM Security Guardium Key Lifecycle Manager primary master server fails to start, the Agent and primary database are unreachable, and the IBM Security Guardium Key Lifecycle Manager service is down. You must manually initiate the database takeover operation on the standby master server so that the standby database takes over as the primary database.
Solution
Start the takeover operation by running the DB2TakeOver.sh or DB2TakeOver.bat script on the standby master server. This script includes Db2 commands only and does not modify IBM Security Guardium Key Lifecycle Manager.
To start the takeover operation, complete the following steps:
- Locate the DB2TakeOver.sh or DB2TakeOver.bat script.
- Windows
- SKLM_INSTALL_HOME\agent
Default location is C:\Program Files\IBM\GKLMV421\agent.
- Linux®
- SKLM_INSTALL_HOME/agent
Default location is /opt/IBM/GKLMV421/agent.
- Open a command line and run the DB2TakeOver.sh or
DB2TakeOver.bat script.
- Windows
- Go to the SKLM_INSTALL_HOME\agent directory and run the
following
command:
where, LOG is the log file path, DB_NAME is the Db2 database name, and INST_HOME is the Db2 instance home.DB2TakeOver.bat LOG DB_NAME INST_HOME
- Linux
- Go to the SKLM_INSTALL_HOME/agent directory and run the
following
command:
where, LOG is the log file path, DB_NAME is the Db2 database name, and INST_HOME is the Db2 instance home.DB2TakeOver.sh LOG DB_NAME INST_HOME
The Db2 database on the standby master server takes over as the primary database.
When the operating system of the earlier primary database server recovers, initiate the takeover service on it as standby.