Skip to Main Content
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 Future consideration
Workspace Db2
Created by Guest
Created on Feb 7, 2022

Population of V12 new added Catalog columns during activation of Function level V12R1M50 and avoid it later during executions of ALTER TABLESPACE because of contention of packages.

After you apply the PTF for APAR PI86123, the first ALTER TABLESPACE, populates any null attributes for objects created in function level V12R1M100 or earlier.

When the one-time population occurs for an ALTER TABLESPACE statement, Db2 must quiesce dependent packages to complete this operation, and you might encounter SQLCODEs -904, -911, or -913 for dependent packages.

In our installation, this has caused a full transactional disaster (Reported in case TS008017044). Por this cause, we propose a Jobname which could be executed during activation of Function level V12R1M500, the one which would trigger instead the population of all those V12 new added Catalog columns and avoid it later during executions of ALTER TABLESPACE that population would require quiesce of dependent Packages (and so obtention of X-locks on the SKPTs of those dependent Packages).

Needed By Yesterday (Let's go already!)
  • Guest
    Feb 7, 2022

    This idea has been opened for DB2 for LUW but should have been opened for DB2 for Z/OS