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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com


Status Submitted
Created by Guest
Created on Oct 28, 2024

Reorg Index materialization

For REORG INDEX pending alter materialization, the utility performs a DRAIN ALL on the target index before starting the SWITCH phase, and then relies on DDL/Dependency logic to invalidate all the affected plans/packages/DSC...etc in the middle of SWITCH phase. If any of these lock requests fail, the REORG would fail/abend in the middle of SWITCH phase and rely on the next user action to either restart or to term utility.

For REORG TABLESPACE pending alter materialization, the utility tries to 'quiesce' the required plans/packages and other resources in the final LOG iteration before it drains all and enters the SWITCH phase to complete the REORG.

The REORG TABLESPACE approach is a bit more user friendly as the utility treats any -904 encountered by the REORG as a ‘drain error’, releases the resources and repeats the processing at a later time without spending much time setting the objects to UTUT dbet state. REORG INDEX had a different design than REORG TABLESPACE because REORG INDEX has never serialised to any table/table space constructs/locks in the past other than the index's drain lock.

The REORG INDEX should really be improved to serialize much like a REORG TABLESPACE when materializing a pending definition change on the index, to avoid 04E abends and timeouts.

Needed By Yesterday (Let's go already!)