EMOC failed to create a vServer due to incorrect view of memory on compute nodes (Doc ID 1682091.1)

Last updated on MARCH 06, 2015

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.4.0.2 and later
Enterprise Manager Ops Center - Version 12cR2 (12.2) to 12cR2 (12.2) [Release 12.0]
Information in this document applies to any platform.

Symptoms

You are using an Exalogic system that is running on an Exalogic Elastic Cloud Software (EECS) version 2.0.4.0.2 that is deployed in a virtual configuration. You have changed the root password for one or more compute nodes and updated the corresponding credentials stored within Enterprise Manager OpsCenter Control (EMOC) as instructed by the following Oracle documentation:

Oracle Exalogic Elastic Cloud
Credentials Management Guide
Release EL X2-2, X3-2 and X4-2
E38253-02
April 2014

Section 2.1.2, "Synchronizing Compute-Node root Passwords with Enterprise Manager Ops Center"


Which can be downloaded from an attachment provided by the following support note:

<NOTE:1594316.1>
Oracle Exalogic Elastic Cloud - Credentials Management Guide


However, following this you may have observed one or more of the following symptoms when creating Guest Virtual Servers using the (EMOC) browser interface:

  1. you may have seen the vServer created on an unexpected node, where the level of free vCPU/Memory is less than on other nodes
  2. vServer creation sometimes fails because the selected node has significantly less memory free than would be expected to successfully start the vServer
  3. In the EMOC browser UI, after selecting the Oracle Virtual Server icon nested under a compute node in the "Assets" accordion panel:

    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