Troubleshooting
Problem
Performance degradation is being seen when using volatile tables in sql queries which do not have the statistics up-to-date. The performance is improved after runstats has been executed on them. Why do user need to collect statistics on volatile tables when volatile attribute makes the optimizer to favor to index scan versus table scan?
Symptom
Performance degradation
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Compiler - Optimizer","Platform":[{"code":"PF002","label":"AIX"}],"Version":"9.1;9.5;9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21427231