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
Copy and use full distributed stats available for federation from DB2 LUW to DB2 LUW
We use federation to check audit records on db2 blu and match then to financial record on Peoplesoft. All treatments are executed from financial DB (row organized), and pb is that nicknames do not take into account distributed stats nor colum grou...
on DB2 LUW , Create all indexes on nicknames, including those with key greater than 1024 bytes
When I create a nickname on a remote table with an index and the index key is greater than 1024 bytes, the index spécification is not created on the local database : There is no warning for this when the nickname is created, nothing in db2diag.log...
I tried to implement a trigger to update nicknames but received the following error. Without this function, the following design is not possible, I have to put the reporting and online schema into 1 database if I want to use triggers for synchroni...
refresh fedration cache withouht the need to bounce instance once port number is changed from x to y
We have fedration defined from db2 to db2 v1 11 servers. once we update the port number of the fedration server we started getting errors like below SQL30080N A communication error "111" occurred sending or receiving data from the remote database....
Do not place IBM confidential, company confidential, or personal information into any field.