DDocAccount Not Staying Optimized From Configuration Manager After Server Restart
(Doc ID 2797817.1)
Last updated on AUGUST 09, 2021
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
We are trying to implement this note: <Note 1940525.1> Searches Fail With Error "DRG-51030: wildcard query expansion resulted in too many terms"Doc ID 1940525.1)
However, after setting dDocAccount to "Is Optimized" from configuration manager and restarting the server, dDocAccount fiield does not have the IsOptimized status as expected.
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