Can the Oracle Text Optimization process be permanently disabled inside WebCenter Content?
(Doc ID 2409094.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
It's not recommended to launch the optimizer from the WebCenter Content server.
This can cause indexing of new items to slow or hang.
Instead it's recommended to run the optimizer directly on the database server.
See <Note: 1087777.1> Index Fragmentation and Optimization When Using OracleTextSearch or DATABASE.FULLTEXT for the details on how to set it to run as a scheduled job on the DB server.
How do you disable the optimization process from running as a WCC scheduled job?
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