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 Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Submitted
Workspace Informix
Components Informix Server
Created by Guest
Created on Dec 9, 2022

Fixing IPA in a 15TB OLTP database or large database

We have a 15 TB size oltp db running in 12.10.FC12.

We want to fix the data with pending IPA,however, we cannot use the traditional way due to :

- we cannot put the DB offline for hours to fix the data with pending IPA and it will be between  5 to 10 millions of revenue loss (24 to 48 hours)  for the company if we shutdown the DB to fix the data with pending IPA.

What we have done so far in relation to data with Pending IPA.
- We cannot use the traditional way via update table set col1=col1 where 1=1, this will take years to complete billions of record. We have tried this approach and did not work in our prod system.
- We cannot use EXECUTE FUNCTION task('table update_ipa parallel','tablename'), this will lock the table and cannot be done online due to blocking of live transactions.
 

 

Needed By Quarter
  • Guest
    Jan 5, 2023

    Oops. Looks like my login failed. The previous comment was me: Art Kagel. Contact me for a copy of fix_ips4.ec

  • Guest
    Jan 5, 2023

    You can use my fix_ipa4.ec tool. Reach out to me privately and I will send you the source.

    It tends to be faster than the API function, only locks a relatively small number of rows at a time, and only updates pages that are not already at the latest version level, so it can be cancelled at any time and restarted with no penalty.


    $ fix_ipa -?

    fix_ipa - Complete outstanding in-place alters for all databases and tables.

    Usage: fix_ipa
    < -h host >
    < -d database > [-t table | -P partnum]
    < -S >
    < -w waittime >
    < -o>
    < -c commit_count >
    < -p PDQRPIORITY >
    fix_ipa -l
    fix_ipa -?
    fix_ipa -V

    -l - List mode. Just list the tables that need fixing.
    -d - Specify a database to process. Default: all.
    -t - Specify a table to process. Default: all in selected database.
    -P - Specify a partnm to process. Default: all in selected database.
    -h - Host to update Default: $INFORMIXSERVER.
    -S - Silent mode. Supress messages.
    -V - Print version information and exit.
    -c - Commit after commit_count rows updated. Default: 10,000 rows.
    -w - # of seconds to wait for locked rows to be released (if < 0 wait
    forever). Default 10.
    -p - PDQPRIORITY to set for the task.