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 Federation
Created by Guest
Created on May 6, 2016

Federation Issue on DB2 ORACLE COMPATIBLE databases when remote is NOT ORACLE COMPATIBLE

When a DB2 Oracle compatible (ORA) is federated against another DB2 DB that is NOT-ORAcle compatible, any select involving char columns results in not pushing down the request to the remote server and transmit the huge amount of records across the network.

This is due to Oracle and DB2 different processing of empty strings.

However, once the remote table has been received, instead of returning the data applying oracle's criteria, the ORA database returns the same the remote NOT-ORA database would have returned.

This makes not-pushing down a senseless loss of time.

When federation is reverse, i.e. from NON-ORA to ORA, the same happens in that the result is an oracle result. However a pushdown occurs, saving a lot of time to query processing and no network flood.

Another way of saying it:

An ORA DB has two identical tables with identical data, but one of them belongs to a NON-ORA DB through federation. Well, the ORA DB treats the local table as Oracle but treats the remote table as DB2, however it hasn't pushed down the query to remote server, taking a long time (2 million records)

When the NON-ORA DB has two tables with identical data but one of them belongs to an ORA DB through federation, it treats the local table as DB2, the remote table as Oracle BUT DOES pushdown, saving lots of processing time due to transmitting only the affected rows, not the entire 2 million record table.