Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Under review
Created by Guest
Created on Apr 19, 2022

Splitting Software Update package upload and pre-check steps

When doing Software Upgrade, ie. when pressing the "transfer" button in Datastudio, idaa server runs a list of 5 steps.

The first step is the transfer of upgrade package of 20+GB. This could take long if the package does not locate on USS (some customers do not have a USS drive of big enough size), so it could take them a few hours to upload the package.

Step number 5 is db2diag preliminary check to make sure the appliance is on a good shape for upgrade. When the preliminary check fails, it fails the complete package transfer as well, ie. all the 4 steps before will be rolled back, the uploaded package is removed, etc.


On one production appliance, one customer experienced at least 4-5 times of a pre-check failure, and each time the package has to be re-transferred. Due to their small USS size and slow upload speed, it took them 3 attempts (on three individual planned weekends) to upgrade the ONE appliance.


The idea is to

  • separate the 5 steps, so that if the preliminary check fails, the package transfer won't be repeated.

Knut suggested:

  • keep the transferred (unverified) packages in some sort of staging area

  • introduce some validation of the transferred packages and in case they are good, skip re-transferring the packages again?

Needed By Yesterday (Let's go already!)