IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

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

IBM Employees:

The correct URL for entering your ideas is:

Workspace Db2
Created by Guest
Created on Sep 17, 2020

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

Needed by Date Dec 31, 2020
  • Guest
    Jul 14, 2021

    Hi Michael,

    the suggested registry variable suits us well, thanks.

    Kind regards, Matthias

  • Admin
    Michael Roecken
    May 14, 2021

    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)."


    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).

  • Guest
    May 14, 2021

    Hi Michael, a Db2 registry variable would be suffucients. Kind regards, Matthias

  • Admin
    Michael Roecken
    May 12, 2021

    Hi. Would a Db2 registry variable be sufficient or would a database configuration parameter be preferred? Thanks.