CTX_DDL.OPTIMIZE_INDEX in Rebuild Mode Using Lots of Tablespace Space

(Doc ID 799674.1)

Last updated on JULY 09, 2015

Applies to:

Oracle Text - Version to [Release 10.2 to 11.2]
Information in this document applies to any platform.


I am using ctx_ddl.optimize_index in rebuild mode to reorganize my Text index partitions. It works fine, is usually much faster than re-creating the partition and it can also be done "online".
However, unfortunately the $I table takes much more space AFTER the optimization than BEFORE the optimization, although it had many more $I rows BEFORE the optimization because of the many updates and synchronizations to the index.
I'm talking about a 27% increase in ASSM managed tablespace usage AFTER the optimization.
Oracle Enterprise Manager (OEM) reports that 30% of the space is not used. I have 152 extents of 10M size AFTER the optimization, but only had 118 BEFORE the optimization. According to ctx_report.index_size, the $I used 1190MB BEFORE the optimize and 1520MB AFTER the optimize.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms