You have any version of Tivoli Storage Manager installed. You deleted large amounts of data from the server, but storage space was not freed to the operating system. For instructions about resolving this issue, see Techdoc 1596944.
#TSM 4 ISSUES FULL#
The server halts because the active log becomes full when index reorganization is running.Reorganization for one or more tables requires a considerable amount of time, and this prevents reorganization from running on other tables.You are seeing degradation in server operations and reorganization activities, for example: The server database is using DB2 9.5 table spaces, and space is not being reclaimed.įollow the instructions in Using scripts to convert the server database to use DB2 9.7 table spaces. You have Tivoli Storage Manager V6.1 installed, or you upgraded from V6.1 to V6.2.
You are seeing database growth and performance degradation. Resolving and preventing problems with database growth and degraded performance Often, database growth and degraded performance are related to issues with table or index reorganization. The following table provides resources to help you resolve or prevent problems that are related to database growth and degraded performance. Occasionally, it appears that the workload on a server is static, but in fact more and more objects are being managed over time, and this causes the database to grow. When you delete large amounts of data from the server, it does not mean that large amounts of storage from the database are freed up. You can resolve these issues by canceling server operations so that reorganization can progress, but canceling server operations is often undesirable. However, certain server workloads (especially servers with large deduplicated storage pools) leave insufficient resources for online database reorganization to run without generating errors or conflicting with server operations. If you installed Tivoli Storage Manager V6.2, V6.3, or V7.1, the reclaimable space feature is available. Insufficient resources for database reorganization.However, the tablespace type for the DB2 V10.5 database is DB2 9.7. Tip: Tivoli Storage Manager V7.1 is installed with a DB2 V10.5 database. Originally installed V6.1, or upgraded to V6.1 To determine whether the reclaimable space feature is available to you, review the following table.Īvailability of reclaimable space feature If the reclaimable space feature is enabled, you can return unused space to the file system of the operating system.
Even when V6.1 servers are upgraded to server V6.2 or later, the DB2 9.5 table spaces remain.
DB2 9.5 table spaces do not have the reclaimable space feature. If you installed Tivoli Storage Manager V6.1, or upgraded the server to V6.1, the server database uses DB2 9.5 table spaces. ĭatabase growth and degraded server performance might result from one or more of the following causes: Tip: If you installed Tivoli Storage Manager 7.1.1.200 or later, follow the instructions in Technote 1683633.
0 kommentar(er)
