IBM Data and AI Ideas Portal for Customers
Hide about this portal


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


Add a new idea Subscribe
Status Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jul 27, 2024

RELATED IDEAS

Introduce or Change Reorg for managing commits when generating Identity column values during the Reorg

See this idea on ideas.ibm.com

When an identity column is added to an already existing and populated table, the table is put into a Reorg Pending status and thus unavailable to the applications. When the Reorg is run to resolve the status it generates the identity column values during the Reorg (unload phase). While doing this the Reorg utility generates log records without any commits and creates long running UR which are reflected in the messages in the MSTR log. The whole process adds a considerable time to the Reorg execution (in our case from minutes to several hours) which results in the altered table to not be available for a long time. Load utility can also generate the identity column values but that checkpoints (every 80k records) the identity col value generation. The load finishes in minutes but in this case this will add an unload, alter and Reload to the implementation. Since the unload phase is not restartable anyway can IBM look into either introducing a checkpointing logic for Reorg OR do way with log generation for identity value creation records. There is an option to manage the num of log records generated by Reorg by manipulating the cache option but then this introduces more Alters to the process.

Needed By Quarter
  • Admin
    Janet Figone
    Reply
    |     Sep 19, 2024

    Dear Dhiren, Thank you for providing the case number with the background information.

    Development will consider ways to introduce intermediate commits and/or reduce the logging frequency due to identity column value generation during REORG utility execution. Therefore, the status of this idea is now Future Consideration.

    Sincerely,

    The Db2 z development team

  • Admin
    Janet Figone
    Reply
    |     Sep 17, 2024

    Dear Dhirendra, Thank you for providing a link to the case for this, however, the link is resulting in an error. Do you have a different link we can try?

  • Admin
    Janet Figone
    Reply
    |     Aug 9, 2024

    Dear Dhirendra, Thank you for submitting this Aha Idea.

    While development understands the details of the related scenario and can confirm the lack of commits in the UNLOAD phase of REORG can lead to the long running UR message observed in the console, it's not immediately clear how this existing process elongated the time of execution in the UNLOAD phase - can this symptom be elaborated further ?

    Also has a SF case been opened to collect documentations and report this problem for Db2 analysis ? At this moment this sounds more like a defect issue instead of an enhancement.

    Many thanks.

    The Db2 for z/OS team

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.