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,
Post an idea
Upvote ideas that matter most to you
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.
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.