Unable To Create New vServers Associated With An EoIB Network After Exalogic 220.127.116.11.2 Patching
(Doc ID 1944362.1)
Last updated on JUNE 04, 2021
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.2 to 22.214.171.124.2
Information in this document applies to any platform.
You have an Exalogic Virtual system that has recently been patched to the Exalogic Elastic Cloud Software (EECS) 126.96.36.199.2 patch level via Exalogic Patch Set Update (PSU) for July 2014 (<PATCH:18630693>). Prior to patching you were able to successfully create guest vServers that were associated with the EoIB networks but since patching, while you are able to successfully create vServers that use only IPoIB networks, attempts to create any vServers associated with at least one EoIB network fail with the following pop-up dialog being displayed to the Enterprise Manager OpsCenter (EMOC) browser and no EMOC "Job" being created:
The following error is present within the OEM-EC component's emoc.log file (/var/opt/sun/xvm/logs/emoc.log):
The error was introduced after applying the Exalogic Patch Set Update (PSU) for July 2014 (<PATCH:18630693>) to upgrade the Exalogic Elastic Cloud Software to the EECS 188.8.131.52.2 patch level.
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
|Steps to Fix-Up EMOC Model (To be performed by OpsCenter Engineering on a Web Conference)|