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 Not under consideration
Workspace Db2
Created by Guest
Created on Aug 15, 2018

Allow CREATE/REPLACE for users other than owner

Currently on Db2 LUW CREATE OR REPLACE is only allowed for the owner of a database object. CREATE OR REPLACE authorization should be opened up to allow create/replace by anyone who has the ability to drop the object and to create the object with any existing granted privileges retained. As a result the ownership of the object may change. This matches the current Db2 for i behaviour of CREATE OR REPLACE .
  • Guest
    Nov 2, 2022

    The only logical result of this type of process is all involved developers will end up using the same system id that owns all the objects to do their maintenance work. This to avoid the extra work of having to track all dependencies and guarantee everything is caught and recreated back in the same order. This was the reason the function was created in the first place, remove the element of human error from the process.

    With that said the result ends up causing a non-compliance from an AUDIT perspective because you can’t track what developer is making what changes. Since they all end up using the same id the details of who did the work is lost. This goes against well established best practices.

    Can someone please explain to me why it was set to be this way officially?

    Kind Regards,

    Bryce Domaille

  • Guest
    Mar 24, 2022

    Yes, original OWNER may no longer have active security credentials. Nothing should be blocked based on OWNER.

  • Guest
    Nov 2, 2020

    yes, I think... it must GRANT EXECUTE, ALTER on the procedure to other user!