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.
Add support to update "Last Login Time" of Linux OS for Db2 LUW
Db2 LUW on Linux OS only use auth and password module of PAM to validate and change password, but it didn't record the "Last Login Time" for the users on the Linux OS, so we don't know if the users are actually using the Db2 for data query. And th...
Event monitor creation, write to table option should allow to specify a tabkespace into which ALL the new tables should be created in
Create event monitor write to table option will create new tables.All the new tables are defined in a tablespace which db2 chooses.I want an option to specify a tablesapce name, in which ALL the new tables should get created in.
Add a monitoring table function to return transaction ids along with their commit times.
Goldman Sachs needs to know all the insert/update/delete operations against all tables updated by 1000s of applications along with their commit times. They dont want to use a replication. They want to use triggers that will be triggered on I/U/D o...
Allow better monitoring of DB2 Thread/Connection types
Currently there are various ZPARMs to "control" thread management (CTHREAD,MAXDBAT,CONDBAT,IDFORE,IDBACK,etc). These ZPARMS are upper bound limits of the number of each type of thread/connection that DB2 is configured with. There is very litt...
Enhancement regarding the .ftok file and the DB2 instance.
I will suggest the following:1. Let Db2 log a simple message 'The .ftok file is missing, last seen ' when the instance started.2. Also, suggest to execute ~/sqllib/bin/db2ftok or go ahead and execute it
Lock event monitor does not log hex values of prepared statements
When using the lock event monitor to track prepared statements involved in lock timeouts/deadlocks, it was observed that parameter marker values for hex entries are not logged even though the option for history and values is enabled. This works fi...
db will be blocked and hang after mon_heap is run out
agents will be blocked and will hang after mon_heap is run out when database turns on event monitor. Now it is works as design, yet customer hope we can change the design and decouple between event monitor and the agents executing some SQLs. So ag...
Purescale - Event Monitor for Locking - Include member information
In Purescale environment, with currently commited enabled and CS isolation query, we can find situations where a "select" receives a locktimeout depending on which member the connection comes. But, event monitor for locking doesn't include this in...
Currently we have db2diag files as part of dbm parameter (DIAGPATH) and all the files (db2diag.log, events,nfy,bin,stack,stmm,dump) going into the same directory. The challenge is in case of issues, we see huge dump files produced (sometimes 40gb...
Do not place IBM confidential, company confidential, or personal information into any field.