Unable To Start ESSAPP due to ESS-01173 Runtime store status check failed; runtime store status: INVALID
(Doc ID 2234035.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On a recently created SOA domain in PROD. The below error shows in the logs and the application ESSAPP is unable to start.
oracle.as.scheduler.runtime.RuntimeStoreCompatibilityException: ESS-01173 Runtime store status check failed; runtime store status: INVALID, schema name: SOA1_ESS
at oracle.as.scheduler.runtime.jdbc.RtsSchemaInfo.checkSchemaCompatibility(RtsSchemaInfo.java:219)
at oracle.as.scheduler.runtime.jdbc.RtsSchemaInfo.checkRuntimeStoreCompatibility(RtsSchemaInfo.java:133)
at oracle.as.scheduler.runtime.jdbc.RtsInstanceManager.checkRuntimeStoreCompatibility(RtsInstanceManager.java:1226)
at oracle.as.scheduler.runtime.InstanceCoordinationManager.checkRuntimeStoreCompatibility(InstanceCoordinationManager.java:344)
at oracle.as.scheduler.adapter.ra.InstanceManager.checkRuntimeStoreCompatibility(InstanceManager.java:502)
at oracle.as.scheduler.adapter.ra.RAImpl.checkRuntimeStoreCompatibility(RAImpl.java:2965)
at oracle.as.scheduler.adapter.ra.RAImpl.endpointActivation(RAImpl.java:840)
at weblogic.connector.security.layer.AdapterLayer.endpointActivation(AdapterLayer.java:994)
at weblogic.connector.external.impl.EndpointActivationUtils.activateEndpoint(EndpointActivationUtils.java:148)
at weblogic.ejb.container.internal.JCABindingManager.connect(JCABindingManager.java:81)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPolling(MDConnectionManager.java:203)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDrivenManager.java:425)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.startManager(MessageDrivenBeanInfoImpl.java:1248)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessageDrivenBeans(MessageDrivenBeanInfoImpl.java:12
at oracle.as.scheduler.runtime.jdbc.RtsSchemaInfo.checkSchemaCompatibility(RtsSchemaInfo.java:219)
at oracle.as.scheduler.runtime.jdbc.RtsSchemaInfo.checkRuntimeStoreCompatibility(RtsSchemaInfo.java:133)
at oracle.as.scheduler.runtime.jdbc.RtsInstanceManager.checkRuntimeStoreCompatibility(RtsInstanceManager.java:1226)
at oracle.as.scheduler.runtime.InstanceCoordinationManager.checkRuntimeStoreCompatibility(InstanceCoordinationManager.java:344)
at oracle.as.scheduler.adapter.ra.InstanceManager.checkRuntimeStoreCompatibility(InstanceManager.java:502)
at oracle.as.scheduler.adapter.ra.RAImpl.checkRuntimeStoreCompatibility(RAImpl.java:2965)
at oracle.as.scheduler.adapter.ra.RAImpl.endpointActivation(RAImpl.java:840)
at weblogic.connector.security.layer.AdapterLayer.endpointActivation(AdapterLayer.java:994)
at weblogic.connector.external.impl.EndpointActivationUtils.activateEndpoint(EndpointActivationUtils.java:148)
at weblogic.ejb.container.internal.JCABindingManager.connect(JCABindingManager.java:81)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPolling(MDConnectionManager.java:203)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDrivenManager.java:425)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.startManager(MessageDrivenBeanInfoImpl.java:1248)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessageDrivenBeans(MessageDrivenBeanInfoImpl.java:12
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 |