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.
Rearchitect the colgroup processing to be more granular using multiple sorts as opposed to a single sort or more intelligently avoid the colgroup sort altogether (when possible)
Looking at the job output you sent in, we can see that there are 18 colgroups specified.
Based on the current design, we have a single sort for colgroup(s).
There are 184310123 rows unloaded
The no. of the rows passed to the single
dstats sort ...
REORG SORTDATA NO should unload to shadow datasets and not unload to SYSREC
Changing DSSIZE for large table using SORTDATA NO, unloads to SYSREC. Since the volume of data is so large, SYSREC needs to go to tape. This causes the reorg to have greater elapsed time. Unloading to the shadows would greatly reduce the elapse...
Allow LISTDEF to be used by REPAIR where appropriate at partition level that includes a range (1:50)
Allow LISTDEF with REPAIR, such as turning off AREO* (NOAREORPENDSTAR) at partition level. This would include a from partlevel to to partlevel. This would reduce the number of REPAIRs that need to be generated.
Idea For Limited Partition Locking for RI Related Objects
Lock just the partitions of related objects using a cascaded key structure when utilities are used to write to the database. Allows Db2 RI use to coexist with utility operation when it is impractical to lock all partitions of parents and children.
Allow TEMPLATE switching for more data sets in REORG and LOAD
Allow TEMPLATE switching in the REORG TABLESPACE, REORG INDEX and LOAD utilities for the necessary work files. For example, small objects may only require data sets with DSNTYPE BASIC and large objects may require data sets with DSNTYPE EXTREQ or...
BUSINESS REQUIREMENTDatabase Recovery is probably the most critical area for DBAs and Application Support teams. As important as new features and performance are, Recovery is absolutely crucial – Production data loss is unacceptable, long database...
When we try to use the DSNUTILB utility to LOAD data into a DB2 table with RESUME YES option, where we need to Load some set of records, which do have same Primary key values already existing in the Target table, then those records to be loaded ar...
Modify the message when Load utility encounter table not found.
Sometimes we unload many tables from source DB2 to another one. If some tables do not exist in the target DB2, the load utility will fail with RC=8.this error message is mixed with ordinary information and ends with "I" in a big jobout file. For e...
Do not place IBM confidential, company confidential, or personal information into any field.