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

See this idea on ideas.ibm.com

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.

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

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