Discovering Additional Exadata DBM Fails. Message Indicates Partitioned Setup (Doc ID 1554210.1)

Last updated on JULY 24, 2013

Applies to:

Enterprise Manager for Exadata - Version 12.1.0.1.0 to 12.1.0.3.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Unable to discover additional independent full rack Exadata Database Machine (DBM).

 

The Discovery Wizard reports:

-----------------------------------------------
This partitioned Oracle Exadata Database Machine target will use the existing
Infiniband switch targets added in the first partitioned DB Machine target. There is no need to
select any Infiniband switch targets.

-----------------------------------------------

 

However, this is NOT a partitioned setup.  There are two full racks: Production and DR.

The Production DBM is discovered successfully.


While discovering the DR rack, the discovery page shows all compute nodes, cell nodes, and ibswitches fine but doesn't allow us to select any of the IB switches.

Infiniband Switches listed are:

ldnps02sw-ib1.intranet.barcapint.com SUN DCS 36P QDR
ldnps02sw-ib2.intranet.barcapint.com SUN DCS 36P QDR
ldnps02sw-ib3.intranet.barcapint.com SUN DCS 36P QDR


Since the console didn't allow to select  any of the switches from this page, if you click next it shows following error:


"There must be at least one compute node, one oracle exadata storage server,
and one Infiniband switch in the oracle Exadata Database Machine"

-- This is not Paritioned setup, but it appears that EM thinks it is.

If we delete the Production Exadata targets from previous successful discovery then attempt discovery of the DR rack again, no errors are reported and discovery works fine.  But after discovering DR rack, the same issue is faced for Production.

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