Here is a quick procedure on how to drop a TSM instance on a TSM server. There are various reasons why you might need to remove a TSM instance, such as repurposing the TSM server or rectifying issues arising from misconfigurations with DB2. In my personal experience, I have often dropped TSM instances due to errors made during TSM instance creation.
Step 1. Back up TSM instance user’s home folder
To ensure a complete backup of the TSM instance user folder, Copy all files located within the root of the TSM home user folder to somewhere else. Below is the sample output of the TSM instance tsmsvr01‘s home user folder. You might need some important files later though such as dsmserv.opt and cert256.arm (SSL certificate) I have copied them to /opt/tivoli/tsmsvr01_old/
my_tsmsvr01:[root]/tsm>ls -rlt /opt/tivoli/tsmsvr01 total 88 drwxr-xr-x. 6 30096 tsmsrvrs 58 Mar 23 23:44 tsmlog drwxr-xr-x. 6 30096 tsmsrvrs 54 Mar 23 23:44 tsmdb -rw-------. 1 30096 tsmsrvrs 80 Mar 23 23:44 cert.rdb -rw-------. 1 30096 tsmsrvrs 80 Mar 23 23:44 cert.crl -rw-------. 1 30096 tsmsrvrs 193 Mar 23 23:44 cert.sth -rw-------. 1 30096 tsmsrvrs 5080 Mar 23 23:44 cert.kdb -rw-r--r--. 1 30096 tsmsrvrs 1257 Mar 23 23:44 cert256.arm drwxrwxr-x. 3 30096 tsmsrvrs 22 Mar 23 23:44 tsmsvr01 -rw-r-----. 1 30096 tsmsrvrs 27 Mar 23 23:45 dsmserv.dbid -rw-r--r--. 1 30096 tsmsrvrs 29 Mar 23 23:47 tsmdbmgr.opt -rw-r--r--. 1 30096 tsmsrvrs 0 Mar 23 23:47 cit.log -rw-r--r--. 1 30096 tsmsrvrs 10878 Mar 23 23:47 citScanOutput.xml -rw-------. 1 30096 tsmsrvrs 193 Mar 23 23:47 dsmkeydb.sth -rw-------. 1 30096 tsmsrvrs 3358 Mar 23 23:47 dsmkeydb.kdb -rw-r-----. 1 30096 tsmsrvrs 377 Mar 23 23:48 NODELOCK -rw-r--r--. 1 30096 tsmsrvrs 864 Mar 23 23:48 dsmserv.opt -rw-r--r--. 1 30096 tsmsrvrs 0 Mar 23 23:52 tsmdbmgr.log drwxr-xr-x. 3 30096 tsmsrvrs 29 Mar 23 23:52 IBM -rw-r--r--. 1 30096 tsmsrvrs 0 Mar 24 00:01 dsminstr.log.lock -rw-r--r--. 1 30096 tsmsrvrs 9197 Mar 24 00:01 dsminstr.log -rw-------. 1 30096 tsmsrvrs 240 Mar 24 00:02 devconfig.out -rw-r-----. 1 30096 tsmsrvrs 412 Jul 14 12:38 dsmffdc.log -rw-------. 1 30096 tsmsrvrs 946 Jul 14 12:38 volhistory.out drwxr-x---. 2 30096 tsmsrvrs 4096 Jul 14 12:47 srvmon my_tsmsvr01:[root]/tsm>cp /opt/tivoli/tsmsvr01/* /opt/tivoli/tsmsvr01_old/
Step 2. Drop DB2 Instance (TSM Instance)
Note the command below. Ensure that you execute the following command using the root user ID.
/opt/tivoli/tsm/db2/instance/db2ilist <-- List TSM instance name configured on IBM DB2 /opt/tivoli/tsm/db2/instance/db2idrop [TSM_Instance_Name] <-- Drop TSM instance from IBM DB2
Refer to the below command output of dropping TSM server instance.
my_tsmsvr01:[root]/tsm> my_tsmsvr01:[root]/tsm>/opt/tivoli/tsm/db2/instance/db2ilist tsmsvr01 my_tsmsvr01:[root]/tsm> my_tsmsvr01:[root]/tsm>/opt/tivoli/tsm/db2/instance/db2idrop tsmsvr01 DBI1446I The db2idrop command is running. DB2 installation is being initialized. Total number of tasks to be performed: 2 Total estimated time for all tasks to be performed: 305 second(s) Task #1 start Description: Initializing instance list Estimated time 5 second(s) Task #1 end Task #2 start Description: Configuring DB2 instances Estimated time 300 second(s) Task #2 end The execution completed successfully. For more information see the DB2 installation log at "/tmp/db2idrop.log.1943596". DBI1070I Program db2idrop completed successfully. my_tsmsvr01:[root]/tsm>
Step 3. Delete TSM instance user ID.
my_tsmsvr01:[root]/tsm>userdel tsmsvr01 my_tsmsvr01:[root]/tsm>rm -rf /opt/tivoli/tsmsvr01