Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Mar 19, 2019

I/O required for RI check against the parent table when inserts done on the child table.

We have noticed that there is a high number of get   

pages on the parents indexes when doing an INSERT of a child row. 

 

Here are the details of our situation:                                  

                                                                        

The parent table has a partitioned primary key index with 132

partitions.                                                            

The primary key is in a different order than the table partitioning.   

The partitioning fields are also in the primary key (just not at the   

top of the key).                                                       

                                                                        

When doing an insert of a child row during the RI 

check on the parent, DB2 is checking all 132 primary key indexes,      

instead of first determining the partition, and then only checking the 

one index.                                                              

                                                                        

When we switched the primary key from a partitioned index to a spanning

(non-partitioned index), it dramatically reduced the number of get     

pages on the RI check.

 

We would like you to consider changing the way it works by determining the partition first and then checking the index.     

 

The service request number for this issue was: 93461 072 649.