Automatic Purge Job Fails with ORA-14758 After Dropping P_PERMANENT Partition Causing SYSAUX Tablespace Growth
(Doc ID 1905788.1)
Last updated on MAY 12, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 and laterOracle 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.
Symptoms
- Due to SYSAUX tablespace growth, the P_PERMANENT partition was dropped since it was felt that it was likely that the last DDL on this partition would be very old and therefore a good candidate for removal.
- Becasue P_PERMANENT partition has been dropped, the system generated interval partition on the tables WRI$_OPTSTAT_HISTGRM_HISTORY and WRI$_OPTSTAT_HISTHEAD_HISTORY is converted to a range partition. eg:
- The purge job failing will results in SYSAUX growing to a huge size and a large list of partitions for the two tables (WRI$_OPTSTAT_HISTGRM_HISTORY and WRI$_OPTSTAT_HISTHEAD_HISTORY) because partitions are not purged as they are supposed to be
Changes
Manually dropped P_PERMANENT partition from SYSAUX tablespace to reduce its size.
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 |
| Changes |
| Cause |
| Solution |
| References |