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.

Similar Messages

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 Ive 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.

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.

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]"

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.

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

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 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.

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.

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
$

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.

DB console Agent Unreachable in Windows 2003 server

Hi All,
I am facing a problem with one of the production database's DB console. Database verison is 10.1.0.5.0.
Once I logged in to the DB console I am noticing a status message saying Agent Unreachable.
I am not getting any updated report about the database.
I have done restart of DB OracleDB console<DB name> services. But no luck.
Kindly help me in resolving this issue ASAP.
regarrdsl.
Aruna

Hi,
Please find the following last 100 lines taken from DB console log file
-------------- [OracleDBConsoleTC08PRD] ------------
EMDROOT=G:\oracle\product\10.1.0\db_1
ORACLE_HOME=G:\oracle\product\10.1.0\db_1
EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
CONSOLE_CFG=dbconsole
TRACE_LEVEL=16
TIMEOUT=15
10/28/09 12:31:37 Job Process API is available
10/28/09 12:31:37 Start pending...
10/28/09 12:31:37 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
10/28/09 12:31:40 dbconsole launch commandline is "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istart dbconsole
10/28/09 12:31:40 Tracking process launch...
10/28/09 12:32:12 Received exitCode 3 from emctl istatus
10/28/09 12:32:12 dbconsole started
10/29/09 06:43:19 Recieved ServCtrlHdlr command, 1
10/29/09 06:43:19 Stopping dbconsole
10/29/09 06:43:19 Launching stop EMD process...
10/29/09 06:43:19 Waiting for stop EMD process to exit. numRetries=74
10/29/09 06:43:23 Stop process has exited with exitCode: 0
10/29/09 06:43:23 Waiting for emwd process to exit. numRetries=74
10/29/09 06:43:23 Watchdog process exited with exit code 55
10/29/09 06:43:23 Signal Shutdown event.
10/29/09 06:43:23 Shutdown thread exited.
10/29/09 06:43:23 ServiceMain wake up by ShutdownProc, emwd has exited. ServiceMain exits
-------------- [OracleDBConsoleTC08PRD] ------------
EMDROOT=G:\oracle\product\10.1.0\db_1
ORACLE_HOME=G:\oracle\product\10.1.0\db_1
EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
CONSOLE_CFG=dbconsole
TRACE_LEVEL=16
TIMEOUT=15
10/29/09 06:43:57 Job Process API is available
10/29/09 06:43:57 Start pending...
10/29/09 06:43:57 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
10/29/09 06:44:01 dbconsole launch commandline is "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istart dbconsole
10/29/09 06:44:01 Tracking process launch...
10/29/09 06:44:36 Did not hear back from emctl istatus.
10/29/09 06:44:36 Waiting a further 5 secs...
10/29/09 06:44:41 Did not hear back from emctl istatus.
10/29/09 06:44:41 Waiting a further 5 secs...
10/29/09 06:44:46 Did not hear back from emctl istatus.
10/29/09 06:44:46 Waiting a further 5 secs...
10/29/09 06:44:51 Did not hear back from emctl istatus.
10/29/09 06:44:51 Waiting a further 5 secs...
10/29/09 06:44:56 Did not hear back from emctl istatus.
10/29/09 06:44:56 Waiting a further 5 secs...
10/29/09 06:45:01 Did not hear back from emctl istatus.
10/29/09 06:45:01 Waiting a further 5 secs...
10/29/09 06:45:06 Did not hear back from emctl istatus.
10/29/09 06:45:06 Waiting a further 5 secs...
10/29/09 06:45:11 Did not hear back from emctl istatus.
10/29/09 06:45:11 Waiting a further 5 secs...
10/29/09 06:45:16 Did not hear back from emctl istatus.
10/29/09 06:45:16 Waiting a further 5 secs...
10/29/09 06:45:21 Did not hear back from emctl istatus.
10/29/09 06:45:21 Waiting a further 5 secs...
10/29/09 06:45:26 Did not hear back from emctl istatus.
10/29/09 06:45:26 Waiting a further 5 secs...
10/29/09 06:45:31 Did not hear back from emctl istatus.
10/29/09 06:45:31 Waiting a further 5 secs...
10/29/09 06:45:34 dbconsole exited with retCode 55.
10/29/09 06:45:34 Check G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD\sysman\log\emdbconsole.nohup for details
-------------- [OracleDBConsoleTC08PRD] ------------
EMDROOT=G:\oracle\product\10.1.0\db_1
ORACLE_HOME=G:\oracle\product\10.1.0\db_1
EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
CONSOLE_CFG=dbconsole
TRACE_LEVEL=16
TIMEOUT=15
10/29/09 06:47:52 Job Process API is available
10/29/09 06:47:52 Start pending...
10/29/09 06:47:52 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
10/29/09 06:47:54 dbconsole may already be running. termStatus=3

Rman jobs "Suspended on Agent Unreachable"

I don't know if this problem is coming from rman, EM, or jobs. The only time it occurs is when I create an "Oracle Recommended" backup job thorugh EM.
The job status is immediately suspended with the message "agent unreachable."
Other RMAN functions that run in jobs scheduled through EM work fine (crosscheck for example). It only happens with I schedule backups through the Oracle Recommended link in EM.
In the meantime, I'm running backups manually at the RMAN prompt.
There's hardly any literature on Metalink or on the forums about this. Can anyone shed some light?

I just ran across this thread when I was looking for a solution for the same issue ("Suspended on Agent Unreachable") hat had just happened to me. In my case, it was on RAC. I got that error when I created custom job and submitted it against cluster. The backup went OK, however, when I picked up one node, and submitted the same custom backup job from the specific node.

Rman jobs "Suspended on Agent Unreachable" through EM

Hi, all:
when I schedule an RMAN backup in OEM, It has a
suspended on agent unreachable status immediately. Deleting the job and creating a new one, and the new job became suspended even before it's first scheduled job
I can manually backup through rman prompt, no problem.
The database is RAC 10.2.0.3 on linux*86.
I checked web found lots of friends had the same problem without solutions, is there anyone has experience to fix it?
Thanks a lot

Have you done anything to determine why the agent is unreachable such as checking its status with emctl or reading a log file?

Status: Agent Unreachable

Similar Messages

Maybe you are looking for