Resolving database reorganization problems
Database table reorganization and index reorganization require a significant amount of system resources. To avoid occupying system resources that can be used elsewhere, run your reorganization routines on off times.
Unexpected database growth and unexpected active and archive log space requirements can occur if tables or the indexes associated with tables are not reorganized. IBM Storage Protect reorganizes tables by default. If automatic reorganization is affecting server performance, you can schedule reorganization manually.
The following
suggestions might help when you configure your reorganization:
- Turn on index reorganization if you are running deduplication on your server. See the server option ALLOWREORGINDEX.
- By default, table reorganization is turned on 24-hours-a-day.
Run reorganization during a relatively idle time during the day.
See the following server options for defining an idle time when reorganization
can run:
- REORGBEGINTIME
- REORGDURATION