My Oracle Support Banner

EM 13c: Enterprise Manager 13c Cloud Control Command Line Deployment Procedure (emcli submit_procedure) Fails with Message: MissingResourceException...missing its type in the input file (Doc ID 2340528.1)

Last updated on JANUARY 02, 2018

Applies to:

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

Symptoms

Executing a deployment procedure in Enterprise Manager (EM) 13c Cloud Control using an "emcli submit_procedure" command results in the following error:

emcli>submit_procedure(name="TEST_DISPATCH_PROCEDURE",input_file="data:submit_config.properties",instance_name="SUBMIT TEST PROCEDURE")
Internal Error: The EM CLI system has encountered an internal error. Details have been added to the OMS log files.


Similar errors are reported in <OMS instance base>/gc_inst/sysman/log/emoms.log:

2017-12-09 14:40:49,334 [emcli-work-manager:emcli-request] ERROR emCLI.CLIPageHandler executeCommand.2174 - Can't find resource for bundle oracle.sysman.emdrep.jobs.procedure.emcli.EmcliMsg, key Target name XXX.host is still present in temporary cache; that means we are missing its type in the input file
java.util.MissingResourceException: Can't find resource for bundle oracle.sysman.emdrep.jobs.procedure.emcli.EmcliMsg, key Target name XXX.host is still present in temporary cache; that means we are missing its type in the input file
at java.util.ResourceBundle.getObject(ResourceBundle.java:395)
at java.util.ResourceBundle.getObject(ResourceBundle.java:392)
at java.util.ResourceBundle.getString(ResourceBundle.java:355)
at oracle.sysman.emdrep.jobs.procedure.emcli.SubmitProcedureVerb.execute(SubmitProcedureVerb.java:306)
at oracle.sysman.emSDK.emCLI.CLIPageHandler.executeCommand(CLIPageHandler.java:2152)
at oracle.sysman.emSDK.emCLI.CLIPageHandler.access$2000(CLIPageHandler.java:168)
at oracle.sysman.emSDK.emCLI.CLIPageHandler$CLIExecutor.executeRequest(CLIPageHandler.java:1461)
at oracle.sysman.emSDK.emCLI.CLIPageHandler$CLIExecutor.doWork(CLIPageHandler.java:1438)
at oracle.sysman.core.common.workmanager.Work.call(Work.java:274)
at oracle.sysman.core.common.workmanager.Work.call(Work.java:50)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

 

017-12-09 14:40:51,865 [AQWorkerThread1122208.b5bffd0e-bd7c-42de-9976-956df9600cc5] WARN procedure.engine logp.251 - diag_bug_20237507_0: detaching from exec 5FE8720BF1D9FE22E053C95D950A7624
2017-12-09 14:40:51,869 [AQWorkerThread1122208.b5bffd0e-bd7c-42de-9976-956df9600cc5] WARN procedure.engine logp.251 - diag_bug_20237507_0: detached from exec 5FE8720BF1D9FE22E053C95D950A7624

 

 

Changes

 Upgrade from EM 12.1.0.5

 

Cause

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
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.