Unexpected database growth, unexpected active and archive log space requirements, and reduced server performance can occur over time if tables or the indexes associated with tables are not reorganized. Tables and indexes are reorganized by default by Tivoli® Storage Manager. If automatic reorganization is affecting server performance, you can schedule reorganization manually.
Reorganization of table data can be initiated by the Tivoli Storage Manager server or by DB2®. If server-initiated reorganization is enabled. The server analyzes selected database tables and indexes based on table activity, and determines when reorganization is required. The database manager runs a reorganization while server operations continue. If reorganization by DB2 is enabled, DB2 controls the reorganization process. Reorganization by DB2 is not recommended.
Server-initiated table reorganization is enabled by default. If you are deduplicating data, consider enabling server-initiated index reorganization. However, table and index reorganization requires locks on the database that might interfere with server operations. Reorganization also requires significant processor, active log, and archive log resources. If reorganization is causing performance problems, you can manually schedule table and index reorganizations.
The best time to start a reorganization is when server activity is low and when access to the database is optimal. Schedule table reorganization for databases on servers that are not running deduplication. Schedule table and index reorganization on servers that are running deduplication.