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:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |