Exadata Database Machine Discovery Fails: The selected compute node is not an existing host target
(Doc ID 1439314.1)
Last updated on SEPTEMBER 24, 2021
Applies to:
Enterprise Manager for Exadata - Version 12.1.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
Unable to add Exadata targets (Compute Nodes, Storage cells, IB switches, PDUs etc) into Cloud Control 12c
While discovering an Exadata Database Machine target, Step 2 of 7 fails to advance to the next step and displays the following error message:
The screen displaying the Database Machine Discovery components will list the compute nodes using the public domain names, rather than the management domain names.
For example:
exa01.public.####.com
instead of
exadb01.management.####.net
Changes
Configured the Exadata Machine with different domains for Public and Management networks.
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 |