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:

Status Delivered
Workspace Db2
Created by Guest
Created on Jun 7, 2019

Remove per-tablespace size limitation for v11.1 and v11.5 community edition

Currently if we restore a database backup that was taken on a higher edition of Db2 into Developer-C, it fails with SQL1139N, even if it is fully less than 100GB. There are two workarounds for this:

  1. Set a MAX for all table spaces before taking the backup. This is problematic, because setting a MAX may not be desired in that environment, and may risk a future outage in that environment.
  2. Apply a different license, do the restore, then change the license.

DB2 should just force the max settings on restore without a user having to go in and change them.

  • Guest
    Jan 22, 2021

    Thanks, this is good news. Can you tell us in which FP or Mod this will be delivered?


    Mark Gillis
    Principal Consultant


    Triton Consulting - Experts in Hybrid Data Management and Digital Transformation

    m: +44 (0) 77866 24704


  • Guest
    Jan 3, 2020

    In case anyone is confused,  the limitation of the community edition is 100 GB of storage per database.  So it's 100GB OF tablespace (the total), not PER tablespace.  db2licm -l wording can be misleading

  • Guest
    Jan 3, 2020

    Encountered this issue as well even though I was just restoring from Express edition 9.7 into Trial 11.1 and finally into the new Community edition 11.5, so higher edition is not a requirement to trigger the issue.

    I have expanded on the How should it work section a little bit:


    First step on restore, Db2 should check each tablespace for a maxsize of None or greater than 100GB.  It should write a warning if any are found and automatically set the tablespace maxsize to 100GB for each.


    Second step, Db2 should estimate the total size of the database to be restored including known compression ratios and give a warning prompt if the total actual space used risk being greater than 100GB. The user will have a chance to abort right away and fix things instead of having to wait for a lengthy restore that will just fail towards the end. 


    Alternately, an utility could be available to run against the backup file to do the above steps as a prerequisite check.

  • Guest
    Sep 10, 2019

    For sure


    I faced the same issues..  it was a pain! Simple change in the code...  Should not be that hard to implement this