Endeca MDEX Memory Reaching Limit Of Host (Doc ID 1601911.1)

Last updated on DECEMBER 14, 2016

Applies to:

Oracle Endeca Guided Search / Endeca Experience Manager - Version 6.2.2 and later
Information in this document applies to any platform.


 In an environment the MDEX engine now increases to use all of the RAM on the host and performance suffers as the system starts to swap.


 The --cmem dgraph argument was recently increased to utilize extra RAM available on the host, or alternately a significant amount of new data was added to your indexes.


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