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
Components Text Search
Created by Guest
Created on May 9, 2017

DB2 V9.7

When doing the case sensitive search, the index on ALT_IDENTIFIER is used correctly, and the query takes around 0.2 seconds as expected.

When doing the case insensitive search, the optimiser correctly uses the V_N1999152021 column rather than the ALT_IDENTIFIER column. However, it doesn't appear to be using the index on the V_N1999152021 column. So, the optimiser starts with a table scan of a table that contains > 500K entries, and does various joins before eventually joining to the C_CUS_INT_IDENTIFIER table. This is taking > 20 seconds in some cases.