Is it required to rebalance the TSM Server DB tablespaces after adding the new db filesystem ?

When the Tivoli Storage Manager server database (TSMDB1) is created using dbdirs on multiple file systems, for example "/TSM/db1, /TSM/db2", the database will use all file systems equally. When additional file systems need to be added to the database space with the "extend dbs" command, the newly added tablespaces will not be used equally. After adding the /TSM/db3 file system to the database space, DB2 will not rebalance the file systems utilization equally. For example 

/dev/tsmdblv021 10412032 10411804 228 100% /TSM/db1

/dev/tsmdblv022 10412032 10411812 220 100% /TSM/db2

/dev/tsmdblv033 10403840 1333136 9070704 13% /TSM/db3

Also Read: Use this DB2 command to extend TSM DB space when the TSM server is down or unable to startup

The 100% full /TSM/db1 and /TSM/db2 will stay 100% full and may cause the Tivoli Storage Manager to stop because of a DISK FULL condition. To prevent this condition you have to rebalance the TSM Database tablespaces. If the Database was initially created by a Tivoli Storage Manager Server V6.2 or above, there are is a way to do this online using the steps below.

Steps to rebalance the TSM Database Tablespace after adding new DB filesystem

• Prepare a filesystem the same size as the initial filesystem. For example /TSM/db4 size : 10403840

• Add /TSM/db4 to tablespace via Tivoli Storage Manager server admin command :

    extend DBs /fs/db4

• Perform the rebalance activity during a quiet time. Logon as the server instance owner and execute the DB2 commands below. (on Windows, you need to run these commands from a DB2 Command Window and "set db2instance=server1).

    db2 connect to tsmdb1

    db2 set schema tsmdb1

    db2 alter tablespace SYSCATSPACE rebalance

    db2 alter tablespace USERSPACE1 rebalance

    db2 alter tablespace LARGESPACE1 rebalance

    db2 alter tablespace LARGEIDXSPACE1 rebalance

    db2 alter tablespace IDXSPACE1 rebalance

    db2 alter tablespace SYSTOOLSPACE rebalance

Also Read: Temporary Log Files for TSM DB and Recovery Logs

• Depending on the size of the tablespace, the rebalance can take some time to finish. For a large tablespace, the rebalance can take about 30 minutes. Run the following command to check the rebalance status

    db2 "select * from SYSIBMADM.TBSP_UTILIZATION " |grep -i progress

• If the rebalance is still active, the above command will return the tablespace still in active resizing. Wait until all tablespaces have done the rebalance and execute the following commands to reduce the tablespaces 

    db2 alter tablespace SYSCATSPACE reduce max

    db2 alter tablespace USERSPACE1 reduce max

    db2 alter tablespace LARGESPACE1 reduce max

    db2 alter tablespace LARGEIDXSPACE1 reduce max

    db2 alter tablespace IDXSPACE1 reduce max

    db2 alter tablespace SYSTOOLSPACE reduce max

• After the rebalance/reduce, the file systems should be equally utilized and there are should be no more file systems in 100% full condition.

Also Read: Steps to do after successful TSM DB restore

Note: If you are not sure on how to do these steps, open an IBM PMR and IBM support should be able to do these steps for you.