Insert Caused Excessive DB File Sequential Read On Index Empty Leaf Blocks After Enabling Primary Key Constraints On The Non-Unique Index (Doc ID 3003509.1)

Last updated on FEBRUARY 09, 2024

Applies to:

Symptoms

• After enabling the primary key using the existing non-unique index, db file sequential read increased significantly even though only insert 1 row.

  For example: 7914830 physical reads for 1 row insert

   

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.