EM 13c 无法自动发现集群目标

郑全

EM 12c, EM 13c: Failed To Discover Clusterware Target From EM console, Error: No Cluster Was Found On The Host (Doc ID 1941647.1)

In this Document
Symptoms
Changes
Cause
Solution
References

APPLIES TO:
Enterprise Manager for Oracle Database - Version 12.1.0.4.0 and later
Information in this document applies to any platform.
SYMPTOMS
Failed to discover clusterware target from EM console, error: No cluster was found on the host




CHANGES


CAUSE
No reference to CRS_HOME in inventory.xml file





SOLUTION
Solution: Open a service request to Oracle Support to fix the inventory and add a relevant entry to the CRS target into inventory.xml

Workaround I: Execute the following commands on all cluster nodes, then try to discover the CRS target from EM console

<AGENT_HOME>/agent_inst/bin/emctl stop agent
export CRS_HOME=<CRS_HOME>
<AGENT_HOME>/agent_inst/bin/emctl start agent
Workaround II: Discovery the cluster target manually by specifying target properties

Setup/add targets/add targets manually
Add Targets Declaratively by Specifying Target Monitoring Properties
Target Type:Cluster
Monitoring Agent: Choose one of the nodes of the cluster
Click on "add manually"
Enter the following details:-

    Target Name: <enter the name of the cluster target*>
    Oracle Home: <oracle home of the cluster*>
    Scan Name: <enter scan name*>
    Scan Port: <enter scan port*>
    ONS Port: <enter ONS port*>

In the section "Cluster Host and High Availability Services Targets" the node which was chosen will be shown.  Click on "add" and choose the other nodes of the cluster.
Click on save

*How to determine the values which need to be supplied:

1) Target Name: The name given to the cluster target.  Get the name of the cluster by running the command "cemutlo -n" .  For example:
$CRS_HOME/bin/cemutlo -n
crs64bitR2
2) Oracle Home: This is the CRS/grid infrastructure home (eg. /u01/app/11.2.0/grid)
3) Scan Name: This can be found by running the command
$CRS_HOME/bin/srvctl config scan
The first line returns the SCAN Name, for example:

$CRS_HOME/bin/srvctl config scan
SCAN name: rachu2-scan, Network: 1/1x.1xx.1xx.x/xxx.xxx.xxx.0/eth0   <<--Look for SCAN name
SCAN VIP name: scan1, IP: /rachu2-scan/xx.xxx.xxx.xx

4) Scan Port: This can be determined by running the command 'srvctl config scan_listener'.  For example:

$CRS_HOME/bin/srvctl config scan_listener
SCAN Listener LISTENER_SCAN1 exists. Port: TCP:1521   <<--Look for TCP:<port #>

5) ONS Port: This can be determined by running the command:

$CRS_HOME/bin/srvctl config nodeapps -s
ONS exists: Local port 6100, remote port 6200, EM port 2016    <<--Look for "EM port"



Example CRS inventory entry on Linux for the 11.2 and later Oracle Database:

$ cat /etc/oraInst.loc | grep inventory_loc
inventory_loc=/home/grid/oraInventory
$ cat /home/grid/oraInventory/ContentsXML/inventory.xml
..
<HOME NAME="Ora11g_gridinfrahome1" LOC="/ocw/grid" TYPE="O" IDX="4" CRS="true">
   <NODE_LIST>
      <NODE NAME="racnode1"/>
      <NODE NAME="racnode2"/>
      <NODE NAME="racnode3"/>
   </NODE_LIST>
</HOME>
..

Note: inventory.xml must not be modified manually to avoid inventory corruption.
Reference: Note 1053393.1 How to Update Inventory to Set/Unset "CRS=true" Flag for Oracle Clusterware Home