12c Cloud Control: Additional OMS Installation Fails With Errors 'java.lang.OutOfMemoryError: Java heap space' (Doc ID 1491413.1)

Last updated on AUGUST 01, 2015

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.

Symptoms

12c Addition OMS installation using Deployement Procedure failed with the below errors in the primary OMS Adminserver log

<EM_Instance_Home>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out

<Sep 12, 2012 11:27:41 AM EDT> <Warning> <DeploymentService> <BEA-290064> <Deployment service servlet encountered an Exception while handling the deployment service message for request id "-1" from server "EMGC_OMS2". Exception is: "java.lang.OutOfMemoryError: Java heap space
".>
<Sep 12, 2012 11:27:42 AM EDT> <Error> <HTTP> <BEA-101017> <[ServletContext@2065979533[app:bea_wls_deployment_internal module:bea_wls_deployment_internal.war path:/bea_wls_deployment_internal spec-version:null]] Root cause of ServletException.
java.lang.OutOfMemoryError: Java heap space
>
<Sep 12, 2012 11:27:42 AM EDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server EMGC_OMS2 : Exception while starting server 'EMGC_OMS2'>

 

The following error is displayed in the Cloud Control console:

Securing OMS ...... java.lang.Exception: Failed to start OMS at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.adapter.wls.OMSWLSAdapter.bounceOMS(OMSWLSAdapter.java:3164) at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.adapter.wls.OMSWLSAdapter.adapterPostDeployAndReposSetup(OMSWLSAdapter.java:3073) at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.framework.OMSGenericAdapter.postDeployAndReposSetup(OMSGenericAdapter.java:327) at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.framework.OMSCARecoveryConfig.execAddOMS(OMSCARecoveryConfig.java:916) at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.framework.OMSCARecoveryConfig.execute(OMSCARecoveryConfig.java:632) at oracle.<span class="hiddenSpellError" pre="">sysman</span>.<span class="hiddenSpellError" pre="">omsca</span>.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:211) OMSCA-ERR:Bounce OMS failed. OMSCA-ERR:Post "Deploy and Repos Setup" operations failed. Check the trace file:/u01/middleware/oms/cfgtoollogs/omsca/omsca_20120204074549.log Add OMS failed OMS CA recover failed Error:Can not recover destination oms. &nbsp;

On the Additional OMS machine, the file <OMS_HOME>/cfgtoollogs/omsca/logs<timestamp>/msLogs/EMGC_OMS2.out contains:

<Sep 12, 2012 11:04:05 AM EDT> <Info> <Management> <BEA-141223> <The server name EMGC_OMS2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {EMGC_ADMINSERVER}.> 
 <Sep 12, 2012 11:04:05 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: 
 
 There are 1 nested errors:
 
 weblogic.management.ManagementException: [Management:141223]The server name EMGC_OMS2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {EMGC_ADMINSERVER}.
 &nbsp;&nbsp; &nbsp;at weblogic.management.provider.internal.RuntimeAccessImpl.&lt;<span class="hiddenSpellError" pre="">init</span>&gt;(RuntimeAccessImpl.java:149)
 &nbsp;&nbsp; &nbsp;at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
 &nbsp;&nbsp; &nbsp;at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
 &nbsp;&nbsp; &nbsp;at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
 &nbsp;&nbsp; &nbsp;at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
 &nbsp;&nbsp; &nbsp;at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
 &nbsp;&nbsp; &nbsp;at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
 &nbsp;&nbsp; &nbsp;at weblogic.Server.main(Server.java:71)
 
 &lt;Sep 12, 2012 11:04:05 AM EDT&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to FAILED&gt; 
 &lt;Sep 12, 2012 11:04:05 AM EDT&gt; &lt;Error&gt; &lt;WebLogicServer&gt; &lt;BEA-000383&gt; &lt;A critical service failed. The server will shut itself down&gt; 
 &lt;Sep 12, 2012 11:04:05 AM EDT&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to FORCE_SHUTTING_DOWN&gt; 
 &lt;Sep 12, 2012 11:04:05 AM&gt; &lt;FINEST&gt; &lt;NodeManager&gt; &lt;Waiting for the process to die: 8065&gt;
 &lt;Sep 12, 2012 11:04:05 AM&gt; &lt;INFO&gt; &lt;NodeManager&gt; &lt;Server failed during startup so will not be restarted&gt;

 

Cause

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