We've got several SQL queries stabilized with dynamic plan stability. Reason is to prevent them from getting a bad accesspath. After operations like "ALTER TABLE ... ROTATE PARTITION..." the query is flagged to valid N in SYSIBM.SYSDYNQRY. Than we may suffer again from a bad accesspath. Therefor it should be possible to "restablize" the accesspath in SYSDYNQRY.
Why is it useful?
|Who would benefit from this IDEA?||DBAs would like that because they'll save a lot of time. Banking customers would like that because they won't suffer from outages.|
How should it work?
1) Proposed solution: give us a command like "RESTABILIZE ...."
2) The bad accesspathes sometimes cause severe problems for our banking customers. With this solution we'ld have a fast workaround.
3) Our workaround is to collect plan_table data with the good accesspath (maybe in another Db2 system) and than implement an OPTHINT.
|Priority Justification||Reason for high priority is the danger of outages|
|Customer Name||Fiducia & GAD IT AG|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions