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
Today, Db2 Restore can continue with a subset of tablespaces if e.g. same tablespaces fail to acquire containers. In the end of roll forward completes, but some tablespaces did not complete and remain in 'storage definition pending' and need to have recovery (restore/rollforward) restarted for these tablespaces.
This is expected. By default Db2 prioritizes getting as much of the database up and recovery as quickly as possible.
A configuration option would be helpful to abort restore if tablespace errors occur, similar to DB2_FAIL_RECOVERY_ON_TABLESPSACES_ERROR
Needed by Date | Dec 31, 2020 |
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.
Has been delivered in 11.5.7.0. Please see https://www.ibm.com/docs/en/db2/11.5?topic=1157-changes-registry-environment-variables.
Hi Michael,
the suggested registry variable suits us well, thanks.
Kind regards, Matthias
OK thanks for the feedback.
One last question ... we were thinking of just using DB2_FAIL_RECOVERY_ON_TABLESPSACE_ERROR :
"if DB2_FAIL_RECOVERY_ON_TABLESPSACE_ERROR is set to any value other than OFF then restore would also fail if a table space fails. I would think it is in the same spirit of failing on any table space goes bad during rollforward (and in the future crash recovery)."
Thoughts?
Historically, Db2 has always tried to get up some part of the database if any table space fails. It seems like there is a growing group of users that wants the opposite which is fail on any table space error. Instead of creating many knobs, our thought is use one knob that controls this decision during all recovery operations (restore, crash recovery, rollforward, HADR replay).
Hi Michael, a Db2 registry variable would be suffucients. Kind regards, Matthias
Hi. Would a Db2 registry variable be sufficient or would a database configuration parameter be preferred? Thanks.