Excessive Object Sizes When Using Parallel
(Doc ID 855472.1)
Last updated on FEBRUARY 15, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
When a bitmap index is created on an ASSM tablespace, using an extent size specified as UNIFORM, with AUTOEXTEND enabled, the index increases to a very large size. If the index is dropped and rebuilt, the size is considerably smaller. The DBMS_SPACE.SPACE_USAGE procedure shows several unformatted blocks for the affected object. The issue doesn't seem to be limited specifically to indexes as other objects show abnormal space allocation as well.
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