Increasing the size of TSM database
You can increase the size of the database by creating directories and adding them to the database. The server can use all the space that is available to the drives or file systems where the database directories are located. To ensure that database space is always available, monitor the space in use by the server and the file systems where the directories are located.
The maximum size of the Tivoli® Storage Manager database is 4 TB.
The QUERY DB command displays the number of free pages in the table space and the free space available to the database. If the number of free pages are low and there is a lot of free space available, the database allocates additional space. However, if free space is low, it might not be possible to expand the database. To increase the size of the database, take the following steps:
- Create one or more database directories. Locate the directories on separate drives or file systems.
- Issue the EXTEND DBSPACE command to add one or more directories to the database. The directories must be accessible to the user ID of the database manager. Locate the directories on different drives or file systems.
For example in AIX, add two directories to the storage space for the database, issue the following command:
extend dbspace /tsmdb005,/tsmdb006
For example in Windows, to add a directory and a drive to the storage space for the database, issue the following command:
extend dbspace h:\tsmdb005,I:
After a directory is added to a Tivoli Storage Manager server, the directory might not be used to its full extent. Some Tivoli Storage Manager events can cause the added database space to become used, over time. For example, table reorganizations or some temporary database transactions, such as long running select statements, can help the added database space to begin filling up. The database space redistribution among all directories can require a few days or weeks. If the existing database directories are nearly full when the directory is added, the server might encounter an out-of-space condition, as reported in the db2diag.log.
If this condition occurs, halt and restart the server. If the restart does not correct the condition, remove the database and then restore it to the same or new directories.
Reducing the size of TSM database
If a significant amount of data has been deleted from the database, consider reducing the database size.
- Create a file containing a list of directories that represent the new directories. For example, dbdirs.txt.
- Run a full database backup by issuing the following command:
backup db devclass=tapeclass type=full
- Halt the server.
- Remove the database instance by issuing the following command:
dsmserv removedb TSMDB1
- Restore the database specifying the file containing the directories to be used. For example, you can issue the following command:
dsmserv restore db todate=today on=dbdirs.txt
- Restart the server.
Increasing the size of the active log
If the log is running out of space, the current transaction is rolled back, and the server issues an error message and halts. You cannot restart the server until the active log size is increased.
To increase the size of the active log while the server is halted, complete the following steps:
- Issue the DSMSERV DISPLAY LOG offline utility to display the size of the active log.
- Ensure that the location for the active log has enough space for the increased log size. If a log mirror exists, its location must also have enough space for the increased log size.
- Halt the server.
- In the dsmserv.opt file, update the ACTIVELOGSIZE option
to the new maximum size of the active log, in megabytes. For
example, to change the active log to its maximum size of 128 GB, enter
the following server option:
- If you plan to use a new active log directory, update the directory name specified in the ACTIVELOGDIRECTORY server option. The new directory must be empty and must be accessible to the user ID of the database manager.
- Restart the server.
Log files of 512 MB are automatically defined until the size specified in the ACTIVELOGSIZE option is reached. If a log mirror exists, log files are also defined automatically.