This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
The RECOVER TABLESPACE with BACKOUT YES is a relatively new recover option. It tells Db2 RECOVER to start with the current state of the tablespace and read the data change log backwards to find all recent changes to the tablespace and undo those changes in the target tablespace. The intent is to use BACKOUT YES when the recovery point is relatively close in time to “now” and you do not want start from the last full copy and roll forward. This is especially useful if the target tablespace is very large, the time required to backout time could be very quick.
But the minor problem in this scenario is that after the tablespace is recovered (using backout yes) then the index(es) are out of sync. Ideally, I would like to RECOVER INDEX BACKOUT YES, but that could only be done if I defined the indexes with COPY YES.
Apparently, RECOVER INDEX first checks if the index has COPY YES attribute before beginning recovery.
But I would like to be RECOVER INDEX BACKOUT YES even if the index is COPY NO.
My suggestion is that RECOVER INDEX allow BACKOUT YES even if the index is COPY NO.
Of course, the IBM documentation must be updated to match. To say RECOVER INDEX BACKOUT YES is allowed with any index. And RECOVER INDEX BACKOUT NO requires index to have COPY YES (and an actual image copy dataset)
https://www.ibm.com/docs/en/db2-for-zos/12?topic=recover-syntax-options-control-statement
Why do I make this request for enhancement?
I had a scenario where I needed to quickly backout a recent data zap that went wrong. I remember RECOVER TABLESPACE BACKOUT YES and I recovered to a QUIESCE RBA point that was made before the data zap. It was super fast. But then the indexes were out of wack. I could not recover the indexes with backout yes and I had to rebuild the indexes which took much longer then the recover tablespace backout yes. I was annoyed
I think the intent of “backout yes” for recover tablespace (And recover index) is for easy and quick recovery in emergency scenarios. You should make it easier for us by not requiring index to be copy yes!
Yes, I know, I could make all my indexes COPY YES. On the off chance that I want to do RECOVER INDEX BACKOUT YES in the future…. That would make it easier for me. But you should change Db2 itself to always allow it and make it easier for everyone.
Needed By | Not sure -- Just thought it was cool |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
In the past I have been working with BMC RECOVERY product. It was great for the reason described above. Just backout a few transactions without having to do a point-in-time recovery or a Tablespace backout followed by an intensive REBUILD INDEX.