Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Future consideration
Created by Guest
Created on May 24, 2022

Improve Config DB and UpdateDB Performance

We have a Maximo oracle database with approximately 80 million workorder records.

CONFIGDB is slow when adding a custom field with a default value to large tables. For example adding a YORN field new_field to workorder table with default value 0, Maximo performs below 3 SQL statements:


alter table workorder add new_field number;

update workorder set new_field = 0 where new_field is null;

alter table WORKORDER modify new_field number not null;


The update SQL takes hours to run, and risk running out of undo space. It is not best practice when running large update transaction without commit in the middle. In this case it is unnecessary to use update SQL. It would be much faster, in matter of seconds if we can replace the 3 SQLs with 1 DDL: alter table WORKORDER add new_field number default 0 not null;


This issue also applies to UpdateDB in some of the maximo install/upgrade programs. For example we attempted to install HSE to Maximo, there are many new columns being added to workorder table, each field was added via the 3 SQLs above, and each field took close to 3 hours to run in our database, the whole HSE installation took days to run.


Idea priority Urgent
  • Guest
    Reply
    |
    Sep 4, 2024

    I can certainly appreciate. I haven't looked too hard into this, but do wonder if there is any time difference using "update workorder set new_field = 0" instead. Maximo knows that the field is new. so why even use a Where Clause.

  • Guest
    Reply
    |
    Aug 30, 2024

    That's a great idea!

  • Guest
    Reply
    |
    Aug 30, 2024

    Yes, this is really needed from BAU perspective.

  • Guest
    Reply
    |
    Apr 12, 2024

    This needs to be implemented.   YORNs should be created as "fast add columns" with the alter statement provided in the idea.   

     

    https://www.oracle.com/technical-resources/articles/database/sql-11g-schemamanagement.html

     

    see the "Adding Columns with a Default Value" section

     

    Note: that after we updated our dbconfig classes to create YORN columns as a "fast add column", we were able to add a YORN to our workorder table (millions of records) in about 2 minutes whereas previously it would take several hours.