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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.