Quickly reset from “bad” access path
RUNSTATS Rescue provides an easy method to reset the DB2 Optimizer-relevant Catalog statistics as quickly as possible after an incorrect access path change has been detected. DB2’s PLAN MANAGEMENT can’t always help, for example when Dynamic SQL is used, or if an object has been recreated (an index or a view).
Using the Enterprise Statistics Distribution (ESD) component of Bind ImpactExpert or DB2 SQL PerformanceExpert (SPX) for DB2 z/OS, all DB2 Optimizer-relevant Catalog statistics are extracted. This extract must be run before any DB2 RUNSTATS utilities are scheduled to run.
- Provides “rescue” from bad statistics
- Quick and easy to use
- Supports Dynamic and Static SQL out-of-the-box
RUNTATS Rescue is available in two options
Option 1 Rescue Static SQL
Option 2 Rescue Dynamic SQL Product Walkthrough
How to reset from “bad” access path in this short Video: Access Path DB2GO
Be they static or dynamic – clarifying the rather opaque IBM Plan Stability Management
In this 20 minutes webcast we show you the complete RUNSTATS Rescue interface with live Demos.
RUNSTATS Rescue gathers all the DB2 Optimizer-relevant statistics and saves them away on a regular basis. When you have a “bad” access path (that you have discovered through SQL Monitoring, or telephones ringing), you can very simply reset the DB2 Catalog Optimizer-relevant statistics to a point in time where the SQL Access path was better, thus rescuing you from the perils of bad access paths.
Primarily designed for dynamic SQL, there is also a static SQL extension available, and we have even added a nice SOFTWARE ENGINEERING “front end” for IBM Plan Stability so that both methods of saving Static SQL are supported.