IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Allow configuration to abort Db2 restore if tablespace errors occur

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

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 17 2020
  • Future consideration
Who would benefit from this IDEA? Customers who had to restore large databases with a large number of tablespaces
How should it work?

A Db2 registry (e.g. DB"_FAIL_RESTORE_ON_TABLESPACE_ERROR [CONTINUE|ABORT|CONTINUE_UNCRITICAL]) variable should be provided which allows to configure if a Db2 restore operation should continue (like today) or abort completely. A further option would be helpful to continue just if a restore error occurs on 'non critical' tablespaces (SYSTOOLSPACE, TEMPORARY TABLESPACES etc.).Aborting the first restore, fixing the problem and start the complete restore again could be much faster.

Idea Priority High
Priority Justification Idea is ranked 'High' because of experience many repeated recoveries
Customer Name Heribert Gausmann
  • Attach files

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 "anonymous@euprivacy.out" 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