Exalogic: ExaBR Fails To Start Control-Stack vServers On Correct Designated Compute Nodes (Doc ID 2120483.1)

Last updated on JULY 10, 2016

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.1 to 2.0.6.2.2
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. This issue is seen only when restart of Control vServers is done via ExaBR when the Control vServers are running on Compute Nodes which are not the designated Compute Nodes 

For e.g. for maintenance activity, if control stack vServers were restarted on other compute nodes other than CN01, CN02, CN03, if we restart the Control stack vServers using ExaBR, they will be restarted on same Compute Nodes where they were running before and not on the designated compute nodes.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms