Reg  oms and agent versions

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

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

Similar Messages

  • OMS and Agent Communication Problem?

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

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

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

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

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

  • ORACLE GRID OMS and agent service issue..

    Dear all,
    i am a solaris admin..please help me .. I am facing problem in discover oracle database through oracle agent...
    We installed oracle DB 10g R2 in solaris standalone server ..we have install OMS .. hostname is hostname01
    We have install OMS client at windows server in some domain host.domain.com
    Is it possible to install and configure OMS and Client in non domain [dns] environment?
    because we can able ping ip address from windows to solaris and vice vesa...
    but i can't able to nslookup..because sun server not in that domain... nslookup only search at DNS server ...
    it wouln't resolve hostname to ip address...
    what is procedure to configure in OMS and client in non -DNS environment??

    update the hosts file on all (client, OMS server, db server) sides to be able to ping by name from any server.
    eg.
    solaris /etc/hosts
    10.121.121.3 <servername>.<domian> <alias>
    retry your ping test by name.

  • Patching Grid Control OMS and Agent to 10.2.0.5 issue

    Oracle 11gR1 RHEL5 - Grid Control 10.2.0.5
    Hi All,
    I have been stuck on this issue for over a month (was relying on Oracle supports help and they just would not reply) and I can't figure it out. Basically, what happened is that my 10.2.0.5 patch set failed partiallty when I was applying it to the OMS. Here is what is going on right now:
    Database Repository (EMREP) - 11gR1 (11.1.0.6) - /opt/app/oracle/product/11.1.0/db_1
    OMS - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/oms10g
    Agent - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/agent10g
    When I was almost done with the 10.2.0.5 patch on the OMS, OUI gave me the following error:
    SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration
    assistants at this time. Not successfully running any "Recommended" assistants
    means your system will not be correctly configured.
    *1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the*
    failures.
    *2. Fix the errors causing these failures.*
    *3. Select the failed assistants and click the 'Retry' button to retry them*
    When I checked the logs I found the following messages (Here is a part of it...I think before it started to fail):
    Finished deleting the above files...
    INFO: Configuration assistant "OMS Oneoff Patch Application" succeeded
    INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
    For more details :
    -For configuration issues, look at the log files present in following location:
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
    -For repository failures, look at the log files
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.
    2.0.5.0
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
    -If not able to identify the repository issues, contact ORACLE Support.
    -After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
    Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
    For UNIX :
    ./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    For Windows :
    runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
    Exception : java.lang.Exception: Command: /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rhel-grid)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep))) -action upgrade -no_transx -no_verify -verbose -repos_user sysman -output_file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 failed. Exit code: expected [0 ], but got 45
    INFO: Configuration assistant "Repository Upgrade" failed
    *** Starting OUICA ***
    Oracle Home set to /opt/app/oracle/product/10.2.0/grid_1/oms10g
    Configuration directory is set to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs. All xml files under the directory will be processed
    Parsing configuration file config.xml ....
    Ended Parsing configuration file config.xml
    Start Processing configuration tool Oracle Internet Directory Patch Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Buffer size for copying file is set to 2048
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Oracle Internet Directory Patch Configuration Assistant
    Start Processing configuration tool Directory Integration Platform Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Directory Integration Platform Configuration Assistant
    Start Processing configuration tool OC4J Instance Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/home_default_island_1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/operations from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/log.xml
    Number of file(s) copied is 1
    Number of directories copied is 0
    End Processing configuration tool OC4J Instance Configuration Assistant
    Start Processing configuration tool OPMN Configuration Assistant - start HTTP server....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
    Number of directories copied is 0
    End Processing configuration tool OPMN Configuration Assistant - start OCA Instance
    Start Processing configuration tool Wireless Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Wireless Configuration Assistant
    Start Processing configuration tool Wireless Metadata Repository Update....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Wireless Metadata Repository Update
    Start Processing configuration tool Portal Metadata Repository Update....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Portal Metadata Repository Update
    Start Processing configuration tool OPMN Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/states from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCacheAdmin~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EM~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/dcm-daemon~dcm-daemon~dcm~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ons.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCache~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EMPROV~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~home~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/opmn.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/HTTP_Server~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ipm.log
    Number of file(s) copied is 10
    Number of directories copied is 0
    End Processing configuration tool OPMN Configuration Assistant
    Start Processing configuration tool Application Server Control Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/pafLogs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.10
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.4
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.7
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/nfsPatchPlug.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-application.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.9
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.8
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emctl.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/server.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/secure.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.6
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em.nohup
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.errors
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-web-access.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emias.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.5
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0.errors
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.3
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/rmi.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.2
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emca_repos_out_of_box12_56_33.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log.1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.transx
    Number of file(s) copied is 34
    Number of directories copied is 0
    End Processing configuration tool Application Server Control Configuration Assistant
    Start Processing configuration tool DCM Repository Update Assistant ....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/dcmctl_logs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/emd_logs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/daemon_logs from the file path expanding...
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool DCM Repository Update Assistant
    INFO: The "/opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.
    INFO: Since the option is to overwrite the existing /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands file, backing it up
    INFO: The backed up file name is /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands.bak.1
    SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctly configured.
    1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
    2. Fix the errors causing these failures.
    3. Select the failed assistants and click the 'Retry' button to retry them.
    INFO: User Selected: Yes/OK
    INFO: Starting to execute configuration assistants
    INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
    For more details :
    -For configuration issues, look at the log files present in following location:
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
    -For repository failures, look at the log files
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
    -If not able to identify the repository issues, contact ORACLE Support.
    -After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
    Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
    For UNIX :
    ./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    For Windows :
    runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
    Exception : java.lang.Exception:
    REPOSITORY UPGRADE STATUS : 3
    INFO: Configuration assistant "Repository Upgrade" failed
    I would appreciate any help on this as I have been stuck on it since April :( Not too happy with Oracle Support.
    Thanks much to all!
    JrOraDBA

    Here is the output for when I applied the patch:
    opatch apply
    Invoking OPatch 10.2.0.3.0
    Oracle interim Patch Installer version 10.2.0.3.0
    Copyright (c) 2005, Oracle Corporation.  All rights reserved..
    Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
    Central Inventory : /opt/app/oracle/oraInventory
    from           : /etc/oraInst.loc
    OPatch version    : 10.2.0.3.0
    OUI version       : 10.2.0.3.0
    OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
    Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-04-22_12-07-14PM.log
    ApplySession applying interim patch '4329444' to OH '/opt/app/oracle/product/10.2.0/grid_1/db10g'
    Invoking fuser to check for active processes.
    Invoking fuser on "/opt/app/oracle/product/10.2.0/grid_1/db10g/bin/oracle"
    OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
    Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
    *(Oracle Home = '/opt/app/oracle/product/10.2.0/grid_1/db10g')*
    Is the local system ready for patching?
    *Do you want to proceed? y*
    y
    User Responded with: Y
    Backing up files and inventory (not for auto-rollback) for the Oracle Home
    Backing up files affected by the patch '4329444' for restore. This might take a while...
    Backing up files affected by the patch '4329444' for rollback. This might take a while...
    Patching component oracle.rdbms, 10.1.0.4.0...
    Updating archive file "/opt/app/oracle/product/10.2.0/grid_1/db10g/lib/libserver10.a"  with "lib/libserver10.a/qerix.o"
    ApplySession adding interim patch '4329444' to inventory
    Verifying the update...
    Inventory check OK: Patch ID 4329444 is registered in Oracle Home inventory with proper meta-data.
    Files check OK: Files from Patch ID 4329444 are present in Oracle Home.
    Running make for target ioracle
    The local system has been patched and can be restarted.
    OPatch succeeded.
    However, the weird thing is that I don't see it in the lsinventory:
    */opt/app/oracle/product/10.2.0/grid_1/db10g/OPatch/opatch lsinventory*
    Invoking OPatch 10.2.0.3.0
    Oracle interim Patch Installer version 10.2.0.3.0
    Copyright (c) 2005, Oracle Corporation.  All rights reserved..
    Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
    Central Inventory : /opt/app/oracle/oraInventory
    from           : /etc/oraInst.loc
    OPatch version    : 10.2.0.3.0
    OUI version       : 10.2.0.3.0
    OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
    Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-06-09_09-37-54AM.log
    Lsinventory Output file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/lsinv/lsinventory2009-06-09_09-37-54AM.txt
    Installed Top-level Products (2):
    Oracle Database 10g Patch Set 3                                      10.1.0.5.0
    Oracle Enterprise Manager Repository Database                        10.2.0.3.0
    There are 2 products installed in this Oracle Home.
    Interim patches (1) :
    Patch  5632264      : applied on Thu Apr 23 12:23:10 CDT 2009
    Created on 8 Feb 2007, 00:38:09 hrs PST8PDT
    Bugs fixed:
    *5632264*
    OPatch succeeded.
    Do you think I should restore the backup (and I only have the database backup, not the Oracle Home backup)?
    THanks.

  • OMS vs Agent version

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

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

  • How much Maximum  Distance  I would keep between Oracle EM OMS and Agent ?

    Hello There,
    Here I am asking little curious question which come in my mind ?
    Actually We have many client geographically located in different cities.And we are remotely managing their databases on VPN.
    I just wanted to Install One Enterprise Manager Grid control for all these databases.
    Here I assume we have 10Mbps Line between our head quater and Clients.
    And regular agent upload max 1.5GB per month for each client.
    Is it possible ?
    If possible how much max distance(miles) do you recommended.
    Thanks
    Hemesh.
    Edited by: Hemss on Jan 28, 2011 5:14 PM

    Hi Hemesh,
    are you sure that 2 GB of data are uploaded with every heartbeat? The best idea to figure out would be - from my point of view - just to test
    it. Otherwise you will not get any feeling for the upload amount and upload time...

  • Reg:Operative and simulation version comparison in cn41

    Hi,
    I am doing comparison of date between Operative project and Simulation project(cn41) .But all the object are displaying row wise in single column
    Project Object                                      Ear Start                        Ear Finish
    Activity1(operative)                                  11.03.2011                        16.03.2011
    Activity1(Simulation)                                 20.03.2011                       15.03.2011
    But I want it to display like this(Both operative and simulation separately)
    Project Object       Ear Start(Op)          Ear Finish(Op)  Ear Start(Si)         Ear Finish(Si)
    Activity1(operative)   
    Activity1(Simulation)                                                   
    How it can be possible.Can Any body give some idea and way to resolve this issue.
    With Regards
    Rohit Prakash
    Edited by: rohitSAPCOMMUNITY on Mar 15, 2011 6:16 AM

    hi sophie,
    create separate network for each wbs in project.  see if this can solve your issue.
    vengaiah chowdary

  • Difference between OMS system time and Agent system time is 117 mins and ha

    Hi Guys,
    In one of my office server i have changed the system time.After changing the time i have got this below alert.
    Could please help me out...

    Please, provide more details:
    1. Is the agent and OMS on the same machine?
    2. If different, is the system time on both machines identical?
    3. What is the operating system for OMS and agent?
    -- Sergiusz

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

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

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

  • Help with solman version and agents

    We configured RCA in Solution Manager and would like to verify the agent versions we've installed if they are ok. Please note
    The following installations in Solution Manager
    Solution Manager v7.01 sp23 ehp1 sp06
    Wiley EM 8.0.2
    ISAGENT  8 SP2 (8.2.2.0.20100713084111)  /LM-SERVICE  7.01 SP7
    Diagnostic Agents 7.11
    Following installations in managed systems
    Version of most managed systems NW7.01
    Diagnostic Agent 7.11
    ISAGENT  8 SP2 (8.2.2.0.20100713084111)   (as seen in Agent admin)
    Are these versions correct? I've looked at numerous notes and they seem ok.
    We've tested and almost all features are working. We did not install saphostagent and i was told by SAP it is absolutely required for NW7.11.
    If we decide not to install the hostagents at our current version, would all RCA functionality work?
    Thanks and appreciate your assistance on this.

    Hello
    The following installations in Solution Manager
    Solution Manager v7.01 sp23 ehp1 sp06 = OK
    Wily EM 8.0.2 --> I would update to 8.2.2.0  I'm not sure on your Wily vs ISAGENT versioning. The installation guide of Wily Introscope sais connecting a newer agent to an older version of Wily EM doesn't work properly, it doesn't specify if they mean ISAGENT 8 to Wily EM 7 or also ISAGENT 8.2.2 to EM 8.0.2 so I would update Wily EM to 8.2.2 to be sure
    ISAGENT 8 SP2 (8.2.2.0.20100713084111) /LM-SERVICE 7.01 SP7  = OK
    Diagnostic Agents 7.11 = OK
    Following installations in managed systems
    Version of most managed systems NW7.01
    Diagnostic Agent 7.11 = OK
    ISAGENT 8 SP2 (8.2.2.0.20100713084111) (as seen in Agent admin) = OK
    Install the SAPHost Agents to make sure you have all relevant data available, make sure you check the SAP note concerning running SAPosCol as a service under the SAPHostAgent
    Also make sure you implement the dispatcher in diagnostics (SAP note available to get dispatcher in diagnostics metrics) and a dashboard is also available to implement in Wily
    Kind regards
    Tom
    Edited by: Tom Cenens on Nov 30, 2010 9:16 AM

  • OMS showing agent unreachable but agent is up

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

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

  • OMS, Repository, Agent Grid upgrade

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

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

  • Performing targets discovery and agent configuration --- HANGS

    Hello,
    I'm running Grid Control 10.2.0.4 on windows2003 server. I have installed the agent on a number of systems with no problem.
    BUT, on one server the install seems to HANG during the:
    "Performing targets discovery and agent configuration" step.
    below is the last entry in my log file. So a couple questions:
    1. Any ideas what is going on?
    2. If I cancel it the install, can I restart it manually (agentca -d ???)
    3. What logs should I look at.
    I have tried installing it on this server several times with no luck. I also had problems upgrading from DB 10.2.0.1 to 10.2.0.3. The DBUA would say "thinks this is a Rerun operation" and recommend I remove some file that doesn't exist (but this is a seperate issue, just included it FYI).
    installActions2008-03-13_03-03-56PM.log
    Backing up files and inventory (not for auto-rollback) for the Oracle Home
    Backing up files affected by the patch '5961654' for restore. This might take a while...
    Backing up files affected by the patch '5961654' for rollback. This might take a while...
    Patching component oracle.oracore.rsf, 10.2.0.3.0...
    Copying file to "g:\oracle\agent10g\bin\oracore10.dll"
    Copying file to "g:\oracle\agent10g\rdbms\admin\oracore10.sym"
    Copying file to "g:\oracle\agent10g\
    lib\oracore10.lib"
    ApplySession adding interim patch '5961654' to inventory
    Verifying the update...
    Inventory check OK: Patch ID 5961654 is registered in Oracle Home inventory with proper meta-data.
    Files check OK: Files from Patch ID 5961654 are present in Oracle Home.
    The local system has been patched and can be restarted.
    OPatch succeeded.
    Finished one-offs apply...
    Deleting the files...
    Finished deleting the above files...
    INFO: Configuration assistant "Oneoff Patch Application" succeeded
    INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn
    INFO: Install area Control created with access level 1
    Performing free port detection on host=gridTEST
    Securing the agent
    Performing targets discovery and agent configuration
    CfmLogger_2008-03-13_03-10-51-PM.log
    INFO: oracle.sysman.top.agent:Executing Command: g:\oracle\agent10g\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe G:\oracle\agent10g\sysman\admin\discover\oracledb.pl G:\oracle\agent10g gridTEST

    I get:
    G:\>emctl status agent
    Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.4.0
    OMS Version : 10.2.0.4.0
    Protocol Version : 10.2.0.4.0
    Agent Home : g:\oracle\agent10g
    Agent binaries : g:\oracle\agent10g
    Agent Process ID : 3548
    Agent URL : ( I deleted this)
    Repository URL : ( I deleted this)
    Started at : 2008-03-13 17:21:11
    Started by user : SYSTEM
    Last Reload : 2008-03-13 17:21:11
    Last successful upload : 2008-03-13 17:21:56
    Total Megabytes of XML files uploaded so far : 0.30
    Number of XML files pending upload : 3
    Size of XML files pending upload(MB) : 0.17
    Available disk space on upload filesystem : 9.55%
    Last successful heartbeat to OMS : 2008-03-13 17:21:25
    Agent is Running and Ready
    G:\>emctl pingOMS
    Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD pingOMS completed successfully
    Now I see the server in Grid Control. THANKS!!!!!!!!!!!!!!

  • Fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'

    Hi all,
    I have a Team Foundation Build Agent that has Visual Studio Team System 2008 Test Edition installed. One of the solutions that I compile with that Build Agent gives me the following errors:
      VCBUILD : fatal error C1047: The object or library file '.\bin\Release\main.obj' was created with an older compiler than other objects; rebuild old objects and libraries
      LINK : fatal error LNK1257: code generation failed
      VCBUILD : fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'
      LINK : fatal error LNK1257: code generation failed
    I've searched online and found that other people have experienced the same problem:
    http://software.intel.com/en-us/forums/intel-c-compiler/topic/62516/
    http://nuicode.com/issues/266
    In the second posting one states "I had the same Error! After installing Service Pack1 for VS2008 it worked!". Thats great for him but I don't see any such update for the Test Edition of Visual Studio Team System 2008 - Test Edition.
    What can I do to get rid of that problem?
    Thanks!

    Hello ACKH
    I once handled a similar case in newsgroups. That case exhibit a almost same symptom. Please check out my summary below:
    Problem
    In that case, the customer has a DLL project that you had built on a machine where VS 2008 SP1 was installed. You then attempted to rebuild that project on a machine without SP1, and got a fatal compiler error C1900 “IL mismatch between ‘P1’ version ‘20080116’ and ‘P2’ version ‘20070207’”, and then LNK1257 “Code generation failed”. He found that rebuilding your static library alleviated the errors, but cannot accept this as a workaround because your clients will not have the ability to rebuild the libraries you distribute before they use them.
    Cause
    You had built the static library with the /GL (Whole Program Optimization) compiler switch, which requires Link Time Code Generation (/LTCG) when the static library is subsequently linked. These features require that all linked modules be built by the same version of the compiler. In fact, if precompiled headers are used, the same machine must build and link all the involved object code. Therefore, it is highly recommended that static libraries not be built with the /GL switch, since their intended use is quite frequently to support reuse by others.
    Solution
    You rebuilt the static library on your VS2008 SP1 machine without the /GL switch, and you no longer encounter this problem.
    Please let me know if this info is helpful to you or not.
    Regards,
    Jialiang Ge
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact [email protected]
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Maybe you are looking for