Enterprise Command Center (ECC) Installation During Domain Configuration Fails With 404 Error And "Unable to resolve 'eccdb'. Resolved ''; remaining name 'eccdb'" Error
(Doc ID 2949829.1)
Last updated on JUNE 18, 2024
Applies to:
Oracle Enterprise Command Center Framework - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
When attempting to run the envSetup.sh to configure the ECC domain step for Enterprise Command Center (ECC), the configuration fails and below errors are seen:
setup.log under $ECC_HOME\Oracle\quickInstall\logs showed below:
Configured the ECC domain successfully.Starting zookeeper ... STARTED
Zookeeper started. Starting Managed Server
Starting the eccManaged ...
Started the eccManaged successfully
ECC WEB ENTRY URL:http://xxxx:7776/ecc ECC Application File:/xx/ECC/Oracle/quickInstall/applications/activity_audit_ecc.zip ERROR: Failed with status 404 for url http://xxx:7776/ecc/user/import/applications?gfmString= Please check the log: Error 404--Not Found. The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
ecc.log under $ECC_HOME\Oracle\quickInstall\logs\ecc showed below error:
activation state to true for the application "ecc".
weblogic.application.ModuleException: javax.naming.NameNotFoundException: Unable to resolve 'eccdb'. Resolved ''; remaining name 'eccdb'
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
The issue can be reproduced at will with the following steps:
1. Setup Oracle ECC 12.2.x by installing the version and following steps as per Doc ID: 2870143.1
2. Finish steps for installing admin server and managed server.
3. Configure the Create ECC domain step and check to see if the step completes and data sources are setup correctly.
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 |
Cause |
Solution |
References |