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


Support apply of LOADCOPY in rollforward database (rdsadmin.rollforward_database SP)

See this idea on ideas.ibm.com

After an initial RDS DB2 database redirected restore the rdsadmin.rollforward_database SP does not support the apply of a LOADCOPY during rollforward database phase. In the DB history file the LOADCOPY is registered with its original location which cannot be accessed by RDS. The DB2LOADREC parameter to specify an alternative, accessible location of the LOADCOPY is not exposed in RDS at this time. 

As a result, the tablespace affected by the missing LOADCOPY cannot be fully rolled forward and and made available after bringing the recovered database online.

This gap blocks the near-zero downtime move to cloud approach (native DB2 backup to S3 + RDS DB2 restore database from S3 + archive log shipping to S3 + DB2 RDS rollforward database) - as e.g. offered by the Db2MT migration tool - in case executions  of LOAD <table> COPY YES take place in the on-prem source databaseduring rollforward phase.

Needed By Quarter