Skip to Main Content
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


Comprehensive Rollback Solution for IBM FTM Version Upgrades

See this idea on ideas.ibm.com

Currently, when post-upgrade issues such as performance degradation emerge after several days in production, only application components can be reverted easily—leaving clients to navigate database backup and restoration processes manually.  Any backup and restore process would inevitably cause significant data loss that would not achieve the business’ Recovery point objectives (RPO).  This approach introduces significant risk and operational complexity while extending critical system downtime.

Proposed Enhancement Framework:

  • Thorough Database Schema Change Documentation: Detailed mapping of all schema modifications between versions with comprehensive impact analysis
  • Database Rollback and Migration Support: Provide scripts or purpose-built migration utilities to preserving data integrity across version transitions, OR certify that new version of database schema can safely be used with old version of code (n-1)
  • Support for Parallel Execution: support running multiple versions of application code (n and n-1) simultaneously on n version of database with minimal configuration overhead. 

Success Metrics:

  • Complete system restoration (application and database layers) within established recovery timeframes (4 hour RTO)
  • Zero data compromise during rollback operations (no transaction lost, additional column level data may be dropped or ignored)
  • Full functional equivalence post-restoration
  • Comprehensive audit documentation of all rollback procedures
Needed By Quarter
  • Guest
    May 15, 2025

    I agree with Donald. However, I think that "Support for Parallel Execution" should be a separate RFE.  Let's get the documentation and roll-back done, gain some experience, and then take on parallel execution.  I suppose that it could be an implementation detail, and may be a separate set of stories under the same epic, but the size will double, and it creates a new support dynamic.  

    Second, what are the provisions for customizations? How does the customer "certify" that custom tables and data usage don't break in this process.  

    Lastly, can we package with agentic AI to provide the "comprehensive impact analysis", including customization.   

  • Guest
    May 14, 2025

    I really like the idea of:

    Database Rollback and Migration Support: Provide scripts or purpose-built migration utilities to preserving data integrity across version transitions, OR certify that new version of database schema can safely be used with old version of code (n-1)

    However, I would reword it to be AND

    Provide scripts or purpose-built migration utilities to preserving data integrity across version transitions, AND certify that new version of database schema can safely be used with old version of code (n-1)