After new paths are added to a Tivoli Storage Manager DB2 database, when will space on these new volume paths be used?
When the EXTEND DATABASE command is used to add new paths to a Tivoli Storage Manager 6.x database, a DB2 ALTER DATABASE command is issued by the server to DB2. Per standard DB2 processing when adding new storage paths the space is used as follows:
- Existing regular and large table spaces using automatic storage will not initially use these new paths. The database manager might choose to create new table space containers on these paths only if an out-of-space condition occurs.
- Existing temporary table spaces using automatic storage might use these new paths immediately. If a temporary table space is not in use at the time of an ADD STORAGE ON operation, new containers might be created on those storage paths immediately. However, if the temporary table space is in use, new containers will not be created until there are no more users of the table space.
It should be noted that a database reorganization and/or a restart of the Tivoli Storage Manager server does not "rebalance" the DB2 database usage across the newly added paths.