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
ADMIN_TAB_INFO is sloooow and this has been the case for quite sometiome.
Extremely slow when used in a RP environment. Also used by check_upgrade which takes 7+ hours to run. Environment has 2million+ objects, 1 range per day for 3 years. Check_upgrade may be calling check for load pending which used admin_tab_info
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...
In a HADR configuration typically customers use db2pd -hadr on the standby to monitor the state. On the standby if there is a problem with one of the tablespaces it'll be marked invalid and future log records against the tablespace will be skipped...
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 little in...
To monitor system resource usage at database level in a pureScale environment
All current monitoring facilities can not meet customer requirements to monitor overall system resource consumed for a specific database, in a database consolidation scenario of pureScale. PMR#: TS000078803
Invoke the DB2 call-out scripts (COS) for ALL First Occurrence Data Collection (FODC) events
Currently the DB2 call-out scripts (COS) will not be invoked for all ALL First Occurrence Data Collection (FODC) events. For instance the only time that FODC_AppErr% events will invoke the db2cos script is when the condition happens on a sub-agent...
DB2 listener not activated after DB process killed by OS and restarted automatically by TSA in HADR environment
We had DB2 HADR primary/standby configuration. Due to one application job,DB2 consumes all memory and OS killed db2sysc process. db2 restarted automatically by TSA but listener wasn't activated . There was no evidence in logs which process was usi...
Do not place IBM confidential, company confidential, or personal information into any field.