Performance Degradation of DMLs after Creating a 'PARTITION BY REFERENCE' Table.
(Doc ID 1064364.1)
Last updated on MARCH 10, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.1.0.7 [Release 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Reviewed on 22-JUL-2011.
Symptoms
With the presence of a "PARTITION BY REFERENCE" table, inserts into the corresponding parent table take longer.
For example, if a second table exists "test_A " that has a "reference partition" to the parent table "test" then the inserts to the parent table are 20 times longer.
Dropping the partition by reference table (test_A) leads to insert into parent table working fine.
Example:
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 |