Unable to discover the Oracle Exadata Database Machine through Enterprise Manager Cloud Control 12c

Asset ID:	1-72-1487737.1
Update Date:	2012-08-31
Keywords:

Solution Type Problem Resolution Sure

Solution 1487737.1 : Unable to discover the Oracle Exadata Database Machine through Enterprise Manager Cloud Control 12c

Applies to:

Enterprise Manager for Exadata - Version 12.1.0.2.0 and later
Exadata Database Machine V2 - Version Not Applicable and later
Oracle Exadata Hardware - Version 11.2.1.2.1 to 11.2.3.1.1 [Release 11.2]
Information in this document applies to any platform.

Symptoms

Enterprise Manager Cloud Control 12c is unable to automatically or manually discover the components of the Oracle Exadata Database Machine.

Error received when clicking 'next' on this page....

Cause

The reason why the components were not being discovered by 12c EM was because the compute nodes (database nodes) did not have the proper node description information.

We can see this from the ibnetdiscover output below - it's missing the ip address information for dbnodes:

[30] "H-00212800013e6af2"[1](212800013e6af3) # "dmorldb01 HCA-1" lid 44 4xQDR

[28] "H-00212800013e6a42"[1](212800013e6a43) # "dmorldb02 HCA-1" lid 42 4xQDR

[27] "H-00212800013e726a"[1](212800013e726b) # "dmorldb03 HCA-1" lid 34 4xQDR

This description information is needed for tools like ibnetdiscover & infinicheck. The 12c EM discovery process was affected, because EM discovers components using ibnetdiscover.

Typically, we would correct this issue by executing the /opt/oracle.cellos/ib_set_node_desc.sh on the compute nodes and this would set the node description with the correct data.

However, a problem was found in the 11.2.3.1 verions of the ib_set_node_desc.sh script. The script is looking for bondib0 and since this is a V2 machine, it was originated with a pre-11.2.2.2.0 release which configured the infiniband interface as bond0 and not bondib0. Therefore, the ib_set_node_desc.sh script does not set the node description correctly.

This is a known issue described in bug 14373741

Solution

To resolve this issue you will need to download file ib_set_node_desc.sh script attached to this note. This file is part of the 11.2.3.2.0 image. Run the script on each compute node which will fix the node description. and allow ibnetdiscover to correctly identifed the compute nodes.

After the script has been run, you should be able to progress with the discovery of the Oracle Exadata Database Machine through Enterprise Manager Cloud Control 12c.

References

<BUG:14373741> - IB_SET_NODE_DESC.SH DOES NOT HANDLE BOND0 INTERFACES
<NOTE:1379836.1> - Unable to discover Exadata DBM in EM 12c,

Attachments

This solution has no attachment