Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Future consideration
Workspace Db2
Created by Guest
Created on Jul 26, 2022

Enable DATABASE_MEMORY change on WRITE SUSPEND database

We are using db2relocatedb to deploy test, dev, preprod environments from production images (disc snapshots). This happens multiple times a week (talking about multiple hundred databases). Most databases have DATABASE_MEMORY set to AUTOMATIC.

Relocated databases are in write suspend mode. If right before the snapshot there was high workload on the source DB it happens that the database memory has a high value set via automatic maintenance.

If the database memory is to high (higher than instance memory left) the "restart db <dbname> write resume" fails with a memory allocation error.

Trying to change the automatic set value during write suspend causes a

SQL1552N The command failed because write operations for the database are suspended or are being suspended.

As long as the server has enough memory to increase the instance memory to a sufficient size we could work around that but we also had systems where we had to increase the server memory only for the relocate.

Best solution would be to make a change of DATABASE_MEMORY possible even if database is write suspend.

Alternative could be a temporary approach like with bufferpool size override (db2set DB2_OVERRIDE_BPF).

Needed By Week