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:

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:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Jan 16, 2017

db2ckupgrade detects objects in syscat.invalidobjects

If db2ckupgrade detects objects in syscat.invalidobjects, could the developers automatically invoke the revalidate procedure and then check syscat.invalid objects again before bombing out? In bad pseudocode:

If rows exist in syscat.invalid objects
If rows still exist in syscat.invalidobjects
Error out like you do now & stop
(otherwise continue!)

What I was reading was that if the proc can't revalidate an object successfully, it will update the stats and keep the row in the invalidobjects table, at which point db2ckupgrade should rightly complain and stop. So unless I'm missing something, I'm thinking that throwing the automatic revalidate step in there probably shouldn't hurt anything.

Bob Harper