OMS vs Agent version

Is it possible to run OMS Oracle Enterprice Grid Control Version 10.2.0.1.0 with enterprice agents of higher version like 10.2.0.2.0?
- Tommy

Your Enterpise Manager will always come (whether downloaded or CD) with the Installation Guide. In the installation guide for each release, it states the Certified Platform, Respository, Management Service, Managed targets etc.
Anything outside of those stated in the guide and release note is a hack around that you deal with on your own.
So I would suggest you read the Installation Guide for your Release because what works for Ugonic's platform outside the certified ones may not work for Tommy.

Similar Messages

  • Reg  oms and agent versions

    Hi,
    I have enteprise grid 10.2.0.5
    what my question can the oms and agent can be different versions
    like oms is 10.2.0.5
    agent is 10.2.0.3
    thanks

    Use metalink article: 412431.1 as a reference to know which versions are certified.
    If you OMS is 10.2.0.5, you shold upgrade your agent to 10.2.0.5 as well.

  • OMS showing agent unreachable but agent is up

    Greetings !!!!!!!!!!!!!
    When I open the targets I see that for this particular host it is showing agent unreachable but if I do following on hte machine where agent is running I get:
    $ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl status agent -secure
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Checking the security status of the Agent at location set in /u01/app/oracle/product/10.2/agent/agent10g/sysman/config/emd.properties... Done.
    Agent is secure at HTTPS Port 3872.
    Checking the security status of the OMS at http://grid:4889/em/upload/... Done.
    OMS is secure on HTTPS Port 1159
    oracle : dg01 : @test : /u01/app/oracle
    $
    MAy I know why grid is showing hte agent is not reachable even thought the agent is running and can talk to OMS:
    The following is the output from the agent installation machine:
    $ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl status agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.3.0
    OMS Version : 10.2.0.3.0
    Protocol Version : 10.2.0.2.0
    Agent Home : /u01/app/oracle/product/10.2/agent/agent10g
    Agent binaries : /u01/app/oracle/product/10.2/agent/agent10g
    Agent Process ID : 10105
    Parent Process ID : 10062
    Agent URL : https://dg01:3872/emd/main/
    Repository URL : https://grid:1159/em/upload
    Started at : 2008-06-26 00:36:00
    Started by user : oracle
    Last Reload : 2008-06-26 00:36:00
    Last successful upload : 2008-06-26 06:46:03
    Total Megabytes of XML files uploaded so far : 34.76
    Number of XML files pending upload : 0
    Size of XML files pending upload(MB) : 0.00
    Available disk space on upload filesystem : 40.38%
    Last successful heartbeat to OMS : 2008-06-26 06:54:47
    Agent is Running and Ready
    oracle : dg01 : @test : /u01/app/oracle
    $
    Thanks in Advance
    Regards

    Mohammed, thanks for your time and reply and showing consideration to this thread.
    I bounced the agent and got the following:
    $ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl stop agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Stopping agent ... stopped.
    oracle : dg01 : @test : /u01/app/oracle
    $ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl start agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Starting agent ........ started.
    oracle : dg01 : @test : /u01/app/oracle
    $ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl status agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.3.0
    OMS Version : 10.2.0.3.0
    Protocol Version : 10.2.0.2.0
    Agent Home : /u01/app/oracle/product/10.2/agent/agent10g
    Agent binaries : /u01/app/oracle/product/10.2/agent/agent10g
    Agent Process ID : 11692
    Parent Process ID : 11649
    Agent URL : https://dg01:3872/emd/main/
    Repository URL : https://grid:1159/em/upload
    Started at : 2008-06-26 14:32:46
    Started by user : oracle
    Last Reload : 2008-06-26 14:32:46
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 15
    Size of XML files pending upload(MB) : 6.06
    Available disk space on upload filesystem : 40.30%
    Last successful heartbeat to OMS : 2008-06-26 14:32:50
    Agent is Running and Ready
    oracle : dg01 : @test : /u01/app/oracle
    $ date
    Thu Jun 26 10:04:41 PDT 2008
    oracle : dg01 : @test : /u01/app/oracle
    $
    But even now grid is showing me agent not reachable......
    Here are the files that you requested. Can you please tell me the location of emoms.trc, couldn't find it.
    $ ls -lart
    total 1964
    -rw-r----- 1 oracle dba 0 Jun 23 03:05 emdctl.log
    drwxr-xr-x 12 oracle dba 4096 Jun 23 03:05 ..
    -rw-r----- 1 oracle dba 0 Jun 23 03:11 emagentfetchlet.trc
    -rw-r----- 1 oracle dba 0 Jun 23 03:11 emagentfetchlet.log
    -rw-r----- 1 oracle dba 0 Jun 23 03:11 nfsPatchPlug.log
    drwxr-xr-x 2 oracle dba 4096 Jun 23 07:37 .
    -rw-r----- 1 oracle dba 1086 Jun 23 13:21 agabend.log.lr
    -rw-r----- 1 oracle dba 11132 Jun 26 02:21 secure.log
    -rw-r----- 1 oracle dba 1327 Jun 26 10:02 agabend.log
    -rw-r----- 1 oracle dba 348790 Jun 26 10:02 emdctl.trc
    -rw-r----- 1 oracle dba 70426 Jun 26 10:02 emagent.nohup
    -rw-r----- 1 oracle dba 32998 Jun 26 10:02 emagent.log
    -rw-r----- 1 oracle dba 31408 Jun 26 10:03 emctl.log
    -rw-r----- 1 oracle dba 42996 Jun 26 10:04 emagent_perl.trc
    -rw-r----- 1 oracle dba 1425694 Jun 26 10:05 emagent.trc
    oracle : dg01 : @test : /u01/app/oracle/product/10.2/agent/agent10g/sysman/log
    $
    ========================================================
    $ tail -200 emagent.trc
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_timeout does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_total can't define table_name: umsg_pop_connections_count
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_total does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_transmit can't define table_name: umsg_pop_network_transmit
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_transmit does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_receive can't define table_name: umsg_pop_network_receive
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_receive does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric Function calls can't define table_name: mail_pop_functions
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_sarm_overview can't define table_name: siebel_component_sarm_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_task_overview can't define table_name: siebel_component_task_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_overview can't define table_name: siebel_component_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_resource_overview can't define table_name: siebel_component_resource_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_database_overview can't define table_name: siebel_component_database_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_group_overview can't define table_name: siebel_component_group_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelSales can't define table_name: SiebelSalesBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelESales can't define table_name: SiebelESalesBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelService can't define table_name: SiebelServiceBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelSelfService can't define table_name: SiebelSelfServiceBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelMarketing can't define table_name: SiebelMarketingBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelPartnerManagement can't define table_name: SiebelPartnerManagementBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelUniversalCustomerMaster can't define table_name: SiebelUniversalCustomerMasterBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelFinancialServices can't define table_name: SiebelFinancialServicesBusinessMetrics
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_database_overview can't define table_name: siebel_server_database_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_resource_overview can't define table_name: siebel_server_resource_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_overview can't define table_name: siebel_server_overview
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_imap_health
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric uptime does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpi_health
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections can't define table_name: mail_mta_connections
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_current can't define table_name: smtpin_connections_current
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_current does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transmit
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric receive can't define table_name: mail_mta_receive
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_received can't define table_name: umsg_smtpin_messages_received
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_received does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_smtpin_messages_avgsize
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name: umsg_smtpin_messages_avgtime
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmission_response can't define table_name: umsg_smtpin_transmission_reponse
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_connection_total can't define table_name: umsg_smtpin_network_connection_total
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_connection_total does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_receive_bytes can't define table_name: umsg_smtpin_network_receive_bytes
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_receive_bytes does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_receive_dl can't define table_name: umsg_smtpin_message_receive_dl
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_receive_dl does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_deferred can't define table_name: umsg_smtpin_messages_deferred
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_deferred does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgreceip can't define table_name: umsg_smtpin_message_avgreceip
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_avgreceip does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpo_health
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections can't define table_name: mail_mta_connections
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transmit
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_current can't define table_name: umsg_smtpout_connections_current
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_current does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_transmitted can't define table_name: umsg_smtpout_messages_transmitted
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_transmitted does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_smtpout_messages_avgsize
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name: umsg_smtpout_messages_avgtime
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime_local can't define table_name: umsg_smtpout_messages_avgtime_local
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime_remote can't define table_name: umsg_smtpout_messages_avgtime_remote
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgrelay_time can't define table_name: umsg_smtpout_messages_avgtime_relay
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric delivery_performance can't define table_name: umsg_smtpout_delivery_performance
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric relay_performance can't define table_name: umsg_smtpout_messages_avgtime_relay
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric relay_performance does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound can't define table_name: umsg_smtpout_connections_outbound
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound_local can't define table_name: umsg_smtpout_connections_outbound_local
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound_local does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound_remote can't define table_name: umsg_smtpout_connections_outbound_remote
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound_remote does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmitted_bytes can't define table_name: umsg_smtpout_transmitted_bytes
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric transmitted_bytes does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmission_rate can't define table_name: umsg_smtpout_transmission_rate
    2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric transmission_rate does not have any data columns
    2008-06-26 14:32:48 Thread-3086935744 INFO TargetManager: nmeetm_setDynPropReComputeParam: Values have been retrieved dynamicPropReComputeInterval = 120 dynamicPropReComputeMaxTries = 4
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for dg01:3872
    2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Computing dynamic properties for {dg01:3872, oracle_emd}
    2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Computing dynamic property VersionAndLocation of oracle_emd,dg01:3872
    2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Done with dynamic property evaluation for {dg01:3872,oracle_emd}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for dg01:3872, ret=0
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent> Entering function
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: for target {host:dg01} assocName:cluster_instance, assocType:cluster
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_emd:dg01:3872} for inclusion as assoc instance for {host:dg01}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_emd do not match ignoring
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {host:dg01} for inclusion as assoc instance for {host:dg01}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type host do not match ignoring
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_listener:LISTENER_dg01} for inclusion as assoc instance for {host:dg01}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_listener do not match ignoring
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_database:test} for inclusion as assoc instance for {host:dg01}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_database do not match ignoring
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {osm_instance:+ASM_dg01} for inclusion as assoc instance for {host:dg01}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type osm_instance do not match ignoring
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for dg01
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic properties for {dg01, host}
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property from_cluster of host,dg01
    2008-06-26 14:32:48 Thread-32218016 WARN TargetManager: Query returned 0 rows (only one expected) for the dynamic property from_cluster
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property getCRSVCategory of host,dg01
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property Config of host,dg01
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property HardwareInfo of host,dg01
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property esa_dyn_prop of host,dg01
    2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Done with dynamic property evaluation for {dg01,host}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for dg01, ret=0
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for LISTENER_dg01
    2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Computing dynamic properties for {LISTENER_dg01, oracle_listener}
    2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Computing dynamic property esaMaxRowCount of oracle_listener,LISTENER_dg01
    2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Done with dynamic property evaluation for {LISTENER_dg01,oracle_listener}
    2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for LISTENER_dg01, ret=0
    2008-06-26 14:32:48 Thread-3086935744 ERROR TargetManager: Skipping target {test, oracle_database}: Missing properties - password
    2008-06-26 14:32:48 Thread-3086935744 ERROR TargetManager: Skipping target {+ASM_dg01, osm_instance}: Missing properties - password
    2008-06-26 14:32:48 Thread-3086935744 INFO TargetManager: save to targets.xml success
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 INFO TargetManager: TargetManager initialized
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Identity Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by I"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Service Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by S"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Identity Pr"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Identity Provider" is too long, truncating to "Signed Federation Termination Request Received by Identity Provi"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Received Successfully by Identit"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Identity Provider" is too long, truncating to "Signed Federation Termination Response Received by Identity Prov"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Sent Successfully by Identity Provider" is too long, truncating to "Name Registration Response Sent Successfully by Identity Provide"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Identity Provider" is too long, truncating to "Name Registration Response Received Successfully by Identity Pro"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Service Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Service Pro"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Service Provider" is too long, truncating to "Signed Federation Termination Request Received by Service Provid"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Service Provider" is too long, truncating to "Federation Termination Response Received Successfully by Service"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Service Provider" is too long, truncating to "Signed Federation Termination Response Received by Service Provi"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Service Provider" is too long, truncating to "Name Registration Response Received Successfully by Service Prov"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Service Pr"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Service Provid"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Service Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Service Provide"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Authentication Request Received By Identity Provider(%)" is too long, truncating to "Successful Authentication Request Received By Identity Provider("
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Identity P"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Identity Provi"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Identity Provid"
    2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Sent By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Sent By Identity Provider(%"
    2008-06-26 14:32:50 Thread-3086935744 INFO TargetManager: save to targets.xml success
    2008-06-26 14:32:50 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds or earlier.
    2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:15 Thread-28801952 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2008-06-26 14:33:15 Thread-28801952 ERROR upload: Error in uploadXMLFiles. Trying again in 72.00 seconds or earlier.
    2008-06-26 14:33:34 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:34 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:35 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:35 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:35 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:35 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:35 Thread-28801952 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2008-06-26 14:33:35 Thread-28801952 ERROR upload: Error in uploadXMLFiles. Trying again in 86.00 seconds or earlier.
    2008-06-26 14:33:50 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:50 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:50 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:50 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:51 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:51 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:51 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2008-06-26 14:33:51 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 103.00 seconds or earlier.
    2008-06-26 14:33:52 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:52 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:53 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:53 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:53 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:33:53 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:33:53 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2008-06-26 14:33:53 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 123.00 seconds or earlier.
    2008-06-26 14:35:57 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:35:57 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:35:57 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:35:57 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:35:58 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
    ERROR-100|No space left on device
    2008-06-26 14:35:58 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2008-06-26 14:35:58 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2008-06-26 14:35:58 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 147.00 seconds or earlier.
    oracle : dg01 : @test : /u01/app/oracle/product/10.2/agent/agent10g/sysman/log
    $

  • OMS, Repository, Agent Grid upgrade

    Newbie here and will try to explain as best as I can.
    So I installed Grid 10.2.0.2 on Windows XP system. I have used the patchset 12.0.4.0 to upgrade OMS, repository and agent. I have followed the documentation on how to do this. First I patched OMS by setting the environment variable to C:\OracleHomes\OMS10g and then clicked on setup oui installed the patch. I did the same for the Agent and change the env var to the agent home and patched the agent. According to the documentation the OMS and repository are upgraded together. So after both homes were upgraded, I open a command prompt to see the status of the oms agent and the management agent using "emctl status agent" and I see the following information.
    OMS
    Agent Version : 10.1.0.5.0
    OMS Version : Unknown
    Agent
    Agent Version : 10.2.0.4.0
    OMS Version : 10.2.0.4.0
    I have also updated the database to 10.2.0.1 (orginally 10.1.0.5) and then patched to 10.2.0.4 and it show this when I connect to SQLPlus, so that seemed to work.
    So why is the OMS agent showing up as 10.1.0.5 even though I assumed it was patched. Is this normal or did something fail during upgrade.
    Thanks

    OK, I guess that makes sense.
    Yes, I installed 10.2.0.1 into a separate home and used DBUA to upgrade the repository DB from 10.1.0.5 to 10.2.0.1. I then patched it to 10.2.0.4 and again used DBUA and so I am assuming my repository would be at 10.2.0.4 and that's why I was asking why the command prompt see it as 10.1.0.5.
    The home directories I have is
    C:\OracleHomes\agent10g, oms10g, db10g, oradata- This is for grid
    C:\Oracle\10.2.0\db_1- is the 10.2.0.4 database.
    The other reason I am asking about this is that I am using the agentdownload.vbs to install the management agent on a few systems. Before the upgrade I was able to successful install it using the 10.2.0.1 and when I upgraded to 12.0.4.0, I noticed I now had three folders 10.2.0.1, 10.2.0.2 and 10.2.0.4 that the agentdownload.vbs reside in. Since I am at 10.2.0.4 I chose to use that vbs file. I tried it on one of systems, but it doesn't seem to work and is asking about securing the agent. I made the necessary changes with the env variable, but it seems to never makes a connection my management server. I then tried to use the 10.2.0.2 vbs file and it works just fine. So I am thinking during my all of trials of getting grid and DB upgraded to 10.2.0.4 that something is amiss. So that's why I am question the versioning on the command prompt.
    Thanks

  • OMS and Agent Communication Problem?

    Hi
    All
    I have installed OMS that have version 10.2.0.2 on windows server and Agent with version 10.1.0.4 on AIX.
    Is it any problem with version of OMS and Agent?
    Thanks,
    Vishal

    Sorry To ask question again. but I have read 412431.1 doc and it satisfy requirement. After reading that I proceed with installation but somehow I m getting this output
    $ emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.2.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.4.1
    OMS Version : Unknown
    Protocol Version : 10.1.0.2.0
    Agent Home : /u07/app/oracle/product/10.2.0/moe.wsi_OWSIDEV
    Agent binaries : /u07/app/oracle/product/10.2.0
    Agent Process ID : 290972
    Parent Process ID : 458882
    Agent URL : http://moe.wsi.:3938/emd/main
    Started at : 2007-10-10 14:58:20
    Started by user : oracle
    Last Reload : 2007-10-10 14:58:20
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 2459
    Size of XML files pending upload(MB) : 24.56
    Available disk space on upload filesystem : 36.92%
    Agent is Running and Ready
    and Here it's says OMS version is unknown So I dont' know what's going on here.
    Thanks,
    Vishal

  • Issues after upgrading to 10.2.0.4  ( both OMS and Agent)

    All,
    we are observing this error quite a lot after upgrading to 10.2.0.4 ( both oms and agent)
    2008-07-31 15:08:19,088 Thread-228 ERROR : (nmevrr.c,328):Memory 0x0 encountered, expect struct_id=12201
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:snmeuctx_setGenCtx+0x912
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nme_class_error+0x184
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrr_Recvlet_refreshState+0x264
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrg_RegisteredRecvlet_refreshState+0x228
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrm_RecvletManager_init+0x5544
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x1792
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x376
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmemdisp_GetMetric+0x10212
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmemdisp_GetMetric+0x15664
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmehl_disabled_remote_ops+0x2600
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x448
    /u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x596
    /lib/libc.so.1:_thr_slot_offset+0x1132
    we have these patches 7012242,7031906,5961654,5632264 installed on the agent home.
    I have also disabled the instance health metrics for all the 10g target db on this host.
    Anybody has any idea how to resolve this . This is becoming quite annoying .
    thanks in advance
    pk

    Hi,
    Just to comfort you, and yes we do monitor 10.2.0.3 instances. This comes from the emagent.trc on one of many rdbms server. The same is not found on other servers running 10.2.0.3 instances. The time coincide with an agent crash on this server. Keeping an eye on this thread while trying to find out what it is related to.
    EDIT: This is due to bug 7012242, see metalink docId: 579137.1
    2008-08-15 05:30:03,081 Thread-689845 ERROR : (nmevrr.c,328):Memory 0x0 encountered, expect struct_id=12201
    /oracle/product/agent10g/lib32/libnmemso.so:snmeuctx_setGenCtx+0x912
    /oracle/product/agent10g/lib32/libnmemso.so:nme_class_error+0x184
    /oracle/product/agent10g/lib32/libnmemso.so:nmevrr_Recvlet_refreshState+0x264
    /oracle/product/agent10g/lib32/libnmemso.so:nmevrg_RegisteredRecvlet_refreshState+0x228
    /oracle/product/agent10g/lib32/libnmemso.so:nmevrm_RecvletManager_init+0x5544
    /oracle/product/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x1792
    /oracle/product/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x376
    /oracle/product/agent10g/lib32/libnmemso.so:nmebb_uploadTargetState+0x928
    /oracle/product/agent10g/lib32/libnmemso.so:nmebb_updateBlackoutInfo+0x384
    /oracle/product/agent10g/lib32/libnmemso.so:nmesse_executeWork+0x132
    /oracle/product/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x448
    /oracle/product/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x596
    /lib/libc.so.1:_thr_slot_offset+0x1128
    Message was edited by:
    ivirnig

  • Agent version 10.1.0.6.0 DB Control version 10.2.0.4 - Is this ok?

    Hi,
    dbconsole is failing to startup. We have already tried rebuilding the repository and still it won't start.
    The agent does come up. One thing to point out is that the agent version that is reported by emctl status agent is 10.1.0.6.0
    with a protocol version of 10.1.0.2.0
    while dbcontrol(and the database are on version 10.2.0.4). Can the 10.1.0.6 agent work with 10.2.0.4? This setup
    did work before but I think the repository rebuild may have caused some problems. The db was installed as 10.1.0.6
    and then upgraded to 10.2.0.4 so the original repository build was likely on a consistent version.
    Thanks

    I see lots of connection refused messages in the emagent.trc file
    Messages are of the form:
    WARN snmehl_connect: connect failed to....
    ERROR pingManager: nmepm_pingReposURL: Cannot connect to...
    This isn't to surprising since dbconsole is not running.

  • Agent Versions Incorrect?

    Good Afternoon,
    I have recently been given control of our SCOM infrastructure as the person before me has left and I've been given the reigns. We are currently running SCOM 2012 Service Pack 1 and have Cumulative Update 8 installed which is the latest CU available from
    Microsoft.
    I have been doing a bit of housekeeping today and noticed that the agent version that is installed on all of our clients is version 7.0.9538.0 which is the version that came pre-installed with 2012 SP1 when it was first released.
    The only server that does seem be on the latest build number is the Management Server which CU8 was installed on to manually. The build number is now 7.0.9538.1123.
    I know for a fact that our previous owner of SCOM installed every CU that has been released and I also remember that he went through the process of updating the clients on all our servers (almost 400).
    I have gone through the process of uninstalling some of the agents and reinstalling but I am unable to update it. We do also have a few servers that are running version 6.1.7221.49. This version is from May 2009 and was part of the SCOM 2007.
    I've noticed that if I log on to one of the servers that an agent is installed on after we ran the update for CU8 I can see that the file versions of the dll files do have the correct build number for CU8 (7.0.9538.1123)
    So from what I see it looks as though this is potentially a bug with SCOM. I'm not sure. How can I update the agent versions within the SCOM console to reflect the correct agent version.
    As you can see in the screenshot1 above the version for the servers with an agent here are still on 7.0.9538.
    In screenshot2 this is from one of the servers with an agent installed in the path of 'C:\Program Files\System Center Operations Manager\Agent'. As you can see the latest version is there but you can also see older versions too.
    Finally if I log on to the SCOM management server and open operations manager shell and run the command get-scomagent it gives me the same incorrect version. 
    I hope someone can help me with this.
    Regards,

    Yes, it´s normal and as expected. The version number 7.0.9538 reflects System Center 2012 SP1 Operations
    Manager and doesn´t change when applying a Update Rollup. If you were to upgrade to R2 then the version would be 7.1.10226.0 instead. 
    If there were older agents from a SCOM 2007 etc, the version number would match the SCOM version.
    Regards,
    Daniel
    IT Consultant at Viridis IT

  • DPM 2012 R2 UR2 and Windows 2003 SP2 Agent Version Issue

    Hi All, I have UR2 installed on my DPM 2012 R2 server and have followed Mike's guide on getting them protected:
    http://blogs.technet.com/b/dpm/archive/2014/06/11/details-on-protecting-windows-server-2003-computers-using-data-protection-manager-2012-r2.aspx
    The agents now show in the DPM console but display as needing an update and showing as agent version 4.1.3313.0 instead of 4.1.3441.0, which is odd.
    Servers have:
    .Net 3.5 Sp1 Full
    Visual C++ 2008 Redistributable - x86 9.0.30729.17
    From the DPM server:
    C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\agents\RA\4.2.1235.0\i386\1033\DPMAgentInstaller_Win2K3_i386.exe
    Executed:
    setdpmserver.exe -dpmservername DPMserverName
    From the DPM server:
    Attach-ProductionServer.ps1 script on the DPM server and refreshed twice
    What have I missed?

    Hi.
    Reboot your 2003 Server
    Run DPM Setup again on Server 2003
    Run setdpmserver.exe again
    click refresh in DPM Server
    worked for me
    Seidl Michael | http://www.techguy.at |
    twitter.com/techguyat | facebook.com/techguyat

  • How to find installed SMD Agent version?

    Hi,
    Please let me know how to find the installed SMD agent version in managed system.
    Thanks,
    Kavitha Rajan.

    Hello,
    Something really easy to differentiate the agents installed:
    -     7.01-> /usr/sap/SMD/JXX
    -     7.11 or 7.20 -> /usr/sap/DAA/SMDAXX
    Regards,
    Allam

  • Agent version differs from LMService

    Hi ,
    I am connecting a NW 7.31 Java system with solman 7.1 SP10 with SMD diagnostic agent for Manage system config set up
    I have installed the SMD agent and connected with central SLD & solman.
    In the agent connectivity it can be seen that the diagnostic agent is in pending status with the message " 7.10.1.0.2011070611153 Agent version differs from LMService"
    what could be the reason and what is LMService here.
    The system kernel version is 720_EXT.
    Please guide and provide a solution
    Thanks in advance

    Hi Daniel,
    Can you check LM-Service SP and Patch level.
    Also Refer the guided process as per these 2 KBAs.
    1962333 - Responsibility of individual steps in transaction SOLMAN_SETUP
    1931100 - "Agent version differs from LMService" Error in Solution Manager 7.1 Agent Administration
    Divyanshu

  • IS Diagnostics Agent Version 7.01 SR1 available?

    Hi,
    We have solution manager version Versions 7.0 EHP1 < SP20 so Diagnostics Agent Version 7.01 SR1 complies with the version of the Solution Manager system.
    But I can not find dowload available on market pla

    Looks like it is required. My version is 1.6

  • Search for all deployed agents version

    Hi,
    I want to list all (recent) deployed zcm agents to find out which computers need to be updated manually to the latest version. The reporting:
    Type Software Applications, focusing on General Software
    Columns Product Manufacturer
    Product Name
    Product Version
    Instances (Summary)
    Product
    Machine Name
    Criteria Device Is Retired = No and
    Product Is Deleted = No and
    Product <= Novell ZENworks Adaptive Agent 11.3.2.47407 and
    Product >= Novell ZENworks Adaptive Agent 11
    ==> doesn't show correct results as some devices are reported as old version but in fact the latest agents version has been installed. What option are useful to find the installed agents versions?
    All the best, Ralf

    Is your Zone Setup to Auto-Rename Devices when the machine name changes?
    I wonder if the issue is that the "Machine Name" may not match "ZCM Device Object Name"
    You may even have Dupe "Machine Names" so that while you think it is updated, it is not because it is actually a different machine than you expected.

  • Report Agent version

    Hi all,
    is it possible that I can get a report about the ZCM Agent version from my clients? I want to know how many clients are online with the old (10.1.0) version....
    GerritRoss

    Originally Posted by gerritross
    Hi all,
    is it possible that I can get a report about the ZCM Agent version from my clients? I want to know how many clients are online with the old (10.1.0) version....
    GerritRoss
    For all how have the same question: You can create dynamic groups in the workstation section. There you can choose Workstation Agentversion. So it is easy to get these information!
    Greets

  • 11g: New agent versions at download-area

    Hello,
    how can i put new agent versions at our download area on grid control server?
    Acutally we have a grid control server verison 11.1.0.1.0 and all agent versions for deployment are 11.1.0.1.0 or older. But i want to install agent version 11.1.0.7.0. What i have to do therefore?
    Regards,
    Heike

    The staging area in <OMS_HOME>/sysman/agent_download/<version> is only for staging base versions of the agent.
    If you want to deploy an agent with patches (e.g. agent version 11.1.0.1.0 with PSU 5 applied), you can apply the desired patches to an existing agent and then clone it. For more information on cloning an agent, please see:
    http://docs.oracle.com/cd/E11857_01/install.111/e16847/clone_agent_usng_zip.htm#BABHBJJA
    By the way, agent version 11.1.0.7.0 is not available.
    Regards,
    - Loc

Maybe you are looking for

  • At a complete loss.....problems downloading Java

    I had Java on my laptop for ages and never had any problems until recently where it just wouldn't let me use it, kept getting an error message saying there were components missing...or something like that. Completely removed it from my laptop (well I

  • Technical System not appearing while creating Business System

    Hi We had already created business system and assigned a technical system and all the interfaces was working fine. Now we removed the technical system and created a new technical system, since we need to point to different server. I created a new tec

  • AppleTV (Gen3) won't display any wireless networks...

    I've seen several other users with similar issues, and I'm wondering what is being done. I got my Apple TV in May in the US, but now live in China. It was working fine until two days ago when, in the middle of streaming a movie, it disconnected from

  • How do i do to get the facebook notifications on the main screen?

    I own the alcatel fire and The facebook notification doesnt appear in the main screen i wanna know if that is possible thanks for your help

  • Error initializing end point

    Hi to everybody, I just installed tomcat 4.1 and j2se1.4.2 and everithing seems to work perfectly but rebooting the system and triing to run tomcat it returns this error: "error initializing enpoint java.net.BindException:Address already in use: JVM_