How do users benefit from TUC?
TUC automates generation and triggering of DB2 maintenance jobs. It identifies any new object and refreshes the maintenance jobs automatically. Customization options allow the administrator to easily control utilities, objects and resources. Real Time Statistics and thresholds are used to trigger utilities only when needed. TUC clients are taking advantage of the products functionality to automate the DB2 object maintenance tasks and have seen significant reduction in resource consumption:
Speedup BACKUP and RECOVERY
The problem: A bank wanted to start taking image copies on DASD to speed up backup and recovery and to allow mirroring to a recovery site. The DASD pool was too small for daily full backups of the entire DB2 subsystem.
The solution: The bank is using TUC to automate daily backups. Only tables that have been changed are copied. TUC decides if a full copy is necessary based on the rate of changes. TUC helped the bank to identify that, in certain workloads, only a few tables were changed. This way the backup time and the space required for backups were dramatically reduced. Only 6% of the total number of tables actually needed backup. Thus the backup process now only takes 20 minutes.
The problem: A bank wanted to be proactive and to identify performance and space problems before they became prominent to users and REORG only the most critical objects without exceeding a limited batch window. Furthermore they wanted to improve performance when accessing large history tables by archiving data that is not in use.
The solution: The bank is using TUC to automate REORGs for a quota of megabytes only for the tables in the most critical condition. TUC collects access performance statistics and can identify if there is a degradation in access performance over time. Unnecessary REORG is avoided, if tables do not suffer from any performance degradation. The bank is using TUC to prune history data by automating REORG DISCARD. The business applications define the conditions for archiving history data. TUC allows recalling archived data or reloading the archived data into history repository. This way the bank is able to decrease the size of large critical tables and improve the access performance to these tables. Backups for smaller tables are also faster. They are able to reduce their REORG process by 30%.
Most recent RUNSTATS
The problem: A large credit card company wanted to ensure that the optimizer is using the most recent statistics and at the same time minimize the CPU cost of statistics collection.
The solution: The credit card company is using TUC to automate statistics collection. The collection frequency is based on the rate of change and the size of the objects. TUC automates REBIND for all dependent packages accessing tables with recently collected statistics to allow the optimizer to choose the best access path for these tables.
Reducing RECOVERY Time
The problem: A credit card company wanted to be ready for any possible recovery scenario, including disaster recovery, recovery to a point in time or rolling back certain changes made to critical tables.
The solution: The credit card company relies on TUC to quickly generate recovery jobs at disaster recovery time. TUC covers all the different aspects of recovery scenarios by allowing easy analysis of the logs with ULT to UNDO changes.
TUC has proven to its existing clients its strength in automating the DB2 object maintenance tasks by improving services to significantly simplify the database administrator routines.
For more information on TUC please see here.