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
Hello! We had problems with CPU in Production environment several months ago with a simple query with IN predicate. The CPU reached 100%! Particularly, this query has many literals within IN predicate and the IN predicate can't be matching. After ...
Provide ROWID addition for PBG to PBR conversion in V13 ALTER statement.
In V13m we get to convert PBG tablespace to PBR by a simple ALTER statement. However, we will be forced to look for a partitioning key by working with application team. In the mean time, in V12 we have a feature called "Hidden ROWID support for pa...
JDBC connection property currentSchema should be externalised in an IFCID
We have jdbc applications which have set the jdbc property currentSchema to determine the collection of db2 objects like tables, views etc. When we want to trace the application with a performance trace, we're not able to analyse the correct colle...
Enhance high availability for partition by growth tablespaces.
Real-life scenario is described in the first paragraph below. I included a subset of it. The issue resulted in critical system outage caused a partition by growth dataset that hit max extents prior to hitting the DSMAX for the partition tablespace...
DB2 z/OS - Message id - DSNJ110E - Additional alerts for active log monitoring and highlighted new message id when DB2 logging was suspended
We had a major incident due to suspended logging for one of the critical customer.
One of the critical production DB2 subsystem logging was suspended , caused by stalled archive log offloading process due to insufficient storage space on archive...
DISPLAY UTIL(*) is used daily, but it doesnt't show the Object involved/affected. This info is already in SYSUTILX so it seems to be possible to obtain it directly with the command Display.
Currently, the DBA, Operator or Developer has to deal ...
Prevent SPT01 growth with new behaviour REBIND(EXTENDED) in Cod-Level M510
Before Codlevel M510, PHASEIN functionality was only used when the package was executing Since the implementation of Codlevel M510 (include PTF 73874 (APAR PH28693)), executing a REBIND with PLANMGMT(EXTENDED) will always store information in SYSP...
Error message improvement when failing to convert tablespace to UTS PBG
Recently we are converting our old segmented and simple tablespaces to UTS PBG. When converting one of these tablespaces we got an abend and a DUMP showing reason code 00C90101. We opended a case (TS009249828) and analyzing the DUMP DB2 lab conclu...
Stop package invalidation after ALTER MAXPARTITIONS
These days in an agile world we have to ALTER PBG spaces on-the-fly to raise the MAXPARTITIONS value. Sadly this ALTER, even though it is an immediate ALTER, sets all dependent packages to VALID = 'N' which is, of course, a disaster.
A number of our common customers run DB2 utilities from third party vendors and IBM replication solutions. They are requesting that our LOAD and REORG utilities write the old dictionary pages to the log for later retrieval by a replication product...
Do not place IBM confidential, company confidential, or personal information into any field.