Troubleshooting
Problem
Adding database space to DB2 when the Tivoli Storage Manager Server is actually down.
Symptom
The Tivoli Storage Manager Server crashes when the filesystems used by DB2 is filled up and no more space is available.
Cause
The Tivoli Storage Manager Server crashed because it filled up all the filesystem's space and no more information can be inserted in the DB itself.
Diagnosing The Problem
Check the Tivoli Storage Manager DB2 filesystem utilization:
- For UNIX systems this can be achieved issuing command:
df -k
- For Windows systems:
use Windows Explorer for checking used space for the filesystem assigned to the DB
Resolving The Problem
Usually this should not occur and the DB filesystem usage needs to be monitored or tailored accordingly (regarding the capacity planning of the Tivoli Storage Manager environment).
With the Tivoli Storage Manager Server up and running it is possible to assign a new filesystem to the DB using the following command:
- extend dbspace <path>
But when the Tivoli Storage Manager Server is down this command is not available.
To assign additional space to the DB2 when the server is down follow these steps:
1. Add a new filesystem to the Operating System with the same size of the existing assigned filesystems.
2. For the following steps at least 200 MB need to be available in the existing DB filesystems.
3. Login as the Tivoli Storage Manager instance owner and run:
- db2 connect to TSMDB1
- db2 ALTER DATABASE TSMDB1 ADD STORAGE ON <path_new_filesystem>
4. After completing the previous commands start the Tivoli Storage Manager Server.
5. Use the following command to verify whether the new filesystem was added successfully:
- query dbs
6. When the new path is shown in the "q dbs" output you have to rebalance the DB. This means that the DB containers get distributed to all available paths. A detailed explanation can be found in the link reference in URL section.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21662954