Exalogic Virtual: "Add Asset" Job For Compute Node Fails In PopulateModel Task Due To "correlation error" Resulting From Left Over Model Objects Not Deleted By The Preceding "Delete Asset" Job For That Particular Compute Node
Last updated on APRIL 21, 2016
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.0 and later
Oracle Virtual Server x86-64
You have an Exalogic Virtual system where, in an effort to have a compute node's properties re-examined and updated within the Enterprise Manager OpsCenter (EMOC) model, you elected to invoke a "Delete Asset" operation on a specific compute node so you would later be able to invoke a subsequent "Add Asset" job to re-discover it's properties.
However, the "Add Asset" job unexpectedly FAILED and as a result the compute node has not re-appeared under the "Assets" accordion panel so that you can launch a further "Add Asset" job to rediscover the node's Integrated Lights Out Management (ILOM) device.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms