Exalogic: ExaBR Fails To Start Control-Stack vServers On Correct Designated Compute Nodes
(Doc ID 2620630.1)
Last updated on NOVEMBER 14, 2022
Applies to:
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.1 and laterExalogic Elastic Cloud X3-2 Hardware - Version X3 and later
Exalogic Elastic Cloud X4-2 Hardware - Version X4 and later
Exalogic Elastic Cloud X5-2 Hardware - Version X5 and later
Exalogic Elastic Cloud X6-2 Hardware - Version X6 and later
Linux x86-64
Oracle Virtual Server x86-64
Symptoms
In Exalogic Virtual racks, ExaBR failing to start the Exalogic control stack vServers on designated compute nodes is seen.
Note:
In EECS v2.0.6.0.0, the Exalogic Control VMs are distributed over fewer compute nodes: two nodes in the case of a fresh EECS v2.0.6.0 installation, and three nodes if you upgrade from EECS v2.0.4.x to 2.0.6.0.0
|
Exalogic Control Component |
Exalogic Control vServer “Simple” Name |
Compute node (default) hosting the Exalogic Control vServer |
||
|---|---|---|---|---|
|
Fresh installation |
Upgrade |
Fresh installation |
Upgrade |
|
|
DB, OVMM, and EC |
ExalogicControl |
ExalogicControlOVMM |
cn01 |
cn01 |
|
PC1 |
ExalogicControlOpsCenterPC1 |
ExalogicControlOpsCenterPC1 |
cn01 |
cn03 |
|
PC2 |
ExalogicControlOpsCenterPC2 |
ExalogicControlOpsCenterPC2 |
cn02 |
cn02 |
We have seen instances where ExaBR is starting all three control stack VMs on the same compute node and failing to place them on the default designated nodes.
Changes
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 |