Memory issues after installing OER

OER assetsAfter installing Oracle Enterprise Repository (OER) we experience some memory issues. Besides the messages in the log files, we also couldn’t use the console and em as we did before (when we were just running SOA Suite). It turned out the installation of OER in the same Weblogic domain resulted in some unexpected things.

The WebLogic Server and SOA Suite are started using the startWebLogic script (for windows .cmd and on Linux/Unix .sh). This script uses the setDomainEnv script to set the environment variable for the domain. The setDomainEnv script in turn calls the setSOADomainEnv that actually sets the USER_MEM_ARGS. That in the end are used in the startWebLogic script.

After the installation of OER the setDomainEnv not only calls the setSOADomainEnv. It also calls a script that sets the USER_MEM_ARGS for the oer_server in the domain. Apparently the memory required for OER is less than needed for the SOA Suite. Since the script for OER is executed last, memory setting remain low. As shown in the smippet taken from the setDomainEnv.cmd:

call "%WL_HOME%\common\bin\commEnv.cmd"
call "%DOMAIN_HOME%\bin\setSOADomainEnv.cmd"
call "%DOMAIN_HOME%\bin\setOERDomainEnv.cmd"

To solve the memory issue when starting the WebLogic Server using the startWebLogic script we alter the sequence so the setOERDomainEnv.cmd goes before the setSOADomainEnv.cmd.

If the installer put a second call to setSOADomainEnv.cmd in the setDomainEnv.cmd. That doesn’t work because the setSOADomainEnv.cmd contains the following check:

REM Skip running this script again if it was run once
if "%XENGINE_DIR%" == "" goto set_env
echo *********************************************************
echo ** SOA specific environment is already set. Skipping ...
goto end_set_env


One thought on “Memory issues after installing OER

  1. Pingback: Blog: Memory issues after installing OER | Oracle, SOA | Syngu

Leave a Reply

Your email address will not be published. Required fields are marked *