OracleTextSearch PGA Size Grows Uncontrollably When Using Custom AUTO_LEXER Configuration
(Doc ID 1297910.1)
Last updated on SEPTEMBER 23, 2021
Applies to:Oracle WebCenter Content - Version 10.0 and later
Information in this document applies to any platform.
When performing a (quick) search on a UCM instance that is configured using OracleTextSearch with the AUTO_LEXER on an Oracle RDBMS 188.8.131.52, the Oracle database process memory increases to several hundreds of megabytes and does not decrease. Subsequent searches will continue to allocate more memory on the database host until all available memory is consumed.
On windows, you may notice that the oracle.exe grows to consume all available memory and grow to several gigabytes.
After running the search, the following SQL statement shows that the "total PGA inuse" and "total PGA allocated" increases significantly, while only a limited amount of PGA memory is marked "freeable":
NOTE: If you are not using the AUTO_LEXER (or are on the 184.108.40.206 patch set and still observe excessive memory allocation) then please take a look at the issue described in <Document 1065852.1> "OracleTextSearch Database's PGA Size Grows Uncontrollably".
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