OMS version

Hello,
I am looking to find my correct OMS version.
When I check my emctl status agent I get my oms verison higher
that what I get from my OEM10G instance grid home page version.
Shouldn't this two be the same ?
Thanks.

what's the o/p of
emctl getversionFrom Agent home/bin
Z:\OEM\agent10g\BIN>emctl getversion
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
       Enterprise Manager 10g Agent Version 10.2.0.4.0From OMS Home/bin
Z:\OEM\oms10g\BIN>emctl getversion
Oracle Enterprise Manager 10g Release 4 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
       Enterprise Manager 10g OMS Version 10.2.0.4.0
       Enterprise Manager 10g AS Control Version 10.2.0.0
       Enterprise Manager 10g Agent Version 10.2.0.4.0these confirms yours oms and agent versions. If you see a different release number other than these on the grid console let us know.

Similar Messages

  • OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0

    Im trying to start the database enterprise manager and I get this error on the log file:
    OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0 Repository needs to be patched.
    Database version is 11.2
    O.S. version is: Linux 2.6.9-78.0.0.0.1.ELsmp #1 SMP Fri Jul 25 14:41:56 EDT 2008 i686 i686 i386 GNU/Linux
    I use this to upload database and console:
    export ORACLE_HOME=/opt/oracle/product/11.2.0/dbhome_1/
    export ORACLE_BASE=/opt/oracle/
    export ORACLE_SID=orcl
    /opt/oracle/product/11.2.0/dbhome_1/bin/lsnrctl start
    /opt/oracle/product/11.2.0/dbhome_1/bin/dbstart /opt/oracle/product/11.2.0/dbhome_1/
    /opt/oracle/product/11.2.0/dbhome_1/bin/emctl start dbconsole
    when I excecute that, I see this on the console:
    Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
    https://192.168.2.210:1158/em/console/aboutApplication
    Starting Oracle Enterprise Manager 11g Database Control ........... started.
    Logs are generated in directory /opt/oracle/product/11.2.0/dbhome_1/machine_one_lega/sysman/log
    So I try to go there, and the web browser shows this:
    503 Service Unavailable
    Service is not initialized correctly. OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0.
    Can you help me find this solution?
    thanks

    Hi Ingenio,
    This problem sometimes occur when the listener is not running, hence connection cannot be done without listener.

  • OEM--Service is not initialized correctly OMS version 10.2.0.4.2 is not com

    Hi,
    I impdp the few schemas from full dump file of the Production DB to Dev env. i realized after that system password was changed and OEM stop running. when i started the OEM and then try to get the page its shows this error. secondly i am not able to login as system. looks like the password is changed. infact i impdp as system. the account status of system shows open. its not a grid enterprise or RAC.
    503 Service Unavailable
    Service is not initialized correctly. OMS version 10.2.0.4.2 is not compatible with repository version 10.2.0.4.3.
    OEL version :Linux dev-dt 2.6.32-358.6.2.el6.x86_64 #1 SMP
    Oracle Version :Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
    Please suggests..
    Edited by: 975484 on May 21, 2013 6:49 AM
    Edited by: 975484 on May 21, 2013 6:50 AM

    975484 wrote:
    Hi,
    I impdp the few schemas from full dump file of the Production DB to Dev env. i realized after that system password was changed and OEM stop running. when i started the OEM and then try to get the page its shows this error. secondly i am not able to login as system. looks like the password is changed. infact i impdp as system. the account status of system shows open.
    503 Service Unavailable
    Service is not initialized correctly. OMS version 10.2.0.4.2 is not compatible with repository version 10.2.0.4.3.
    OEL version :Linux dev-dt 2.6.32-358.6.2.el6.x86_64 #1 SMP
    Oracle Version :Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
    Please suggests..recreate EM repository

  • Agent Status Reports OMS Version : (unknown)

    I upgraded our 11g OEM installation to 12.1.0.1 and just completed patching to 12.1.0.3. Some of the 11g agents were on platforms not supported by 12.1.0.1 (part of the motivation fro the 12.1.0.3 upgrade, now complete).
    Following the instructions in Chapter 7, Installing Oracle Management Agent in the Oracle Enterprise Manager Cloud Control Basic Installation Guide 12c Release 3 (12.1.0.3) I was able to get the agent installed and started on one of the servers I was not able to upgrade during the upgrade process. The new agent is up and running but reports OMS Version : (unknown) -
    cmspweb:app/agent12g/agent_inst/bin->./emctl status agent
    Oracle Enterprise Manager Cloud Control 12c Release 3
    Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
    Agent Version     : 12.1.0.3.0
    OMS Version       : (unknown)
    Protocol Version  : 12.1.0.1.0
    Agent Home        : /usr/local/oracle/app/agent12g/agent_inst
    Agent Binaries    : /usr/local/oracle/app/agent12g/core/12.1.0.3.0
    Agent Process ID  : 3821
    Parent Process ID : 3767
    Agent URL         : https://garmin.ucdavis.edu:3872/emd/main/
    Repository URL    : https://oracle-emrep1.ucdavis.edu:4904/empbs/upload
    Started at        : 2013-10-08 11:56:26
    Started by user   : oracle
    Last Reload       : (none)
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far : 0
    Number of XML files pending upload           : 0
    Size of XML files pending upload(MB)         : 0
    Available disk space on upload filesystem    : 69.43%
    Collection Status                            : Collections enabled
    Heartbeat Status                             : OMS is unreachable [bad response]
    Last attempted heartbeat to OMS              : 2013-10-08 14:30:13
    Last successful heartbeat to OMS             : (none)
    Next scheduled heartbeat to OMS              : 2013-10-08 14:30:43
    Agent is Running and Ready
    and the upload fails with the error EMD upload error:full upload has failed: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (OMS_DOWN) which makes sense. Searching the web I found a number of suggestions including securing the agent, which I was able to do and resynching the agent from the console which I am *not* able to do as the agent and targets are not showing in the console.
    The targets.xml file on the agent host has one line -
    <Targets AGENT_TOKEN="CB22F0CA441C8CDECF3CA3ABA0D8C02C9AACFF98A41D653CFB2F41B7BC41EE0D"/>
    and I realize that is not at all a complete file. In the gcagent.log file I see ping errors -
    2013-10-08 14:29:43,596 [319:8C08BF97] INFO - attempting initial heartbeat
    2013-10-08 14:29:43,805 [319:8C08BF97] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: ERROR- Failed to update Target type Metadata)
    2013-10-08 14:29:43,810 [319:8C08BF97] WARN - Ping protocol error
    o.s.gcagent.ping.PingProtocolException [OMS sent an invalid response: "ERROR- Failed to update Target type Metadata"]
    The firewall is open and the agent is using the correct port and I am stumped. If anyone has any suggestions I would certainly appreciate them.
    Thank you.
    Bill Wagman

    Is this a newly installed agent?
    Did it work before? What has changed since it last worked?
    Anything in the emagent.trc file?
    $emctl upload
    EMD upload error: uploadXMLFiles skipped :: OMS
    version not checked yet..
    this is emctl status agent[dev01/AixAgentOracleHome/agent10g]$emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.1.0.4
    Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.4.0
    OMS Version : UnknownThe agent does not connect successfully with the OMS, no version there.

  • Oracle Grid control 11gR1 : emctl start oms gives OMS version 11.1.0.1.0 is

    Hi, I have installed grid control 11gR1 on OEL 5.6 64 bit env. The repository db is oracle 11.1.0.7.0 with WLS 10.3.2
    My install of the Grid contol was a fresh install on a db and weblogic. Whenever i start the emctl start oms, i get the following error
    OMS version 11.1.0.1.0 is not compatible with repository version 10.2.0.4.0 Repository needs to be upgraded
    Eventhough my db is 11, which is the emctl giving the above error? Its starting the EMGC admin and OMS server ( i can see them running in weblogic console), but my EM console is not coming up, saying either WLS or OMS is down.
    i have tried to recreate repos db, droped and created it, but no luck.
    Appreciate any pointers. Also, if there is a sequence of steps to follow the grid contol uninstall and install, pls let me know.

    thx for the post. I had a successful install and I then logged on to the EM console and configured it to monitor the db instances. After a few days, the server restarted and after which i wasn't able to start the OMS and hence unable to logon to EM console.

  • OMS version 10.2.0.4.0 is not compatible with repository version 10.2.0.1.

    I restored database resulting in the above error.
    I guess my database backup was taken before grid control upgrade to 10.2.0.4.
    how to fix this? Thanks.

    See note "Oracle Enterprise Manager 10g Grid Control Certification Checker \[ ID 412431.1 \]". There is a nice application which shows all the compatible combinations. Only 10.2.0.4 is supported with 10GR4 OMS (10.2.x repository version).

  • Solaris 10.2 OEM Installation: but emctl displays OMS version is 10.1

    Hi,
    How can I validate the correct version of the installation I did. I though Iwas installing OEM GC Solaris 10.2.0.1. Installer said it was 10.2.0.1. I did an OMS and AGENT install all using same software distro and when I run ./emctl in the agent home/bin it says my Agent and OMS are version 10.1.0.1
    --catharine                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    I think the OTN at one time had the wrong software up there but if you saw it install 10.2 then you should have it. Any chance you are grabbing the emctl from another Oracle home?
    Of course you could check with ./runInstaller but how about just looking in /opt/app/oracle/product/agent10g/relnotes ?

  • OMS version 10.2.0.4.0 is not compatible with repository version 10.1.0.5.9 Repository needs to be patched.

    I received this message when attempting to restart the oms after performing:
    emca -deconfig dbcontrol db
    emca -repos recreate
    emca -config dbcontrol db
    in an effort to fix the problem:
    Getting Chrome browser error "SSL connection error" Error code: ERR_SSL_PROTOCOL_ERROR after upgrade
    Can you advise me as to where I may find this 10.2.0.4 patch for my repository?

    OMS is a term used with Grid Control (OMS app tier with Repository database and multiple agents).
    emca is used with DB Express on a single database instance to manage the DB Express repository info.
    They cannot be used together.
    Did you have Grid Control?:  If so, i believe you've corrupted your repository and need to restore, or contact Oracle Support.

  • What is the minimum server layer OEM version supports SNMP trap reception ?

    Hi:
    - I have been trying to enable SNMP trap reception on an OEM plug-in.
    - I turned on debug channel for recvlets.snmp and saw:
    2009-10-16 16:07:42,808 Thread-3028552624 ERROR recvlets.snmp: Duplicate threshold : test900, oracle_guide, interfaces, status
    and
    2009-10-16 16:09:08,382 Thread-3021634480 INFO recvlets.snmp: Trap received is to convert Data Point
    2009-10-16 16:09:08,379 Thread-3021634480 INFO recvlets.snmp: Sending Data Point ...
    2009-10-16 16:09:08,379 Thread-3021634480 INFO recvlets.snmp: Listening for TRAP
    So, it looks like the OEM agent can receive traps but no data point or alert appears.
    And, the agent always issues an error about duplicate thresholds.
    - Does the agent have to be patched ?
    My agent is:
    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.1.0
    Protocol Version : 10.2.0.0.0
    Agent is Running and Ready
    - on the server layer, the oms is:
    Oracle Enterprise Manager 10g Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Oracle Management Server is Up.
    Is a patch needed for OMS ?
    Should OMS be version 10.2.0.5.0 ?
    Thanks
    John
    Edited by: user8826739 on Feb 23, 2010 7:17 AM

    10.2.0.5 should be fine ...
    Dave

  • How Upgrade OMS to 10.2.0.5

    Dear Gurus,
    OS - RH5
    Oracle 10G2.4
    I need your help to understand something I don't get with my Grid Configuration.
    I've create a brand new Grid Database in 10.2.0.4
    Following all instruction to setup the Grid Control 10.2.0.5 which means
    Create Database - Ok
    1st - setup Grid 10.2.0.3 - Done - OK
    2nd - Apply patchset to upgrade into 10.2.0.5 - Ok ( !!!! )
    3rd - Deploy agent 10.2.0.3 and apply Patchset to upgrade into 10.2.0.5 - Done OK
    In all others servers the agent status shows :
    ++[oracle@srvldbt02 ~]$ 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 : /u01/app/oracle/product/agent10g++
    ++Agent binaries : /u01/app/oracle/product/agent10g++
    ++...++
    In the OMS server the agnet shows :
    +[oracle@srvldbp04 Disk1]$ emctl status agent+
    Oracle Enterprise Manager 10g Release 5 Grid Control
    Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
    Agent Version     : 10.1.0.4.2
    OMS Version       : Unknown
    Protocol Version  : 10.1.0.2.0
    Agent Home        : /u01/app/oracle/oms10g
    Agent binaries    : /u01/app/oracle/oms10g
    +...+
    Agent is Running and Ready
    [oracle@srvldbp04 Disk1]$
    Can you please tell me what shall I do? When I try to apply patch 10.2.0.5 which is in zip file
    gc_x86_64_10205_part1of2.zip and is patch 3822442
    the installed products shows - Installed !!!!!!
    It doesn't suggest me to upgarde .....
    My agent Home is
    Agent Home : /u01/app/oracle/oms10g
    Did I misss any step ?
    Txs if you can help

    Yeha, that's what is starnge
    In my OMS Folder there is an agenet but I don't know where !!!!
    +[oracle@srvldbp04 ~]$ emctl status agent+
    Oracle Enterprise Manager 10g Release 5 Grid Control
    Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
    Agent Version     : 10.1.0.4.2
    OMS Version       : Unknown
    Protocol Version  : 10.1.0.2.0
    Agent Home        : /u01/app/oracle/oms10g
    Agent binaries    : /u01/app/oracle/oms10g
    Agent Process ID  : 25301
    Parent Process ID : 25287
    Agent URL         : http://srvldbp04.int.imd.ch:1157/emd/main/
    Started at        : 2010-01-13 15:59:07
    Started by user   : oracle
    Last Reload       : 2010-01-13 15:59:07
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far :     0.00
    Number of XML files pending upload           :        0
    Size of XML files pending upload(MB)         :     0.00
    Available disk space on upload filesystem    :    30.98%
    Agent is Running and Ready
    +[oracle@srvldbp04 ~]$+
    +[oracle@srvldbp04 oms10g]$ pwd+
    +/u01/app/oracle/oms10g+
    +[oracle@srvldbp04 oms10g]$ ls -lrt+
    total 1260
    -rwxr-xr-x  1 oracle oinstall   6133 May 20  2005 README.htm
    -r-xr-----  1 oracle oinstall   1082 Dec 24  2008 oc4j_OCMRepeaterDeploy.sh
    -rw-rw-r--  1 oracle oinstall 961995 Feb  4  2009 OCMRepeater.ear
    -rw-r--r--  1 oracle oinstall     62 Nov 26 16:26 oraInst.loc
    drwx-w-rwx  7 oracle oinstall   4096 Nov 27 11:50 jdk
    drwx-w--w-  3 oracle oinstall   4096 Nov 27 11:50 jre
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 rlmgr
    drwx------  4 oracle oinstall   4096 Nov 27 11:51 emcli
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 agentdeploy
    drwx------  7 oracle oinstall   4096 Nov 27 11:51 uddi
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 syndication
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 has
    drwx------  8 oracle oinstall   4096 Nov 27 11:51 datadirect
    drwx------  6 oracle oinstall   4096 Nov 27 11:51 backup_restore
    drwx------  5 oracle oinstall   4096 Nov 27 11:51 sso
    drwx------  6 oracle oinstall   4096 Nov 27 11:51 javacache
    drwx------  5 oracle oinstall   4096 Nov 27 11:51 upgrade
    drwx------  7 oracle oinstall   4096 Nov 27 11:51 opmn
    drwx------  5 oracle oinstall   4096 Nov 27 11:51 iaspt
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 slax
    drwx------  5 oracle oinstall   4096 Nov 27 11:51 precomp
    drwx------  5 oracle oinstall   4096 Nov 27 11:51 plsql
    drwx------ 10 oracle oinstall   4096 Nov 27 11:51 rdbms
    drwx------  3 oracle oinstall   4096 Nov 27 11:51 srvm
    drwx------  6 oracle oinstall   4096 Nov 27 11:51 javavm
    drwx------  4 oracle oinstall   4096 Nov 27 11:51 oracore
    drwx------  5 oracle oinstall   4096 Nov 27 11:52 portal
    drwx------  5 oracle oinstall   4096 Nov 27 11:52 perl
    drwx------  3 oracle oinstall   4096 Nov 27 11:52 sqlj
    drwx------  6 oracle oinstall   4096 Nov 27 11:52 webservices
    drwx------  9 oracle oinstall   4096 Nov 27 11:52 diagnostics
    drwx------  6 oracle oinstall   4096 Nov 27 11:52 xdk
    drwx------  3 oracle oinstall   4096 Nov 27 11:52 jsp
    drwx------  4 oracle oinstall   4096 Nov 27 11:52 wireless
    drwx------  4 oracle oinstall   4096 Nov 27 11:52 wcs
    drwx------  5 oracle oinstall   4096 Nov 27 11:52 nls
    drwx------  4 oracle oinstall   4096 Nov 27 11:52 jdbc
    drwx------  2 oracle oinstall   4096 Nov 27 11:52 mesg
    drwx------  6 oracle oinstall   4096 Nov 27 11:52 sqlplus
    drwx------  6 oracle oinstall   4096 Nov 27 11:52 clone
    drwx------  7 oracle oinstall   4096 Nov 27 11:52 chgip
    drwx------  4 oracle oinstall   4096 Nov 27 11:52 assistants
    drwx------  4 oracle oinstall   4096 Nov 27 11:52 owm
    drwx------  5 oracle oinstall   4096 Nov 27 11:52 soap
    drwx------  9 oracle oinstall   4096 Nov 27 11:52 ldap
    drwx------  6 oracle oinstall   4096 Nov 27 11:52 Apache
    drwx------ 11 oracle oinstall   4096 Nov 27 11:52 network
    drwx------  2 oracle oinstall   4096 Nov 27 11:52 deconfig
    drwx------  7 oracle oinstall   4096 Nov 27 11:52 dcm
    -rwx------  1 oracle oinstall   9271 Nov 27 12:03 root.sh.old
    -rwx------  1 oracle oinstall   1153 Nov 27 12:03 allroot.sh
    drwxrwx---  4 oracle oinstall   4096 Nov 27 15:44 toplink
    drwx------  7 oracle oinstall   4096 Nov 27 15:44 oui
    drwxrwx---  4 oracle oinstall   4096 Nov 27 15:44 ocm
    drwxrwx---  2 oracle oinstall   4096 Nov 27 15:44 modules
    drwx------  7 oracle oinstall   4096 Nov 27 15:44 dsa
    drwx------ 25 oracle oinstall   4096 Nov 27 15:45 sysman
    -rwxr-xr-x  1 oracle oinstall   5248 Nov 27 15:45 root.sh.old.1
    drwx------  3 oracle oinstall   4096 Nov 27 15:45 relnotes
    drwx------ 15 oracle oinstall   4096 Nov 27 15:45 inventory
    drwx------  2 oracle oinstall   4096 Nov 27 15:45 config
    drwx------ 10 oracle oinstall   4096 Nov 27 15:45 install
    drwx------  3 oracle oinstall   4096 Nov 27 15:47 lib
    drwx------  3 oracle oinstall   4096 Nov 27 15:48 jlib
    drwxr-xr-x  3 oracle oinstall  12288 Nov 27 16:01 bin
    drwx------ 14 oracle oinstall   4096 Nov 27 16:02 ccr
    drwx------  7 oracle oinstall   4096 Nov 27 16:03 j2ee
    drwx------  4 oracle oinstall   4096 Nov 27 16:03 uix
    drwx------ 16 oracle oinstall   4096 Dec 11 16:52 webcache
    -rw-r-----  1 oracle oinstall      6 Jan 13 15:59 emctl.pid
    drwx------  7 oracle oinstall   4096 Jan 13 16:16 OPatch
    drwx------  5 oracle oinstall   4096 Jan 20 12:08 cfgtoollogs
    -rwxr-xr-x  1 oracle oinstall     10 Jan 27 15:52 root.sh
    -rw-------  1 oracle oinstall     37 Jan 27 15:52 install.platfo

  • I can't find the db infomation in the oms

    HI ALL:
    pls help me,on server A,I have installed the 10g Grid Control,including the oms ,agent and a new database,other,server B,i hava installed a database and a agent.
    my question is that,in the EM,the server A's DB infomation is displayed,but the server B's db infomation can't display only the server B's host infomation.
    execute the command,find follow:
    server A:
    OMS STATUS:
    oracle@mmDB /opt/oracle/OracleHomes/oms10g/bin$./emctl status oms
    Oracle Enterprise Manager 10g Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Oracle Management Server is Up.
    AGENT STATUS:
    oracle@mmDB /opt/oracle/OracleHomes/agent10g/bin$./emctl status agent
    Oracle Enterprise Manager 10g Release 10.2.0.1.0.
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.1.0
    OMS Version : 10.2.0.1.0
    Protocol Version : 10.2.0.0.0
    Agent Home : /opt/oracle/OracleHomes/agent10g
    Agent binaries : /opt/oracle/OracleHomes/agent10g
    Agent Process ID : 17647
    Parent Process ID : 17630
    Agent URL : https://mmDB:3872/emd/main/
    Repository URL : https://mmDB:1159/em/upload
    Started at : 2006-10-12 11:08:14
    Started by user : oracle
    Last Reload : 2006-10-12 11:08:23
    Last successful upload : 2006-10-12 11:53:38
    Total Megabytes of XML files uploaded so far : 3.62
    Number of XML files pending upload : 0
    Size of XML files pending upload(MB) : 0.00
    Available disk space on upload filesystem : 74.21%
    Last successful heartbeat to OMS : 2006-10-12 11:53:22
    Agent is Running and Ready
    server B:
    AGENT STATUS:
    oracle@testdb /opt/oracle/OMS/agent10g/bin$./emctl status agent
    Oracle Enterprise Manager 10g Release 10.2.0.1.0.
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.1.0
    OMS Version : 10.2.0.1.0
    Protocol Version : 10.2.0.0.0
    Agent Home : /opt/oracle/OMS/agent10g
    Agent binaries : /opt/oracle/OMS/agent10g
    Agent Process ID : 30359
    Parent Process ID : 30339
    Agent URL : https://testdb:3872/emd/main/
    Repository URL : https://mmDB:1159/em/upload
    Started at : 2006-10-12 10:52:42
    Started by user : oracle
    Last Reload : 2006-10-12 10:52:42
    Last successful upload : 2006-10-12 10:53:28
    Total Megabytes of XML files uploaded so far : 2.06
    Number of XML files pending upload : 0
    Size of XML files pending upload(MB) : 0.00
    Available disk space on upload filesystem : 80.27%
    Last successful heartbeat to OMS : 2006-10-12 10:53:44
    oracle@testdb /opt/oracle/OMS/agent10g/bin$./emctl upload
    Oracle Enterprise Manager 10g Release 10.2.0.1.0.
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    ALL IS fine.but in the em,i can't find the db infomation of the server B

    on the server B,the db version is 9206,
    on the server A,the db version is 10.2.0.1
    check the emagent.trc file,find follows:
    2006-10-12 15:59:25 Thread-16384 ERROR : sched_setaffinity failed, errno 22
    2006-10-12 15:59:25 Thread-16384 ERROR util.files: ERROR: nmeufis_new: failed in lfiopn on file: /opt/oracle/Or
    acleHomes/agent10g/sysman/emd/agntstmp.txt. error = 2 (No such file or directory)
    2006-10-12 15:59:25 Thread-16384 WARN main: clear collection state due to OMS_version difference
    2006-10-12 15:59:25 Thread-16384 WARN command: Job Subsystem Timeout set at 600 seconds
    2006-10-12 15:59:25 Thread-16384 WARN upload: Upload manager has no Failure script: disabled
    2006-10-12 15:59:25 Thread-16384 WARN upload: Recovering left over xml files in upload directory
    2006-10-12 15:59:25 Thread-16384 WARN upload: Recovered 0 left over xml files in upload directory
    2006-10-12 15:59:25 Thread-16384 ERROR upload: Error merging files
    2006-10-12 15:59:25 Thread-16384 ERROR upload: Error merging files
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_user_count can't define table_name: mai
    l_imap_usercount
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_user_count does not have any data columns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_db_session_count can't define table_nam
    e: umsg_imap_dbconnections
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_db_session_count does not have any data colum
    ns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_socket_count can't define table_name: u
    msg_imap_socketcount
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_socket_count does not have any data columns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_connections can't define table_name: ma
    il_imap_connections
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_connections_lost can't define table_nam
    e: umsg_imap_connections_lost
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_connections_lost does not have any data colum
    ns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_connections_timeout can't define table_
    name: umsg_imap_connections_timeout
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_connections_timeout does not have any data co
    lumns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_connections_total can't define table_na
    me: umsg_imap_connections_count
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_connections_total does not have any data colu
    mns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_debug_user_list can't define table_name
    : mail_pop_users_list
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_ds_metrics can't define table_name: mai
    l_imap_functions
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_network can't define table_name: mail_i
    map_network
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_network_receive_bytes can't define tabl
    e_name: umsg_imap_network_receive
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_network_receive_bytes does not have any data
    columns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_network_transmit_bytes can't define tab
    le_name: umsg_imap_network_transmit
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Metric umsg_imap_network_transmit_bytes does not have any data
    columns
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_command_counts can't define table_name:
    mail_imap_commandcount
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_imap_protocol_metrics can't define table_nam
    e: umsg_imap_frequencytimes
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_sps_metrics can't define table_name: mail_im
    ap_sps
    2006-10-12 15:59:25 Thread-16384 WARN metadata: TABLE metric umsg_uptime can't define table_name: mail_imap_up
    time
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Name FileSystems has already been used
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <GetTable> can't be added to <ExecutionDescriptor>, it will b
    e freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: Name FileSystems has already been used
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <GetTable> can't be added to <ExecutionDescriptor>, it will b
    e freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric DataSources mean that it i
    s not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: DataSources: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric NativeDataSources mean tha
    t it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: NativeDataSources: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric ManagedDataSources mean th
    at it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: ManagedDataSources: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric ConnectionPools mean that
    it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: ConnectionPools: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric DataSourcesTopo mean that
    it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: DataSourcesTopo: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric NativeDataSourcesTopo mean
    that it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: NativeDataSourcesTopo: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric ConnectionPoolsTopo mean t
    hat it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: ConnectionPoolsTopo: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric AppRoutingIds mean that it
    is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: AppRoutingIds: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric WebModuleRoutingFlags mean
    that it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: WebModuleRoutingFlags: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric Oc4jRoutingMode mean that
    it is not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: Oc4jRoutingMode: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN metadata: The ValidMidTierVersions for metric RoutingIds mean that it is
    not supported for CORE version 10.2.0.0.0. The metric will be discarded.
    2006-10-12 15:59:25 Thread-16384 ERROR metadata: RoutingIds: TableMetric Validation failed
    2006-10-12 15:59:25 Thread-16384 WARN emSDK.xml: <Metric> can't be added to <TargetMetadata>, it will be freed
    2006-10-12 15:59:25 Thread-16384 WARN engine: File=file:/opt/oracle/OracleHomes/agent10g/sysman/admin/metadata
    /oracle_ovf_ivr.xml,line=398: <InstanceProperty> is not valid element, will be ignored
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric osm_diskGroupPolicies does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric uptime can't define table_name: mail_pop_uptime
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric debug_usercount can't define table_name: mail_pop
    userslist
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections can't define table_name: mail_pop_con
    nections
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric commandcount can't define table_name: mail_pop_co
    mmandcount
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric spsstats can't define table_name: mail_pop_sps
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric usercount can't define table_name: mail_pop_userc
    ount
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric usercount does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric socketcount can't define table_name: umsg_pop_soc
    ketcount
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric socketcount does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric frequency_times can't define table_name: umsg_pop
    _frequencytimes
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric userlist can't define table_name: umsg_pop_userli
    st
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric userlist does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric dbconnections can't define table_name: umsg_pop_d
    bconnections
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric dbconnections does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_lost can't define table_name: umsg_po
    p_connections_lost
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_lost does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_timeout can't define table_name: umsg
    popconnections_timeout
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_timeout does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_total can't define table_name: umsg_p
    op_connections_count
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_total does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric network_transmit can't define table_name: umsg_po
    p_network_transmit
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric network_transmit does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric network_receive can't define table_name: umsg_pop
    networkreceive
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric network_receive does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric Function calls can't define table_name: mail_pop_
    functions
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric uptime can't define table_name: mail_imap_health
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric uptime does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpi_health
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections can't define table_name: mail_mta_con
    nections
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_current can't define table_name: smtp
    in_connections_current
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_current does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transm
    it
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric receive can't define table_name: mail_mta_receive
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_received can't define table_name: umsg_s
    mtpin_messages_received
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric messages_received does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_sm
    tpin_messages_avgsize
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name:
    umsg_smtpin_messages_avgtime
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric transmission_response can't define table_name: um
    sg_smtpin_transmission_reponse
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric network_connection_total can't define table_name:
    umsg_smtpin_network_connection_total
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric network_connection_total does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric network_receive_bytes can't define table_name: um
    sg_smtpin_network_receive_bytes
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric network_receive_bytes does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_receive_dl can't define table_name: umsg
    smtpinmessage_receive_dl
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric messages_receive_dl does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_deferred can't define table_name: umsg_s
    mtpin_messages_deferred
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric messages_deferred does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgreceip can't define table_name: umsg_
    smtpin_message_avgreceip
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric messages_avgreceip does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpo_health
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections can't define table_name: mail_mta_con
    nections
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transm
    it
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_current can't define table_name: umsg
    smtpoutconnections_current
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_current does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_transmitted can't define table_name: ums
    g_smtpout_messages_transmitted
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric messages_transmitted does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_sm
    tpout_messages_avgsize
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name:
    umsg_smtpout_messages_avgtime
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgdeliverytime_local can't define table
    name: umsgsmtpout_messages_avgtime_local
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgdeliverytime_remote can't define tabl
    e_name: umsg_smtpout_messages_avgtime_remote
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric messages_avgrelay_time can't define table_name: u
    msg_smtpout_messages_avgtime_relay
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric delivery_performance can't define table_name: ums
    g_smtpout_delivery_performance
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric relay_performance can't define table_name: umsg_s
    mtpout_messages_avgtime_relay
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric relay_performance does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_outbound can't define table_name: ums
    g_smtpout_connections_outbound
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_outbound does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_outbound_local can't define table_nam
    e: umsg_smtpout_connections_outbound_local
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_outbound_local does not have any data colum
    ns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric connections_outbound_remote can't define table_na
    me: umsg_smtpout_connections_outbound_remote
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric connections_outbound_remote does not have any data colu
    mns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric transmitted_bytes can't define table_name: umsg_s
    mtpout_transmitted_bytes
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric transmitted_bytes does not have any data columns
    2006-10-12 15:59:26 Thread-16384 WARN metadata: TABLE metric transmission_rate can't define table_name: umsg_s
    mtpout_transmission_rate
    2006-10-12 15:59:26 Thread-16384 WARN metadata: Metric transmission_rate does not have any data columns
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for testdb:3872
    2006-10-12 15:59:26 Thread-114692 DEBUG TargetManager: Computing dynamic properties for {testdb:3872, oracle_em
    d}
    2006-10-12 15:59:26 Thread-114692 DEBUG TargetManager: Computing dynamic property VersionAndLocation of oracle_
    emd,testdb:3872
    2006-10-12 15:59:26 Thread-114692 DEBUG TargetManager: Done with dynamic property evaluation for {testdb:3872,o
    racle_emd}
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmedt_waitDynPropertyFinish for testdb:3872, ret=0
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent> Ente
    ring function
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: for
    target {host:testdb} assocName:cluster_instance, assocType:cluster
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Exa
    mining target {oracle_emd:testdb:3872} for inclusion as assoc instance for {host:testdb}
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: ass
    ocTgType cluster and type oracle_emd do not match ignoring
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Exa
    mining target {host:testdb} for inclusion as assoc instance for {host:testdb}
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: ass
    ocTgType cluster and type host do not match ignoring
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for testdb
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic properties for {testdb, host}
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic property from_cluster of host,testdb
    2006-10-12 15:59:26 Thread-131076 WARN TargetManager: Query returned 0 rows (only one expected) for the dynami
    c property from_cluster
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic property getCRSVCategory of host,testd
    b
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic property Config of host,testdb
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic property HardwareInfo of host,testdb
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Computing dynamic property esa_dyn_prop of host,testdb
    2006-10-12 15:59:26 Thread-131076 DEBUG TargetManager: Done with dynamic property evaluation for {testdb,host}
    2006-10-12 15:59:26 Thread-16384 DEBUG TargetManager: nmedt_waitDynPropertyFinish for testdb, ret=0
    2006-10-12 15:59:26 Thread-16384 INFO TargetManager: save to targets.xml success
    2006-10-12 15:59:26 Thread-16384 WARN TargetManager: Regenerating all Metadata
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: getTypeAndNameForHostTarget found host, testdb
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: getTypeAndNameForHostTarget found host, testdb
    2006-10-12 15:59:27 Thread-16384 INFO TargetManager: TargetManager initialized
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: In getTypeAndNameForHostTarget
    2006-10-12 15:59:27 Thread-16384 DEBUG TargetManager: getTypeAndNameForHostTarget found host, testdb
    2006-10-12 15:59:27 Thread-16384 WARN collector: Regenerating all DefaultColls
    2006-10-12 15:59:27 Thread-16384 ERROR collector: nmecs_validateStateFile(): state file /opt/oracle/OracleHomes
    /agent10g/sysman/emd/state/snapshot invalid, backing up and wiping state
    2006-10-12 15:59:27 Thread-16384 ERROR collector: Collector state files cleaned, severity will be resent
    2006-10-12 15:59:27 Thread-16384 INFO TargetManager: save to targets.xml success
    2006-10-12 15:59:27 Thread-163847 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds or earl
    ier.

  • 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(12c) does not start

    OMS Version : 12 cloud control
    1. oms shutdown
    emctl stop oms
    2. installed Patch(13346924)
    3. oms start
    emctl start oms
    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
    Starting WebTier...
    WebTier Successfully Started
    Starting Oracle Management Server...
    Oracle Management Server is not functioning because of the following reason:
    A recent plug-in upgrade operation has failed. Follow these steps to recover:
    1. Restore/recover the repository database (For example from a backup)
    2. Start the Management server using 'emctl start oms' command. Oracle Management Server cannot be started without recovering the repository database.
    Execute 'emctl status oms -details' to get further information about this failure. After identifying and fixing the issues reported in log files you can retry plug-in upgrade.
    For more details, Refer to 'Plug-in Deployment' section in the Enterprise Manager Advanced Configuration Guide.
    so i patch was rollback,... but ems do not start
    EMS do not connected > connect message is "Backend WLS or EM application seems to be down"
    backup file not exists...... OMS is reinstall?
    have another solution?
    Edited by: Taerang on 2012. 3. 4 오전 4:12

    No Upgrade for bundle patch #1
    installed one-off patch(13346924) ====> oms problem
    i env is
    em12c(not bundle patch 1) + Database Plugin Upgrade(http://download.oracle.com/otn/nt/oem/12101/12.1.0.1.0_oracle.sysman.db_2000_20111221.opar)

  • Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방

    Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방법
    =========================================================================
    다음은 Grid Control 을 설치한 이후에 node를 관리해 오다가 새로운 관리할 Target node를
    추가한 이후에 Grid Control 이 있는 node의 OMS와 새로 추가한 node의 Agent가 HeartBeat 통신
    실패 시에 해결책을 소개하고 있습니다.
    Problem Description
    Grid Control 에서 새로운 node를 추가한 다음에 그 새로운 node 에서
    emctl status agent 명령 수행 시 다음과 같은 에러가 발생합니다.
    Environment :
    mesdev01 : 새로 추가한 Agent가 있는 node명
    mesdev02 : 'Central Grid Agent' 존재 & 'Repository database가 존재하는 node'
    새로 추가한 node에서 아래와 같이 emctl status agent 명령을 수행합니다.
    그런데, OMS에 대한 HeartBeat fail 이 발생했음을 알 수 있습니다.
    [mesdev01:/oracle/app/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 Version : 10.2.0.3.0
    OMS Version : 10.2.0.3.0
    Proto Version : 10.2.0.2.0
    Agent Home : /oracle/app/oracle/product/agent10g
    Agent binaries : /oracle/app/oracle/product/agent10g
    Agent Process ID : 10526
    Parent Process ID : 10511
    Agent URL : http://mesdev01:3872/emd/main/
    Repository URL : http://mesdev02:4889/em/upload/
    Started at : 2007-12-28 10:36:59
    Started by user : oracle
    Last Reload : 2007-12-28 10:36:59
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 287
    Size of XML files pending upload(MB) : 26.40
    Available disk space on upload filesystem : 40.44%
    Last attempted heartbeat to OMS : 2007-12-28 14:13:36
    Last successful heartbeat to OMS : unknown <===
    여기서 주목할 만한 에러는 Last successful heartbeat to OMS 체크 시 status가
    unknown 으로 보인다는 것입니다.
    에러 증상
    emctl status agent 수행 시 Last successful heartbeat to OMS : unknown
    또는 agent 에서 OMS의 Status를 알 수 없다는 아래의 에러가 보이는 경우임.
    Note: "The OMS status is Unknown"
    Explanation
    이러한 에러는 주로 agent가 node에 새로(newly) install 된 경우 발생합니다.
    원래 communication 이 정상적으로 보인다면 다음과 같이 수행 결과가 나와야 합니다.
    다음은 Repository database가 존재하는 mesdev02 node에서 emctl status agent를 수행한 결과
    성공적으로 보이는 결과입니다.
    mesdev02:/u01/app/oracle/OracleHomes/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
    Proto Version : 10.2.0.2.0
    Agent Home : /u01/app/oracle/OracleHomes/agent10g
    Agent binaries : /u01/app/oracle/OracleHomes/agent10g
    Agent Process ID : 29307
    Parent Process ID : 29300
    Agent URL : https://mesdev02:3872/emd/main/
    Repository URL : https://mesdev02:1159/em/upload
    Started at : 2007-12-27 11:29:22
    Started by user : oracle
    Last Reload : 2007-12-27 17:57:18
    Last successful upload : 2007-12-28 15:02:09
    Total Megabytes of XML files uploaded so far : 48.78
    Number of XML files pending upload : 0
    Size of XML files pending upload(MB) : 0.00
    Available disk space on upload filesystem : 38.29%
    Last successful heartbeat to OMS : 2007-12-28 15:02:59 <====
    Agent is Running and Ready
    원인
    이 에러가 발생하는 원인은 새로 추가한 database의 Agent process가 GRID Control 이
    install된 main server의 OMS와 연결되지 않기 때문인데, 이렇게 새로운 node를 추가한 이후에
    수행해줘야 할 절차가 있습니다.
    OMS_HOME/sysman/log 의 secure.log 를 확인해 보면 OMS is "secure locked" 라는 에러가 보입니다.
    The OMS is "secure locked", then the agent also needs to be secure.
    [ 사전 check 사항 ]
    1. 두 node 모두 DNS server에 등록되어 있는지 확인한다.
    2. 두 node 모두 쌍방 간에 /etc/hosts file에 서로의 ip address와 hostname을 넣어준다.
    위 두가지 check 사항이 충족된 경우에도 발생한다면 새로 추가한 node 쪽에서 자신의 정보를
    OMS(즉, Repository node) 에게 정보를 upload하지 않았기 때문입니다.
    Upload를 하는 방법은 간단하게 아래와 같은 emctl upload agent 라는 명령으로 가능합니다.
    emctl upload agent
    Upload를 하게 될 때 그 정보는 XML 형태로 중앙 Repository에 저장됩니다.
    Solution Description
    아래 절차 중에 1번만 Grid Control이 설치된 OMS server에서 수행을 하고,
    2번~7번까지는 새로 추가한 Agent node에서 수행합니다.
    1. On oms server: (Grid Control 이 설치된 서버에서 수행)
    <OMS_HOME>/bin/emctl status oms -secure
    OMS node인 mesdev02 node에서 우선 emctl status oms -secure 를 수행합니다.
    mesdev02:/u01/app/oracle$$OMS_HOME/bin/emctl status oms -secure
    Oracle Enterprise Manager 10g Release 3 Grid Control
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Checking the security status of the OMS at location set in /u01/app/oracle/OracleHomes/oms10g/sysman/config/emoms.properties... Done.
    OMS is secure on HTTPS Port 1159
    2. Stop Agent: Agent를 설치한 node에서 수행합니다.
    <AGENT_HOME>/bin/emctl stop agent
    [mesdev01:/oracle/app/oracle/product/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.
    3. Verify no residue emagent processes running:
    이와 같은 명령으로 남아 있는 emagent process가 있는지 확인합니다.
    ps -ef|grep emagent
    [mesdev01:/oracle/app/oracle/product/agent10g/bin]ps -ef|grep emagent
    oracle 4353 3125 0 16:19:34 pts/tb 0:00 grep emagent
    4. If running secure please resecure agent on :
    <AGENT_HOME>/bin/emctl secure agent
    emctl secure agent 를 수행하는 목적은 모든 agent에 대해서 secure communication 을
    하기 위해 필요합니다.
    [ 주의사항 ]
    emctl secure agent 명령은 Grid Control installation 과정에서
    --> 'Specify Security Options' 단계에서
    --> Management Service Security 항목에서
    --> OMS와 함께 Secure Communication을 하고자 하는 agent에 password 설정을 하는데,
    --> Require Secure Communication for all agents 를 check 표시하였다면
    install 이후에 아래와 같이 emctl secure agent 명령을 수행하여야 합니다.
    (기본적으로 Require Secure Communication for all agents는 enable되어야 함).
    [mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl secure agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.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... Done.
    Requesting an Oracle Wallet and Agent Key from the OMS... Done.
    Check if HTTPS Upload URL is accessible from the agent... Done.
    Configuring Agent for HTTPS in CENTRAL_AGENT mode... Done.
    EMD_URL set in /oracle/app/oracle/product/agent10g/sysman/config/emd.properties
    Securing agent... Successful.
    5. 4번 단계가 정상적으로 완료되면 이제 Agent를 기동합니다.
    Start Agent
    <AGENT_HOME>/bin/emctl start agent
    [mesdev01:/oracle/app/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 ................................. started but not ready.
    6. Then verify upload works
    <AGENT_HOME>/bin/emctl upload agent
    [mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl upload agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD upload error: Upload timedout before completion
    ==> timedout 메시지는 warning으로 보이며, 운영에는 지장이 없습니다.
    7. 다시 확인 차 emctl status agent 명령을 수행해 봅니다.
    Then run status of agent
    <AGENT_HOME>/bin/emctl status agent
    [mesdev01:/oracle/app/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 Version : 10.2.0.3.0
    OMS Version : 10.2.0.3.0
    Proto Version : 10.2.0.2.0
    Agent Home : /oracle/app/oracle/product/agent10g
    Agent binaries : /oracle/app/oracle/product/agent10g
    Agent Process ID : 4618
    Parent Process ID : 4609
    Agent URL : https://mesdev01:3872/emd/main/
    Repository URL : https://mesdev02:1159/em/upload
    Started at : 2008-01-02 16:21:03
    Started by user : oracle
    Last Reload : 2008-01-02 16:21:03
    Last successful upload : 2008-01-02 16:25:37
    Total Megabytes of XML files uploaded so far : 54.28
    Number of XML files pending upload : 40
    Size of XML files pending upload(MB) : 0.97
    Available disk space on upload filesystem : 37.22%
    Collection Status : Disabled by Upload Manager
    Last successful heartbeat to OMS : 2008-01-02 16:24:49 <== success!
    Agent is Running and Ready
    [mesdev01:/oracle/app/oracle/product/agent10g/bin]
    8. 만약 Last successful heartbeat to OMS 에 위와 같은 success로 보이지 않으면
    step 1부터 7까지 수행된 모든 output 을 수집하여 문의를 합니다.
    9. 그리고, debugging을 위해 다음의 log 화일들을 보관하시기 바랍니다.
    <OMS_HOME>/sysman/log
    <OMS_HOME>/sysman/log 의 secure.log가 특히 중요합니다.
    <AGENT_HOME>/sysman/log
    References
    Note 458033.1
    Title:Problem: Agent Upload Fails: OMS Is Locked and Agent not Secured

  • 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

Maybe you are looking for

  • Open PO Quantity

    Hi From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. there is a routine for the PO open quantity 0BO_QTY as follows: RESULT = COMM_STRUCTURE-cpquaou * COMM_STRUCTURE-numerator /            COMM_STRUCTURE-denomintr. cpquaou is m

  • How to search char in a string

    hi, i am new to JSP. i have a string, for example an address "Frauenstrasse 10", i want to split it into street name "Frauenstrasse" and house number "10". but i don't know the syntax to process String. can anyone help? thanks!

  • ATV2 and Airplay for videos???

    I bought the ATV2 and when I try to stream a music from Itunes 10 by clicking the airplay icon on this program, everything is ok. But when I do the same thing with my videos from Itunes, it doesn't work at all. Is anything wrong or is it just like th

  • Credtit Availble in Tax payment Wizard

    Hi All I am trying to get the total Credit available for each and every CENVAT Components for the month in the report... I checked the table TPW6 but it lists all the Journal Entries from which the credit payable can be calculated.. Is there any way

  • How can I stretch the homepage so it fills my whole monitor

    When I bring your homepage up it does not cover my monitor screen fully. How can I "stretch" it?? Also, your onscreen instructions on how to sort my favorites alphabetically does not seem to work. How can I get them sorted??