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
$

Similar Messages

  • Agent unreachable

    Hi,
    I have installed agent 10g on unix machine(HPUX-11.1) agent runs for 6-8 hrs
    after that it dies out and when i see the db through grid control it says agent unreachable but when grep for agent it shows up and running , iam not sure whats happening here.
    [oracle:leopard:NOSID] /oracle/product/agent10g/sysman/log > ps -ef|grep agen>
    root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
    root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
    oracle 23822 23690 0 Nov 20 ? 13:24 /oracle/product/agent10g/bin/emagent
    oracle 23690 1 0 Nov 20 ? 2:54 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
    aduaslq 16850 22944 0 Nov 23 ? 4:58 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent---->agent is for OAM
    [oracle:leopard:NOSID] /oracle/product/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 is Not Running
    [oracle:leopard:NOSID] /oracle/product/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 ....... failed.
    Failed to start HTTP listener.
    Consult the log files in: /oracle/product/agent10g/sysman/log
    [oracle:leopard:NOSID] /oracle/product/agent10g/bin > ps -ef|grep agent
    root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
    root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
    oracle 23822 23690 0 Nov 20 ? 13:23 /oracle/product/agent10g/bin/emagent
    oracle 3913 15344 0 21:42:27 pts/7 0:00 grep agent
    oracle 23690 1 0 Nov 20 ? 2:53 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
    aduaslq 16850 22944 0 Nov 23 ? 4:57 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent
    /oracle/product/agent10g/sysman/log :vi emagent.trc
    2007-11-27 17:48:44 Thread-189993 ERROR util.files: ERROR: nmeufos_new: failed i
    n lfiopn on file: /oracle/product/agent10g/sysman/emd/agntstmp.txt.error = 24 (T
    oo many open files)
    2007-11-27 17:48:44 Thread-189993 ERROR pingManager: Error in updating the agent
    time stamp file
    2007-11-27 17:48:48 Thread-189994 ERROR util.fileops: ERROR: snmeuf_dirlist can'
    t list directory: /oracle/product/agent10g/sysman/emd/upload: Too many open file
    s (errno=24)
    2007-11-27 17:48:51 Thread-189995 ERROR engine: Failed when generating a new ECI
    D.
    2007-11-27 17:48:51 Thread-189995 ERROR fetchlets.healthCheck: GIM-00104: file n
    ot found
    LEM-00031: file not found; arguments: [lempgmh] [lmserr]
    LEM-00033: file not found; arguments: [lempgfm] [Couldn't open message file]
    LEM-00031: file not found; arguments: [lempgmh] [lmserr]
    2007-11-27 17:48:51 Thread-189995 ERROR engine: [oracle_database,leopard-amuaslq
    .am,health_check] : nmeegd_GetMetricData failed : Instance Health Check initiali
    zation failed due to one of the following causes: the owner of the EM agent proc
    ess is not same as the owner of the Oracle instance processes; the owner of the
    EM agent process is not part of the dba group; or the database version is not 10
    g (10.1.0.2) and above.
    Please Any suggestions.

    As per note_id:430805.1
    3. We now need to focus also on the monitored database side. This section takes place in the monitored RDBMS Oracle Home:
    If the monitored database is 10gR1 (10.1.x):
    10.1.0.4: you need to apply Patch 5868695 on the RDBMS Oracle Home, otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
    10.1.0.5: At this moment, this specific one-off patch is not available on top of RDBMS 10.1.0.5. Please contact support if you need this fix for RDBMS 10.1.0.5 on HP-UX.
    10.1.0.3, 10.1.0.2: consider patching / upgrading
    If the monitored database is 10gR2 (10.2.x):
    10.2.0.3 (and above): nothing to be done. The fix is already included.
    10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
    My concern is what if we have 8i and 9i monitored databases?Please let me know.

  • CloudControl 12c shows "Agent Unreachable" for Cluster Database

    Hello ,
    when clicking on "Targets -> Databases" our RAC database shows up as follows:
    Name Type Status
    PROD02 Cluster Database symbol for "Agent Unreachable"
    PROD021 Database Instance symbol "green arrow" for "Up"
    PROD022 Database Instance symbol "green arrow" for "Up"
    I don't understand why the symbol for the Cluster Database is not a green arrow, too. The agent on each node is up and running - and when either clicking on "PROD02" or "PROD021" (or PROD022) Cloud Control offers the full functionality. Therefore the status "Agent Unreachable" is missleading (from my point of view). I don't want to remove the complete Cluster Database and discover it once again - several jobs have already been defined and I don't want to do that once again.
    Did anybody else experience the same behaviour?
    Any help will get appreciated...
    Rgds
    JH

    ... seems like if I'm hitting bug "BUG 13865299".
    => "12c Cluster database or Cluster ASM in Pending or "Agent unreachable" for undetermined time [ID 1463196.1]"

  • OEM 10g - Job Status - Suspended on Agent Unreachable

    Hi,
    I have checked out a few post on this forum which is similar to my problem.
    But could not get the exact workaround.
    The scheduled backup is not getting failed / successful since 29th January 2010.
    We have not made any changes on the database level. But there was a patching activity at application level.
    and as soon as I try to schedule a backup it shows the same status "suspended on agent unreachable"
    I have checked the emctl status and dbconsole status.
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.6.0
    OMS Version : 10.1.0.6.0
    Protocol Version : 10.1.0.2.0
    Agent Home : e:\oracle\product\10.2.0\db_1\content.mydomain.de_aeb
    Agent binaries : e:\oracle\product\10.2.0\db_1
    Agent Process ID : 6104
    Agent URL : http://content.mydomain.de:3938/emd/main
    Started at : 2010-02-01 21:55:19
    Started by user : SYSTEM
    Last Reload : 2010-02-01 21:55:19
    Last successful upload : 2010-02-17 06:12:10
    Last attempted upload : 2010-02-17 06:12:25
    Total Megabytes of XML files uploaded so far : 323.40
    Number of XML files pending upload : 1
    Size of XML files pending upload(MB) : 0.01
    Available disk space on upload filesystem : 9.36%
    Agent is Running and Ready
    E:\oracle\product\10.2.0\db_1\BIN>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    http://content.mydomain.de:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory e:\oracle\product\10.2.0\db_1/scontent.mydomain.de_AEB/sysman/log
    Upload also seems to be working fine.
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    What should I do ? Will restarting the agent help ? Will restarting the agent have any adverse effect on DB ?
    Any help would be a great help.
    Rushabh

    Hi,
    This is urgent.. Please help..
    I am not able to start the emctl...
    Below is the error that I am getting..
    E:\oracle\product\10.2.0\db_1\BIN>emctl stop agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    This will stop the Oracle Enterprise Manager 10g Database Control process. Conti
    nue [y/n] :y
    The OracleDBConsoleaeb service is stopping..........
    The OracleDBConsoleaeb service was stopped successfully.
    E:\oracle\product\10.2.0\db_1\BIN>emctl clearstate agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD clearstate completed successfully
    E:\oracle\product\10.2.0\db_1\BIN>emctl secure agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Enter Agent Registration password :
    Agent is already stopped... Done.
    Securing agent... Started.
    Requesting an HTTPS Upload URL from the OMS... Failed.
    The OMS is not set up for Enterprise Manager Security.
    E:\oracle\product\10.2.0\db_1\BIN>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    When I try to secure agent it is asking for a password, but it is already saved I think..
    When I press enter it is showing the above error.
    What should I do now ?
    Regards,
    Rushabh
    Edited by: user650383 on Feb 16, 2010 10:44 PM

  • Oracle Management Console 10g - Job Status - Suspended on Agent Unreachable

    Recently we updated our RDMS from 10.2.0.1 to 10.2.0.4.0 PATCH 25.
    Ever since we upgraded, we have had trouble with our RMAN backups. Now when a scheduled backup begins it never ends. Now whenever we schedule a job, from a backup to any simple system command, the status immediately returns "Suspended on Agent Unreachable".
    We can start and stop the dbconsole successfully, and I can use the OEM to monitor the database, and make changes to that. However, I cannot run any scheduled database jobs through the OEM. However, I can run the rman jobs via the command line.
    The database server, and the OEM console is on the save server. I am not running RAC. Everything database related is on this one server.
    Here are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    Agent Version     : 10.1.0.6.0
    OMS Version       : 10.1.0.6.0
    Protocol Version  : 10.1.0.2.0
    Agent Home        : E:\oracle\product\10.2.0\db_1\content.mydomain.com_ORCL
    Agent binaries    : E:\oracle\product\10.2.0\db_1
    Agent Process ID  : 34372
    Agent URL         : http://content.mydomain.com:3938/emd/main
    Started at        : 2010-01-11 14:58:24
    Started by user   : SYSTEM
    Last Reload       : 2010-01-11 14:58:24
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far :     0.00
    Number of XML files pending upload           :     5016
    Size of XML files pending upload(MB)         :    42.77
    Available disk space on upload filesystem    :    37.94%
    Agent is Running and ReadyHere are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..I think the EMD upload error may be the problem, but I'm unsure how to resolve this.
    What do I need to do in order to resolve this issue?
    If any more info would be useful, please let me know and I will post it immediately.
    thanks.

    Rondeyli,
    Thanks, that was it. I followed your instructions, and was able to get the system to work. I had to alter the commands a bit to get them to work on my system, so here is what I did.
    I performed the following steps:
    1. Ran the following command:
            emctl stop dbconsole
    2. deleted all files in $AGENT_HOME/sysman/emd/upload and $AGENT_HOME/sysman/emd/state
    3. Ran the following command:
           emctl clearstate dbconsole
    4. Ran the following command:
           emctl secure dbconsole
    5. Ran the following command:
           emctl start dbconsoleThis got everything running for me.
    thanks.

  • Agent unreachable problem

    One of the monitored SuSE Linux host in my Grid OEM has status "Agent unreachable". As such the host has not been monitored. It was ok before and I am not sure why (and from when) it has the problem. I have checked and the dbsnmp agent on the Linux host is up and running. I have restarted the agent but it does not help.
    Below is the output from "emctl status agent" command issued on the Linux host.
    What do I need to check and try?
    Many thanks.
    Checking Agent status, please wait...
    The Oracle base for ORACLE_HOME=/opt/app/oracle/product/agent/agent11g is /opt/app/oracle
    Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
    Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
    Agent Version : 11.1.0.1.0
    OMS Version : 10.2.0.5.0
    Protocol Version : 10.2.0.5.0
    Agent Home : /opt/app/oracle/product/agent/agent11g
    Agent binaries : /opt/app/oracle/product/agent/agent11g
    Agent Process ID : 4684
    Parent Process ID : 4572
    Agent URL : https://romulus.it.csiro.au:3872/emd/main/
    Repository URL : https://oraserv.it.csiro.au:1159/em/upload
    Started at : 2011-01-26 20:22:05
    Started by user : oracle
    Last Reload : 2011-01-26 20:22:05
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 2
    Size of XML files pending upload(MB) : 0.29
    Available disk space on upload filesystem : 1.97%
    Last successful heartbeat to OMS : 2011-01-26 20:22:25
    Agent is Running and Ready

    I issued the "emctl upload agent" command and got some error message about not enough space. I noticed that the /opt/app file was 99% full (it still had few GB free), and I did some clean up and got it down to 93% full (120 GB free now). I then issued "emctl upload agent" again and it gev the output
    Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
    Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    I then checked my Grid Control OEM and the agent unreachable problem is no longer there. :-)
    I will check the log files under sysman/log to investigate the original problem further.
    Many thanks for your help.
    Cheers.

  • Rman backup job Suspended on Agent Unreachable

    Hi,
    I have Oracle 10.2.0 installed on windows 2003 server. i configure oracle suggested rman backup which works fine till now. but now it shows
    Suspended on Agent Unreachable message and backup doesn't happen.
    if check like
    C:\Documents and Settings\Administrator>emctl status agen
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    Agent is Not Running
    C:\Documents and Settings\Administrator>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    These Windows services are started:
       Application Experience Lookup Service
       Application Management
       Automatic Updates
       COM+ Event System
       COM+ System Application
       Computer Browser
       Cryptographic Services
       DCOM Server Process Launcher
       DefWatch
       Distributed File System
       Distributed Transaction Coordinator
       DNS Client
       DNS Server
       Error Reporting Service
       Event Log
       File Replication Service
       FTP Publishing Service
       HTTP SSL
       IIS Admin Service
       Indexing Service
       Intel PDS
       Intersite Messaging
       IPSEC Services
       Kerberos Key Distribution Center
       Logical Disk Manager
       LogMeIn
       LogMeIn Maintenance Service
       Net Logon
       Network Connections
       Network Location Awareness (NLA)
       NT LM Security Support Provider
       OracleDBConsoleneo
       OracleOraDb10g_home1iSQL*Plus
       OracleOraDb10g_home1TNSListener
       OracleServiceNEO
       Plug and Play
       Print Spooler
       Protected Storage
       Remote Access Connection Manager
       Remote Procedure Call (RPC)
       Remote Registry
       Secondary Logon
       Security Accounts Manager
       Server
       Shell Hardware Detection
       SQL Server (MSSQLSERVER)
       SQL Server Agent (MSSQLSERVER)
       SQL Server Analysis Services (MSSQLSERVER)
       SQL Server FullText Search (MSSQLSERVER)
       SQL Server Integration Services
       SQL Server Reporting Services (MSSQLSERVER)
       Symantec AntiVirus Server
       System Event Notification
       Task Scheduler
       TCP/IP NetBIOS Helper
       Telephony
       Terminal Services
       Windows Management Instrumentation
       Windows Search
       Windows Time
       Workstation
       World Wide Web Publishing Service
    The command completed successfully.means my agent was stop but now i start it.
    i find on Google that this type of error happen when you change in database like ip address, sid etc but i haven't do any change.
    i am facing same problem so many times.
    Now how to reschedule the existing backup job so that it starts work again.
    thanks
    umesh

    thanks for reply
    i do it.
    C:\Documents and Settings\Administrator>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    EM Daemon is not running.
    Logs are generated in directory C:\oracle\product\10.2.0\db_1/Techwave_neo/sysman/log
    C:\Documents and Settings\Administrator>emctl stop dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    The OracleDBConsoleneo service is stopping.....
    The OracleDBConsoleneo service was stopped successfully.
    C:\Documents and Settings\Administrator>emctl start dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleneo service is starting................
    The OracleDBConsoleneo service was started successfully.now it is working fine.
    now issue is how i reschedule my suspended job.
    i got this error.
    Edit is not supported for this job type, only general information about the job can be updated No scheduled executions - this job can not be modified.

  • Corrective Action on Agent Unreachable?

    Let me first explain exactly what I am looking to do. My current setup is a repeating job that recreates connections (tunnels) to the agent boxes every 15 minutes to ensure that connections stay up. This can get hung up and drag the network down. Ideally, I would like to setup an automated system to correct the issues. If an Agent becomes unreachable, I want to initiate a corrective action that will try to recreate the connection. I was told that the corrective action would be run ON THE AGENT, which would inevitably fail if there was no connection. So a 2nd task would be added to the corrective action in response to the first failed task, that would run the connection scripts on the OEM box and re-establish connection. If that fails as well, then I would like a notification to be sent out (incident rules typically).
    That is my ideal set up. Here are the issues I am running into. The first is that the Agent Unreachable does not seem to be an editable metric. It is listed as a metric called Response > Status, under All Metrics. However, under Metric settings, it can not be edited, and thus, I do not see a way to tie a corrective action to this metric. Once I do tie the corrective action to this metric, do I need to set up a job to run in the corrective action or is the corrective action basically a job that runs in response to an event? That is how I understood it...just looking for verification. It would be greatly appreciated if I could be pointed in the correct direction.

    I'm not sure you can do this through a metric alert corrective action, but it sounds like a great enhancement request. You didn't mention the EM version that you're using, but if you're on EM12c you can implement something like this through an advanced notification method. There's more than one way to do it but here's what I just tested and confirmed will work:
    1) Generate an ssh key for the oracle user running the OMS, and save the key with no password
    2) Copy the generated public key to $HOME/.ssh/authorized_keys for the user running the agent on the host where you would like to restart the agent
    3) Create a shell script owned by the OMS oracle user that contains the line "ssh [email protected] /pathtoagent/bin/emctl start agent"
    4) Log in to EM12c as user SYSMAN and create an advanced notification method that calls the shell script created in step 3
    5) Create an incident ruleset applying to the agent target
    6) Create an rule in the ruleset that applies to incoming incidents where Category = Availability and Severity = Critical
    7) Create an action for that rule that calls the advanced notification method from step 4
    Then stop the agent to test it. Once the incident is generated, the notification method will run, ssh from the OMS host to the agent host, and start up the agent again.
    It doesn't look like you can pass parameters to the notification methods, so you may need to create a separate notification method and separate shell script for every agent you monitor.
    You could probably also do this through an SNMP trap advanced notification if you have other management software on your network that could catch the trap and respond to it appropriately.
    But for me the real question would be: why are your agents going unreachable so often that you need to bother with this?

  • 12c Cloud Control - Agent Unreachable

    Hello,
    I am quite new to 12c cloud control and I am unable to resolve an "Agent Unreachable" issue.
    I could find Agent does not upload to OMS in OEM 12c as relevant
    but nothing in that worked for me.
    The setup is as follows:
    1) 12c cloud control is installed on a box and is up and running (both OMS and agent)
    2) The agent on the same host as OMS can talk to OMS and the agent status is shown as "available" in OMS console
    3) There is another box that has a 11.2 database installed as well as 12c agent installed (called as DEVBOX for convenience)
    4) DEVBOX has database up and running and 12c agent also up and running. In the past, it was probably being able to "talk" to OMS but I can't remember
    However, at present, on OMS console, this agent is shown as "unreachable". I tried few things but only possible issue I could find is
    when I try to use Setup -> Add Target -> Add Targets Manually -> Add non-Host targets using guided process, on the "specify Host" page
    when I click on "Select Host" option, the hostname in the agent URL for the DEVBOX is different than the actual host name.
    As the agent URL for DEVBOX is not reachable (because the hostname is invalid), I can't do anything with this agent.
    Can somebody please help?

    Loc Nhan wrote:
    To remove an agent from the console:
    - Go to the homepage of the host where the agent reside
    - From the Host menu under the host name, select Related Targets
    - Remove all non-agent targets
    - Remove the host target by selecting Host > Target Setup > Remove Target
    - Stop the agent
    - Remove the agent target by going to the agent homepage and selecting Agent > Target Setup > Remove TargetLoc,
    Once again thanks for looking into this. I followed your advice above and removed the host and the agent from OMS console.
    Now, with the 12c agent already running on the DEVBOX, I was hoping that OMS will automatically detect the agent but I
    can't find it in OMS console.
    On DEVBOX:
    [oracle@devbox agent_inst]$ ./bin/emctl status agent
    Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.
    Agent Version     : 12.1.0.1.0
    OMS Version       : 12.1.0.1.0
    Protocol Version  : 12.1.0.1.0
    Agent Home        : /u01/app11g/oracle/agentHome12c/agent_inst
    Agent Binaries    : /u01/app11g/oracle/agentHome12c/core/12.1.0.1.0
    Agent Process ID  : 8945
    Parent Process ID : 8893
    Agent URL         : https://devbox.dev.abc.com:3872/emd/main/
    Repository URL    : https://gridbox.prd.abc.com:4901/empbs/upload
    Started at        : 2012-08-17 09:47:30
    Started by user   : oracle
    Last Reload       : (none)
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far : 0
    Number of XML files pending upload           : 0
    Size of XML files pending upload(MB)         : 0
    Available disk space on upload filesystem    : 17.52%
    Collection Status                            : Collections enabled
    Last attempted heartbeat to OMS              : 2012-08-17 09:48:51
    Last successful heartbeat to OMS             : 2012-08-17 09:48:51
    Agent is Running and Readyon OMS box:
    [oracle@gridbox middleware]$ ./oms/bin/emctl status oms -details
    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.
    Enter Enterprise Manager Root (SYSMAN) Password :
    Console Server Host : gridbox.prd.abc.com
    HTTP Console Port   : 7789
    HTTPS Console Port  : 7801
    HTTP Upload Port    : 4890
    HTTPS Upload Port   : 4901
    OMS is not configured with SLB or virtual hostname
    Agent Upload is locked.
    OMS Console is locked.
    Active CA ID: 1
    Console URL: https://gridbox.prd.abc.com:7801/em
    Upload URL: https://gridbox.prd.abc.com:4901/empbs/upload
    WLS Domain Information
    Domain Name      : GCDomain
    Admin Server Host: gridbox.prd.abc.com
    Managed Server Information
    Managed Server Instance Name: EMGC_OMS1
    Managed Server Instance Host: gridbox.prd.abc.comAs I mentioned earlier, gridbox and devbox can communicate with each other on necessary ports.
    I would prefer to resolve this issue without having to re-install the agent.
    Would appreciate some help.
    Thanks.

  • EM 10g Database Control - Status: Agent Unreachable

    Hi,
    OS: AIX 5L
    Database: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bit
    We have installed 2 instances with EM 10g database control option.
    At the end EM was running over the second database.
    Then we switch it to look over the first one by reconfiguring these files:
    $ORACLE_HOME/sysman/config/emd.properties;
    $ORACLE_HOME/sysman/config/pref/dbastudio-oradba.crd.
    Now EM seems to work fine except for this error: Agent Unreachable.
    oradba@aix09(:SIGP)/u01/apps/oradba/product/10.1.0/aix09_SIGP/sysman/log > emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.1.0.2.0
    Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.2.0
    OMS Version : 10.1.0.2.0
    Protocol Version : 10.1.0.2.0
    Agent Home : /u01/apps/oradba/product/10.1.0/aix09_SIGP
    Agent binaries : /u01/apps/oradba/product/10.1.0
    Agent Process ID : 4284428
    Parent Process ID : 3399760
    Agent URL : http://aix09:1830/emd/main
    Started at : 2004-08-09 12:24:29
    Started by user : oradba
    Last Reload : 2004-08-09 12:24:29
    Last successful upload : (none)
    Last attempted upload : 2004-08-09 14:29:51
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 1955
    Size of XML files pending upload(MB) : 50.12
    Available disk space on upload filesystem : 4.60%
    Agent is Running and Ready
    /aix09_SIGP/sysman/log/ emagent.trc:
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2004-08-09 14:31:53 Thread-1910 WARN upload: FxferSend: received http error in header from repository: http:/
    /aix09:5500/em/upload/
    ERROR-400|ORA-04020: deadlock detected while trying to lock object 30x700000021709BF80x700000021B01D200x700000
    0267473A8
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2004-08-09 14:31:53 Thread-1910 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Error in uploadXMLFiles. Trying again in 300.00 seconds.
    After connecting as sysman I’ve ran these statements:
    SQL> SELECT emd_url
    2 FROM mgmt_targets t
    3 WHERE t.target_name = 'aix09'
    4 AND t.target_type = 'host';
    EMD_URL
    http://aix09:1830/emd/main
    SQL> SELECT t.target_name, t.target_type,
    2 TO_CHAR(t.load_timestamp,'DD-MON-YYYY HH24:MI:SS') "discovery_time
    3 TO_CHAR(t.last_updated_time,'DD-MON-YYYY HH24:MI:SS') "last_metada
    ta_load",
    4 TO_CHAR(a.marker_timestamp,'DD-MON-YYYY HH24:MI:SS') "last_severit
    y_load",
    5 TO_CHAR(t.last_load_time,'DD-MON-YYYY HH24:MI:SS') "last_metric_lo
    ad"
    6 FROM mgmt_targets t, mgmt_availability_marker a
    7 WHERE t.target_guid = a.target_guid
    8 AND t.target_name = 'aix09'
    9 AND t.target_type = 'host';
    TARGET_NAME
    TARGET_TYPE discovery_time
    last_metadata_load last_severity_load last_metric_load
    aix09
    host 03-AUG-2004 14:47:55
    05-AUG-2004 18:28:45 05-AUG-2004 18:30:42 05-AUG-2004 17:13:55
    Does any one know what do I have to do to solve this problem ?
    Thanks in advance,
    Vitor

    Can you start a browser on the client machine?
    (netscape/mozilla) and try to load
    http://aix09:1830/emd/main
    Make sure both the client and the OMS server can resolve aix09 hostname
    Make sure the client can resolve the OMS server name.

  • Backup Suspended on Agent Unreachable - 11GR2 Windows

    Hi as the title suggests an RMAN backup has gone into a state of Suspended on Agent Unreachable.
    I have a 2 node RAC and have run emctl status dbconsole on each node. On node 1 I get a message: EM Daemon is running. On node 2 I get a message: Oracle enterprise Manager 11g is running.
    Why are these messages different? and could this be the reason why the job has gone into the state it has?
    Thanks in advance

    I strongly suggest to not using RMAN via OEM, but with the good old command line.
    The messages are different because on one node there is the real web app (oc4j...) while on the other one there is only the agent running so it is expected.
    Alessio

  • DBConsole says 'Agent Unreachable' after database restore & recovery

    Hi,
    Last week our server crashed and I had to completely re-install oracle and then restore/recover our database. Now everything is back up, but when I try to access the online DBConsole (http://localhost:5500/em), the status says 'Agent Unreachable'.
    I checked the status of the agent and it said Agent is Running and Ready.
    I was told that if the agent was not restored, it may be out of sync -- but I don't know how to sync it.
    Does anybody know how I can resolve this problem?
    Thanks in advance,
    Nora

    As per note_id:430805.1
    3. We now need to focus also on the monitored database side. This section takes place in the monitored RDBMS Oracle Home:
    If the monitored database is 10gR1 (10.1.x):
    10.1.0.4: you need to apply Patch 5868695 on the RDBMS Oracle Home, otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
    10.1.0.5: At this moment, this specific one-off patch is not available on top of RDBMS 10.1.0.5. Please contact support if you need this fix for RDBMS 10.1.0.5 on HP-UX.
    10.1.0.3, 10.1.0.2: consider patching / upgrading
    If the monitored database is 10gR2 (10.2.x):
    10.2.0.3 (and above): nothing to be done. The fix is already included.
    10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
    My concern is what if we have 8i and 9i monitored databases?Please let me know.

  • Status:  Agent Unreachable

    Hi,
    I have installed 10g. I could access the EM very easily, once all the required services were started. it was http://host:5500/em
    Then I installed another database, other than the default which was orcl.
    Then the port number changed (I do not know why, but when I looked in portlist.ini) just to try different ports, I figured out, it was not
    http://host:5502/em
    when I hit it, it prompts for userid and password. I was so happy looking at this screen, but once I enter the userid and password, what is get is
    Status: Agent Unreachable with Startup/Shutdown option. When I click on it, I get error "500 Internal Server Error" in my browser.
    Thanks in advance

    If you have done two different Oracle Installations that will use different Standalone DB Console and two different Agents, your system may have had a problem starting the two agents.
    If you are using Windows, have a look at Services to see the Agents which has the name of the new ORACLE_HOME as part of the name. Start the Agent. If you have a problem starting thet new one, stop the first one you installed, then start the new one.

  • Agent Unreachable, collection status: file handles exhausted

    Hi, I have a problem with management agent. Status of agent in grid control is Agent Unreachable. Here is an output of emctl status agent:
    Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.5.0
    OMS Version : 10.2.0.5.0
    Protocol Version : 10.2.0.5.0
    Agent Home : /opt/oracle/agent10g
    Agent binaries : /opt/oracle/agent10g
    Agent Process ID : 26832
    Parent Process ID : 26821
    Agent URL : https://bs11.xxxx.lan:3873/emd/main/
    Repository URL : https://gridcontrol.xxxx.lan:1159/em/upload
    Started at : 2010-07-06 14:24:30
    Started by user : oracle
    Last Reload : 2010-07-06 14:31:50
    Last successful upload : 2010-07-06 15:11:47
    Total Megabytes of XML files uploaded so far : 51.87
    Number of XML files pending upload : 4
    Size of XML files pending upload(MB) : 0.01
    Available disk space on upload filesystem : 60.35%
    Collection Status                            : File handles exhausted
    Last successful heartbeat to OMS : 2010-07-06 15:11:52
    I wonder what does this message mean Collection Status                            : File handles exhausted I can't find any solution to my problem, I tried restarting agent, clearstate, upload, resynchronization... all of this did nothing.

    Did you already check: Master Note for 10g Enterprise Manager Grid Control Agent Performance & Core Dump issues [ID 1087997.1]
    On http://support.oracle.com
    https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocTitle=Master%20Note%20for%2010g%20Enterprise%20Manager%20Grid%20Control%20Agent%20Performance%20&%20Core%20Dump%20issues&bmDocDsrc=KB&bmDocType=BULLETIN&bmDocID=1087997.1&viewingMode=1143&from=BOOKMARK%29%29
    Regards
    Rob
    http://oemgc.wordpress.com

  • Agent Logs under agent names shows no information in CSD

    I have 1 supervisor and that supervisor needs to see the agent logs under each individual agent name but for some reason there is nothing being reported there. If an agent takes a call or makes a call, inbound or outbound will appear under the agent name with data but logs just will not show anything. Is there a setting somewhere i'm missing?          

    You may have already checked this and apologize if you did, but have you verified that the supervisor is configured to see the columns under the Logs?
    In Supervisor, go to View - Preferences.  In the window that appears, go to Team - Agent - Logs and click on "Configure" on the right side, in the "Columns" field.  Make sure that the columns have a check mark next to them.
    If that is ok, have you tried running Supervisor from a different machine to see if that works?

Maybe you are looking for

  • OPMN SERVER ERROR WHILE INSTALLING BI 11g

    Hi Guys, I have been trying to install obiee 11g on a VM machine in which 32 bit Windows XP OS has been installed. I have restarted Microsoft loopback adapter and have tried innumerable number of times but no sucess. I get an OPMN SERVER error while

  • A problem with BIOS ??

    Hello, I have a HP pavilion dv3 and seems that my BIOS is down...when I turn on the PC, my screen just keeps flashing black and white...I tried to turn it on by pressing the windows key with B and power button what worked just once and then I turned

  • Reading and internal table

    I have the following code but it doens't like  this line. Hod do i need to code this corectly LOOP AT WA_DATAPACKAGE INTO WA_DATAPACKAGE_LN.     wa_TABIX = SY-TABIX.         READ table DATA_PACKAGE INTO WA2_DATAPACKAGE_LN                      WITH KE

  • Change invoice status on old sales order?

    Hi, We are trying to archive old sales order but we got problem with some old sales orders. The sales orders aren't invoiced (for different reasons) so we can't archive them (Overall status: Being processed). Since the sale orders are very old we don

  • How to unlock iphone 5 while overseas

    I have tried to use a Vodafone SIM card while in Romania and I get the message that "the SIM card is from a carrier that' not supported by the activation policy that's currently assigned by the activation server." How can I unlock this phone? I can't