Exalogic Virtual: EMOC Jobs Fails Due To Local Derby Database Corruption In A ProxyController
(Doc ID 2042007.1)
Last updated on FEBRUARY 24, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.1 and later
You have an Exalogic Virtual system where you have previously been able to successfully to create new guest vServers that has developed a problem preventing you from creating further new vServers:
- While creating a new vServer via the browser based user interface of the Enterprise Manager OpsCenter Control (EMOC) when click on Finish on the final page of the "Create vServer" wizard a pop-up error is displayed and no EMOC job is created.
- In addition, within the EMOC "Administration" accordion panel the icon for one of the ProxyController instances is displayed with a moniker of a white "?" on an orange square (indicating it is not reachable), even though you have confirmed that the ProxyController vServer in question is running and the proxyadm service has been started.
If you have encountered this problem then, shortly after stopping and restarting the ProxyController instance that is displayed with the warning moniker, you will see the following messages within the cacao.0 log file (/var/opt/sun/cacao2/instances/scn-proxy/logs/cacao.0):
There may have recently been an unexpected restart of the Exalogic Control Stack or ProxyController in question due to an abrupt and unexpected shutdown of a vServer within the Exalogic Control Stack.
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