EM 12c: Deployment of the Golden Gate (oracle.fmw.gg) Plug-in to the Enterprise Manager 12c Cloud Control OMS Fails with EM-04001 Error (Doc ID 1564814.1)

Last updated on MAY 06, 2016

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.2.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Enterprise Manager 12c Cloud Control OMS plugin (oracle.fmw.gg:12.1.0.1.0:0) deployment failure results in OMS startup failure.

 

The following is logged in .../<OMS_HOME>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out:

<Jun 25, 2013 7:39:01 PM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jun 25, 2013 7:39:11 PM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jun 25, 2013 7:39:21 PM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jun 25, 2013 7:39:31 PM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
<Jun 25, 2013 7:39:36 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: Unable to obtain lock on /ora/app/oracle/product/Middleware/gc_inst12cr2/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/tmp/EMGC_ADMINSERVER.lok. Server may already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:206)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:67)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)

>
<Jun 25, 2013 7:39:36 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 25, 2013 7:39:36 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 25, 2013 7:39:36 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 25, 2013 7:39:36 PM> <FINEST> <NodeManager> <Waiting for the process to die: 15073400>

 

The following is logged in the /ora/app/oracle/product/Middleware/oem12cr2/oms/cfgtoollogs/pluginca/plugin_deployment_1/configplugin_all_<date_stamp>.log

2013-06-24 13:14:42,853 [main] WARN  pluginca.PluginCADriver - ---------------------------------------------------------------
2013-06-24 13:14:42,853 [main] WARN  pluginca.PluginCADriver - ---Plugins On Which Action "Deployment(all)" Is To Be Performed---
2013-06-24 13:14:42,853 [main] WARN  pluginca.PluginCADriver -            oracle.fmw.gg:12.1.0.1.0:0
2013-06-24 13:14:42,854 [main] WARN  pluginca.PluginCADriver - ---------------------------------------------------------------
2013-06-24 13:14:42,854 [main] WARN  pluginca.PluginCADriver -
2013-06-24 13:14:49,374 [main] WARN  deploymentservice.EMPluginDeploymentUtil - No OMS name property passed. Assuming there is only one entry in emInstanceMapping.properties.
2013-06-24 13:14:52,744 [main] WARN  pluginca.PluginCABackup - Adding step PRE_DEPLOY_CALLBACK which is not recognized by pluginca backup system.
2013-06-24 13:14:52,892 [main] WARN  pluginca.PluginCABackup - Adding step POST_DEPLOY_CALLBACK which is not recognized by pluginca backup system.
2013-06-24 13:23:51,881 [pool-2-thread-1] ERROR pluginca.MidtierConfigStep - EM-04001: Server side Plug-in deployment failed with message Error while attempting to deploy plug-in templates to EM domain: Unable to start OMS. Contact Oracle Support
oracle.sysman.core.common.extensibility.pluginca.PluginCAException: EM-04001: Server side Plug-in deployment failed with message Error while attempting to deploy plug-in templates to EM domain: Unable to start OMS. Contact Oracle Support
at oracle.sysman.core.common.extensibility.pluginca.PluginCARunnable.setError(PluginCARunnable.java:158)
at oracle.sysman.core.common.extensibility.pluginca.PluginCARunnable.setError(PluginCARunnable.java:129)
at oracle.sysman.core.common.extensibility.pluginca.PluginCARunnable.setError(PluginCARunnable.java:88)
at oracle.sysman.core.common.extensibility.pluginca.MidtierConfigStep.run(MidtierConfigStep.java:215)
at oracle.sysman.core.common.extensibility.pluginca.PluginCASerialStepsExecutor.run(PluginCASerialStepsExecutor.java:80)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
Caused by:
java.lang.Exception: Unable to start OMS
at oracle.sysman.core.common.extensibility.pluginca.util.PluginCAUtil.startOMS(PluginCAUtil.java:238)
at oracle.sysman.core.common.extensibility.pluginca.PluginTemplateDeployer.deployAllTemplates(PluginTemplateDeployer.java:60)
at oracle.sysman.core.common.extensibility.pluginca.MidtierConfigStep.run(MidtierConfigStep.java:210)
... 7 more
2013-06-24 13:23:51,942 [pool-2-thread-1] WARN  pluginca.PluginCASerialStepsExecutor - Fatal error encountered. Not continuing with any further step
2013-06-24 13:23:51,944 [main] WARN  pluginca.PluginCADriver - Not running check point oracle.sysman.core.common.extensibility.pluginca.checkpoints.DbObjectValidityCheckPoint since a fatal error has encountered before
 



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