Thursday, February 23, 2012

Grid 11g:"Siebel Discovery Agent is not installed at one or more hosts" trying to discover Siebel topology

We installed agents in all our 4 Siebel servers, let's say named sappl1, sappl2, sappl3 and sappl4.
Under Hosts Tab we see they are up.
When we tried to discover Siebel topology, we got errors:
Discovery Summary
Add Enterprise operation is not successful.  Resolve the error messages and then try again

Error Messages
     Siebel Discovery Agent is not installed at one or more hosts
     Discovery From Gateway Server Failed

Trace Messages
     Discovered the Siebel topology from Gateway Server

In our OMS server, in ../gc_inst/em/EMGC_OMS1/sysman/log/emoms.trc, there were these entries:
2012-02-23 09:12:26,891 [Thread-114] ERROR enterprise.TDProcConfig log.625 - doConfiguration: There are some issues with respect to Agents.
2012-02-23 09:12:26,891 [Thread-114] ERROR enterprise.TDProcConfig log.625 - doConfiguration: Agent erros out for host  sapp3 with message : .Siebel Discovery Agent is not installed at one or more hosts
2012-02-23 09:12:26,891 [Thread-114] ERROR enterprise.TDProcConfig log.625 - doConfiguration: Agent erros out for host  sapp2 with message : .Siebel Discovery Agent is not installed at one or more hosts
2012-02-23 09:12:26,891 [Thread-114] ERROR enterprise.TDProcConfig log.625 - doConfiguration: Agent erros out for host  sapp4 with message : .Siebel Discovery Agent is not installed at one or more hosts

Names sapp2, sapp3, sapp4 were not correct.
OMS had discovered the servers as "sapplX".
In Siebel servers' /etc/hosts file the entries were:
10.101.1.17    sapp1        sappl1
10.101.1.18    sapp2        sappl2
10.101.1.19    sapp3        sappl3
10.101.1.20    sapp4        sappl4

We changed the order:
10.101.1.17    sappl1        sblapp1
10.101.1.18    sappl2        sblapp2
10.101.1.19    sappl3        sblapp3
10.101.1.20    sappl4        sblapp4

Discovery will succeed this time.
Posted by
Labels: , ,

3 comments:

  1. JeetJune 6, 2012 at 2:07 AM

    Hi,

    Recently we came accross with the same error as described in your post but we are not able to discover the agent even after adding entrie into gateway serve /etc/hosts file.

    Below are the steps we did and configuration-

    11g Agent is running fine on all servers and all targets are identified in the grid control but when i try to add a enterprise it gives me the error below -

    Discovery From Gateway Server Failed
    Siebel Discovery Agent is not installed at one or more hosts

    We have following servers -

    Siebel server - stgchub004
    Siebel server - stgchub003
    Gateway server - stgchub005

    /etc/hosts file for stgchub003
    [stgchub003]/chub/apps/emagent/agent11g/bin>cat /etc/hosts
    #
    # Internet host table
    #
    ::1 localhost
    127.0.0.1 localhost
    10.133.233.57 stgchub003 loghost
    ====================================

    /etc/hosts file for stgchub004

    [stgchub004]/chub/apps/emagent/agent11g/sysman/log>cat /etc/hosts
    #
    # Internet host table
    #
    ::1 localhost
    127.0.0.1 localhost
    10.133.233.60 stgchub004 loghost
    10.133.233.60 stgchub004.unix.gsm1900.org loghost
    ================================
    entry in stgchub005

    [stgchub005]/chub/apps/emagent/agent11g/bin>cat /etc/hosts
    #
    # Internet host table
    #
    ::1 localhost
    127.0.0.1 localhost
    10.133.233.63 stgchub005
    10.133.233.63 stgucm_stgchub005

    ===============================

    From the OMS server trace files we found below errors -

    tstogrd001:oracle:/orasw/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log: more emoms.log
    2012-06-05 15:56:12,620 [EMUI_15_56_12_/console/functions$target=stgchub005$host=stgchub005$pageType=byDay$type=host] WARN util.PAUtil loadCheckPrivilegesFlag.923 - Unable to load privilege check
    flag
    2012-06-05 15:56:12,620 [EMUI_15_56_12_/console/functions$target=stgchub005$host=stgchub005$pageType=byDay$type=host] WARN ui.ProvisioningAdvisorSection InitializeSection.259 - Unable to check whe
    ther user has PAF privileges. Rejecting access by default.
    2012-06-05 15:56:16,636 [XMLLoader0 60000294666.xml] ERROR loader.XMLLoader LoadFiles.720 - Error while processing 60000294666.xml:
    java.sql.SQLException: ORA-20801: ECM load failed: Metadata does not exist for target type oracle_database and snapshot type streams_processes_count_item
    ORA-06512: at "SYSMAN.ECM_CT", line 324
    ORA-06512: at line 1
    ORA-06512: at "SYSMAN.EMD_LOADER", line 5184
    ORA-06512: at line 1

    =======================

    Can you help us to know what exactly we need to add in /etc/hosts file of all servers.

    your help is very much appreciated.

    Thanks,
    Jeet

    ReplyDelete
    Replies
    1. Lefteris TsekourasJune 6, 2012 at 9:56 AM

      Hello.
      This doesn't look exactly like the case I had, since you have different errors in your emoms.log.
      Try the following.
      Check how are your hosts discovered by OMS, shortname or fullname.
      For me, it's shortname: sblappl1, sblappl2, sblappl3, sblappl4. Not sblappl1.ote.gr
      Now, edit /etc/hosts and leave only 1 line for each server.
      Mine is:
      127.0.0.1 loopback localhost # loopback (lo0) name/address
      10.101.1.18 sblappl2 sblapp2
      10.101.1.17 sblappl1 sblgwvip sblapp1
      10.101.1.19 sblappl3 sblapp3
      10.101.1.20 sblappl4 sblapp4 ucmgwvip ucmgwvip.ote.gr

      Also, remove the IPv6 entries "::1 localhost".
      OMS has a lot of issues caused by this.

      Delete
  2. JeetJune 8, 2012 at 7:42 PM

    Hi ,

    Thank you sir for your update.

    To let you know issue got resolved following the below steps-

    1.Changed in the /etc/hosts entry of Gateway server with short name & FQDN of all siebel servers
    2.Following the doc -Unknown Exception During Siebel Discovery [ID 1319925.1]
    3.Stop&start Agent

    Hope this may help someone in future.

    Thanks & Regards,
    Jeet

    ReplyDelete

Subscribe to: Post Comments (Atom)