Is OMS required?

OS: W2K server.
I've decided to go 2 tier approach so, my IFS and DB are running in the same machine which is server and domain controller. I hope I'm not makning any mistake on the terminology here. Eventually my DB up and IFS runs, but I cant discover it in the OEM, because I can't see "discover" comment any where in the pop up menus. On the otherhand, document says to run ifsomssetup, but I can't say at this moment do I need OMS for 2 tier.
The other question is, without trying to discover IFS in OEM; I followed the steps in "Validate basic operation" and tried to acces web page through explorer but page didn't come up. Is any body can guess what could be the mistake?
Last question: Do I need IIS and relativly SMTP. FTP or WWW Publisher running automatically when W2K up. As far as I know IFS introduce new web server with no connection to IIS, any idea if I should kill the IIS while running the IFS.
thanks in advance.

I stopped the IIS and FTP services from automatically running on the server that is running iFS. This way there will not be a conflict with the ports.
For confirming basic operation, make sure that you do the following (at least it works for me) from the iFS bin directory.
//I usually wait about 20 seconds between each step
ifsjservctl start
start ifslaunchdc
start ifslaunchnode
ifsstartdomain
After everything is running in my environment I've got to wait at least a minute (sometimes more) before iFS will accept a connection. (Monitor the CPU utilization until it stabilizes back to normal)
Test with IE at http://yourserver/ifs/files/ (don't forget the trailing /
For Ent Mgr after I ran the ifssomsetup iFS showed up in Ent Mgr application. It works well, but I can not get jobs to work appropriately in Ent Mgr. It always fails authentication.

Similar Messages

  • EM12c Install on VmWare Machine

    Hello all.
    My name is Joe. New here. We are looking at the requirements for EM12c. We have VMWare ESX. We have installed the EM12c on the test VM. We are using the same VM as an agent only to test alerts and incidents. Problem we are having is that the EM12c keeps crashing. CPU is at 100% sometimes. We have 100 Gigs space allocated for the VM. At the moment is 99% full? Also 15gigs of ram allocated.
    I guess the question is (I wrote this to one of our analysts)
    What we came across is that the VM has 100 GB disk space and almost all of it is being used. Problem is that we are missing around 12 Gigs somewhere!! The hard drive has 97.9 Gigs used but on the properties of the complete C drive (all folders hidden as well) it is only 85 Gigs or so. ?????????? Where are the other 12 Gigs?
    Also, the memory allocated for this VM is 15GB of Ram. What is interesting is the CPU Requirements. The OMS requires 2 CPU cores, which we have for this VM, but the repository requires also 2 CPU cores. So does this mean we will need 4 CPU cores if the OMS and the repository are on the same machine or we need 2 VM's. One for each? Maybe this is why the CPU was at 100%?
    We are a small business (as outlined in the EM install).
    Any help would be appreciated!
    Thanks
    Joe

    The missing 12 GB will come from the swap file I think. If you run the server using Windows you won't see this file by default.
    If you look at the hardware requirements ( http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_hw.htm )
    you will see you need about 20 GB for the OMS and about 50 GB for the repository. The OS needs some GB and the database is probably running in archive mode so the archives are also stored on disk. Conclusion: 100GB is not too much to have as disk space. Ask the Administrator to increase the disk to 200GB
    Eric

  • Patching 11.1.1.6.2: Opatch Failed error code 39

    Hi everyone,
    i am just patching OBI EE 11.1.1.6.0 to 11.1.1.6.2.
    While applying opatch for the paricular patches i got an error with this patch: *14228505*
    The logfile says:
    [21.01.2013 11:59:29] OPatch invoked as follows: 'apply '
    [21.01.2013 11:59:29] Oracle Home : c:\oracle\middleware\Oracle_BI1
    Zentrales Bestandsverzeichnis: C:\Program Files\Oracle\Inventory
    von : n/a
    OPatch-Version : 11.1.0.9.0
    OUI-Version : 11.1.0.9.0
    OUI-Speicherort : c:\oracle\middleware\Oracle_BI1\oui
    Speicherort von Log-Datei : c:\oracle\middleware\Oracle_BI1\cfgtoollogs\opatch\14228505_Jan_21_2013_11_59_28\apply2013-01-21_11-59-27AM_1.log
    [21.01.2013 11:59:29] Patch history file: c:\oracle\middleware\Oracle_BI1\cfgtoollogs\opatch\opatch_history.txt
    [21.01.2013 11:59:29] OPatch detects the Middleware Home as "C:\oracle\middleware"
    [21.01.2013 11:59:33] Starting ApplySession on Mon Jan 21 11:59:33 CET 2013
    [21.01.2013 11:59:33] OPatch will do the following:
    [Oracle Home discovery] : Configure and Validate Oracle Home info.
    [Prerequisite for apply] : Invoke prerequisites to see if patch can be applied.
    [Patch conflict detection for apply patch] : Check if any conflict with already installed patches in Oracle Home.
    [21.01.2013 11:59:33] --------------------- Oracle Home discovery ---------------------
    [21.01.2013 11:59:33] ApplySession Interim-Patch '14228505' wird für OH 'c:\oracle\middleware\Oracle_BI1' angewendet
    [21.01.2013 11:59:33] Starting to apply patch to local system at Mon Jan 21 11:59:33 CET 2013
    [21.01.2013 11:59:36] Start the Apply initScript at Mon Jan 21 11:59:36 CET 2013
    [21.01.2013 11:59:36] Finish the Apply initScript at Mon Jan 21 11:59:36 CET 2013
    [21.01.2013 11:59:36] --------------------- Prerequisite for apply ---------------------
    [21.01.2013 11:59:36] Running prerequisite checks...
    [21.01.2013 11:59:36] Patch "14228505" is ignored as it is not a "Fusion Applications patch".
    [21.01.2013 11:59:36] Check if patch "14228505" is a no-op patch.
    [21.01.2013 11:59:36] None of the selected patches are no-op. patches..
    [21.01.2013 11:59:38] Space Needed : 4221147894
    [21.01.2013 11:59:38] Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
    The details are:
    Patch ( 14228505 ) is not applicable on current platform.
    Platform ID needed is : 912
    Platform IDs supported by patch are: 233
    [21.01.2013 11:59:42] [ Error during Prerequisite for apply phase ] Detail: OUI-67074:OPatch während Prüfung auf Voraussetzungen nicht erfolgreich: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
    [21.01.2013 11:59:42] System intakt, OPatch versucht nicht, das System zurückzuschreiben
    [21.01.2013 11:59:42] Finishing ApplySession at Mon Jan 21 11:59:42 CET 2013
    [21.01.2013 11:59:42] Total time spent waiting for user-input is 0 seconds. Finish at Mon Jan 21 11:59:42 CET 2013
    [21.01.2013 11:59:42] Stack-Beschreibung: oracle.opatch.PrereqFailedException: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
    [21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatchSessionHelper.runApplyPrereqs(OPatchSessionHelper.java:5939)
    [21.01.2013 11:59:42] StackTrace: oracle.opatch.ApplySession.processLocal(ApplySession.java:3780)
    [21.01.2013 11:59:42] StackTrace: oracle.opatch.ApplySession.process(ApplySession.java:5824)
    [21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:1871)
    [21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatch.main(OPatch.java:573)
    CMD says:
    Recommended actions: This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.
    What i commandedbefore:
    set ORACLE_HOME=D:\Oracle\Middleware\Oracle_BI1
    set PATH=%ORACLE_HOME%\bin;%PATH%
    set JAVA_HOME=%ORACLE_HOME%\jdk
    set PATH=%JAVA_HOME%\bin;%PATH%
    set PATH=%ORACLE_HOME%\OPatch;%PATH%
    The following patches already succeeded: 14226980, 13960955 and 14226993.
    Does anyone of you has an idea? It's really important!
    Thank you,
    Alex

    I ran into this problem and this is how I solved it. I had OEM Grid Control installed with the database and OMS on the same server. opatch always worked when using the database Oracle Home. Our company moved the database to another system, so I tried using the OMS Oracle Home and got the error. The OMS Oracle Home is a 10.1.0.5 version. I believe I installed the 10.2 Opatch in the directory with a unzip -o option.
    I started clean. I renamed the old OPatch and reinstalled the 6880880 patch for the required version. OMS requires the 10.2 version. The problem went away. It had nothing to do with the Java version

  • Streams setup Wizard

    Using Streams setup Wizard, I tried to configure streams for replication requirements.
    And at the final stage of this wizard , I got this following error:
    " You do not have Oracle Management Server(OMS) Setup "
    Can anybody help me in resolving this error..
    Srinivas Jaltaru
    ( [email protected] )

    The OEM console can be run either in STANDALONE mode or with an Oracle Management Server(OMS).
    The streams wizard behavior varies depending upon the mode in which the OEM console is operating.
    If you have successfully connected the console in OMS mode, then I would suspect that there is a problem with the preferred credentials configuration.
    Have you looked at the Oracle9i by Example series that includes a section on Oracle Streams? The example includes directions on the configuration of the OMS required for the Streams wizard to run properly as well as a patch required for the Streams wizard. Here is a pointer to the URL for the Oracle9i By Example website.

  • What is the alternative of F5 BIG-IP LTM Load Balancer for OEM 12c

    We want to implement service load balance, however oracle recommended
    F5 BIG-IP LTM Load Balancer for OEM 12c
    How much it is cost? and is there any free alternative we can use which supported by Oracle?
    Thanks

    Apart from F5, Cisco is another SLB vendor. I am not sure about any free alternative though.
    Note that regardless what SLB that you pick, it should meet the requirements documented in section 29.3.2.2 of the EM12c Release 3 Administrator's Guide:
    The SLB must provide support for multiple virtual server ports. Enterprise Manager typically requires that up to 4 ports are configured on the SLB (Secure Upload, Agent Registration, Secure Console, Unsecure Console)
    Support for persistence. HTTP and HTTPS traffic between the browser and the OMS requires persistence
    Support for application monitoring. The SLB must be capable of monitoring the health of the OMSs and detecting failures, so that requests will not be routed to OMSs that are not availa
    Regards,
    - Loc

  • Linux and OEM

    Ok, I couldnt run OEM on linux (couldnt find any actually), so I installed one on windows 98 and used that to access the DB on my linux box. The problem is I can only run DBA-Studio (and access my DB from Linux) and cant run Enterprise Manager cause it asks me for a management server which I cant find (nor the installation). Is there any other way to run OEM and access my database?

    you need to install Oracle Management Server
    if you want to use some of the features of
    OEM 2.x (SQL Analyzer, for example), and
    you need to enable the intelligent agent and data gatherer on your database, also.
    Afaik, OMS requires an NT machine for the server, only client-side tools can be installed on WinXX.
    Anyway, some the tools (Storage manager, schema manager, etc) can be used connecting
    directly to the database.
    The version 2.0.4 found at technet is beta (alpha?) software, use 2.1 version found at same site, but unfortunatelly this version is buggy, and you need a 20M patch found at metalink to use some of the tools (SQL Analyzer IIRC)
    Saludos
    -- Marcos.
    null

  • GRID Control Server (OMS) - what services are required?

    What services are required (and what is the startup order) on the Windows 2003 GRID Control Server (OMS). The target database is 10g on Solaris.

    Hi.
    I assume that you have three folders in the oms installation folder, called oms, agent and db.
    You should first start the grid database on the 2003 server along with the listener from the db folder.
    Than you should install the application server processes by running:
    opmnctl startall from the oms\opmn\bin - folder.
    Than you should start the agent by runnint agent\bin\emctl start agent
    You should further start the agent on the Solaris node and verify the upload to oms:
    $ORACLE_HOME/bin/emctl start agent
    $ORACLE_HOME/bin/emctl status agent
    Good luck
    rgds
    Kjell

  • Memory consumption on oms/agent

    Hello all, I had posted this at the wrong place. I was wondering if someone can shed some light on this....i did get one reply back saying look at the metalink doc...which i did...but dose not seem to be my issue...
    Re: agent taking too much memory...
    Also, how dose OMS runs ??? dose OMS starts a java process ??? why is the java process conusing so much memory ?
    if i grep for the java process....i get the below(system was restarted yesterday, thats why diff pid)...
    $ ps -ef|grep 29301
    oracle 11192 24846 0 08:42:51 pts/1 0:00 grep 29301
    oracle 29301 29284 0 14:19:40 ? 27:53 /opt/java6/bin/IA64W/java -client -Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:CompileThreshold=8000 -XX:PermSize=128m -Dweblogi
    $ ps -ef|grep 29120
    oracle 29120 29103 0 14:18:41 ? 12:41 /opt/java6/bin/IA64W/java -client -Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:CompileThreshold=8000 -XX:PermSize=128m -Dweblogi
    oracle 11804 24846 0 08:45:10 pts/1 0:00 grep 29120
    $
    why do i have 2 java things, and looks like they are running the same cmd....is that part of OMS or ???

    I assume that your are using GridControl 11g?
    Why are there java-processes? Because that's how the architecture of GridControl was build :-)
    And as a matter of fact java-processes are usually memory and cpu-consuming processes. When checking the requirements for GC you will figure out that you will need a certain amount of cpu and ram to keep that thing running...
    Please check the documentation "Enterprise Manager Documentation 11g Release 1 (11.1)" which can be found under http://download.oracle.com/docs/cd/E11857_01/index.htm for a detailed description of the architecure

  • Questions on the Hardware requirement mention in the 12c installation guide

    Hello experts,
    I have a confusion on the Hardware requirements mentioned in the 12c installation guide where they mentioned as below.
    RAM with ADP1, JVMD2 8 GB 12 GB 20 GB
    1 ADP Manager is Application Dependency and Performance
    2 JVMD is JVM Diagnostics
    Question 1: what does this RAM with ADP or JVMD mean. is it just the additional RAM space required in the server or does is that special requirement ??
    Oracle WebLogic Server JVM Heap 1.7 GB 4 GB 8 GB
    Size
    Question 2: What is this JVM Heap size ? how do we configure this in the server ??
    Thanks in Advance for your Help.

    Hi,
    #1: It means if you also want to install ADP and JVMD, the total RAM required is a small (e.g. < 1000 targets), medium (e.g. > 1000 targets and < 10000 targets), large EM deployment (e.g. > 10000 targets) is 8 GB, 12 GB, 20 GB, respectively. That is the memory requirement for an OMS host.
    #2: The heap size for the OMS java process. You can adjust the heap size by changing the -Xmx<heapsize> (see an example below) in the following file:
    <middleware_home>/gc_inst/user_projects/domains/GCDomain/bin/startEMServer.sh
    An example of OMS heap size setting of 2048 MB:
    if [ "${SERVER_NAME}" != "EMGC_ADMINSERVER" ] ; then
    USER_MEM_ARGS="-Xms256m -Xmx1740m -XX:MaxPermSize=768M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing"
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
    if [ "${PRODUCTION_MODE}" = "" ] ; then
    USER_MEM_ARGS="-Xms256m -Xmx2048m -XX:MaxPermSize=768M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -XX:CompileThreshold=8000 -XX:PermSize=128m"
    Regards,
    - Loc

  • OMS is up and running but unable to get the console page through web browser

    Hi All,
    I have a wierd issue here.  I have my OMS running successfully, but I am not able access it through HTTPS connection in web browser.  My version of OEM is 11.1.0.1
    It was working till yesterday, I am not sure what happened suddenly that its not accessible anynore.
    I can successfully start and stop my OMS and it gives the status update also .
    Also, my agents can not connect to the OMS , I see that last succesfull OMS heartbeat is not current .
    Any advice for the places to look in will help.  I tried to find the logs under sysman but nothing was there. Also , since I am able to start and stop the OMS successfully I dont have error logs.
    I believe in 11g , when we start OMS , HTTP services also start ? , still I am unable to access it.
    Let me know if any of you can you guide me through it.
    Thanks,
    Krishna.

    Looking over you configuration, it looks like you perhaps have a typo in your weblogic-ejb-jar.xml resource reference. In your weblogic-ra.xml you have defined the JNDI name to be MctEIS11/connFctryCCA but in your resource reference in the weblogic-ejb-jar.xml, you have defined the JNDI name as MctEIS11/connFctryCCA1. In applications where we have an RA and EJB clients, these JNDI names are usually defined as the same and we take advantage of the fact that the resource ref definition in the EJB descriptor makes the resource application scoped (vs. global scoped) so we will usually do application scoped JNDI lookups from within the EJB (i.e. ctx.lookup("java:comp/env/MctEIS11/connFctryCCA")). We do this because we support the WL production redeployment feature which defines as a best practice that all application references be defined at the application scope so they are self contained and not shared between multiple versions of the app that are deployed simultaneously. Your situation may not require use of application scoped lookups so I do not want to give you the impression that it is required. Just sharing our configuration in hopes that it may help you resolve your issue.

  • Install Enterprise Manager Grid Control 11R1 Failed at OMS Configuration

    Hello:
    I have installed Oracle 11g (11.2.0.1) and WebLogic Server (WLS) 10.3.6.0 and currently I am in the process of installing Enterprise Manager Grid Control 11R1 on a Linux RedHat 5.8 and it fails at OMS Configuration.
    I have read the following thread and they suggested to use WLS 10.3.2:
    Trouble installing EM GC -- installer patch 9329357 fails
    I was looking for WLS 10.3.2 in Oracle's website and I could not find it.
    Any help would be greatly appreciated.
    Here is the log regarding the error:
    The patch has more than one Archive Action but there is no Make Action.
    ApplySession applying interim patch '9367763' to OH '/dbs0/product/fmw/oms11g'
    Running prerequisite checks...
    You selected -local option, hence OPatch will patch the local system only.
    Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
    (Oracle Home = '/dbs0/product/fmw/oms11g')
    Is the local system ready for patching? y
    Y (auto-answered by -silent)
    User Responded with: Y
    Backing up files and inventory (not for auto-rollback) for the Oracle Home
    Backing up files affected by the patch '9367763' for restore. This might take a while...
    Backing up files affected by the patch '9367763' for rollback. This might take a while...
    Patching component oracle.ldap.rsf, 11.1.1.2.0...
    Updating archive file "/dbs0/product/fmw/oms11g/lib/libldapclnt11.a" with "lib/libldapclnt11.a/gslu.o"
    ApplySession adding interim patch '9367763' to inventory
    Verifying the update...
    Inventory check OK: Patch ID 9367763 is registered in Oracle Home inventory with proper meta-data.
    Files check OK: Files from Patch ID 9367763 are present in Oracle Home.
    Execution of 'sh /dbs0/product/fmw/oms11g/install/oneoffs/111010/9367763/custom/scripts/post -apply 9367763 ':
    Return Code = 0
    The local system has been patched and can be restarted.
    OPatch succeeded.
    This config tool has failed. Please re-run this config tool manually from another terminal as
    <ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/install/oneoffs/apply_NewOneoffs.pl <ORACLE_HOME> <oneoff_numbers>
    Eg: /scratch/EM/agent10g/perl/bin/perl /scratch/EM/agent10g/install/oneoffs/apply_NewOneoffs.pl /scratch/EM/agent10g 5632264,5961654
    Finished one-offs apply...
    Deleting the files...
    Finished deleting the above files...
    Configuration assistant "OMS Oneoff Patch Application" Succeeded
    Running Configuration assistant "Repository Configuration"
    Calling the EMSCHEMA MANAGER: CREATE
    Please check the Repository Configuration Assistant logs at: /dbs0/product/fmw/oms11g/sysman/log/schemamanager
    The create is completed now running the MOS
    Configuration assistant "Repository Configuration" Succeeded
    Running Configuration assistant "MDS Schema Configuration"
    Configuration assistant "MDS Schema Configuration" Succeeded
    Running Configuration assistant "OCM EM Repository Instrumentation"
    Configuration assistant "OCM EM Repository Instrumentation" Succeeded
    Running Configuration assistant "OMS Configuration"
    Executing the OMSCA command...
    Check the OMS Configuration Assistant logs at: /dbs0/product/fmw/oms11g/cfgtoollogs/omsca
    INFO: Required tool's Execution failed
    Configuration assistant "OMS Configuration" Failed
    INFO: ***Configuration Assistants Action END ***
    *** The installation was Successful, but some configuration assistants were failed or cancelled or skipped. ***

    Hello:
    For some reason after selecting the Retry button it successfully passed the Add-on OMS Side Configuration. Now I am failing at the "Agent Configuration Assistant". Here's the agent log:
    log4j:ERROR No appenders could be found for category (oracle.sysman.emas.sdk.discovery.discover.WeblogicTargetDiscovery).
    log4j:ERROR Please initialize the log4j system properly.
    Total Discovery time is :1675milliseconds.
    INFO: oracle.sysman.top.agent:AddingToTargetsXml: WLS targets
    INFO: oracle.sysman.top.agent:Adding /oracle/product/agent11g/sysman/install//oraclewls.out file to /oracle/product/agent11g
    INFO: oracle.sysman.top.agent:addToTargetsXML:TargetInstaller added target file= /oracle/product/agent11g/sysman/install//oraclewls.out to /oracle/product/agent11g successfully.
    INFO: oracle.sysman.top.agent:AgentPlugIn:perform:Starting Agent with startAgent=true
    INFO: oracle.sysman.top.agent:Starting the agent
    INFO: oracle.sysman.top.agent:Starting the agent...
    INFO: oracle.sysman.top.agent:Executing Command: /oracle/product/agent11g/bin/emctl start agent
    INFO: oracle.sysman.top.agent:Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
    INFO: oracle.sysman.top.agent:Copyright (c) 1996, 2010 Oracle Corporation. Allrights reserved.
    INFO: oracle.sysman.top.agent:Agent is already running
    INFO: oracle.sysman.top.agent:Requested Operation Completed with Status = 0
    INFO: oracle.sysman.top.agent:
    The Management Agent Configuration Assistant has failed. The following failureswere recorded:
    Securing of the agent failed.
    INFO: oracle.sysman.top.agent:Internal PlugIn for {Micro Step state:step:2:configuration in CfmAggregateInstance: oracle.sysman.top.agent:11.1.0.1.0:common:family=CFM:oh=/oracle/product/agent11g:label=10} failed with an unhandled exception:
    java.lang.Exception:
    The Management Agent Configuration Assistant has failed. The following failureswere recorded:
    Securing of the agent failed.
    at oracle.sysman.emcp.agent.AgentPlugIn.startProcessing(AgentPlugIn.java:269)
    at oracle.sysman.emcp.agent.AgentPlugIn.invoke(AgentPlugIn.java:243)
    at oracle.sysman.emCfg.core.PerformMicroStep.runJavaClass(PerformMicroStep.java:540)
    at oracle.sysman.emCfg.core.PerformMicroStep.executeMicroStep(PerformMicroStep.java:120)
    at oracle.sysman.emCfg.core.ActionPerformer.performMicroStep(ActionPerformer.java:917)
    at oracle.sysman.emCfg.core.ActionPerformer$Performer.run(ActionPerformer.java:1038)
    INFO: oracle.sysman.top.agent:The plug-in Agent Configuration Assistant has failed its perform method
    Any help would be greatly appreciated.
    Thanks,
    Orivares

  • How to set-up new user for 9i OEm and OMS

    Apologies since this is a 10g grid control forum but I wasn't sure where to post these questions..
    I am trying to give a DBA access to our 9i OEM Repository so he can add his servers and databases for monitoring. I know he will need 'SELECT ANY DICTIONARY' and that I will need to create his user id in the Repo DB with DBA authority. Are there any other roles or privileges that he will need?
    Will I also need to place an agent on each server for the 9i OEM/OMS to discover it? Will the listenere.ora need to have the OEM Repository entries added?
    I searched the OEM Admin Guide but only found info on using the OEM Security Manager which I am not able to access.
    Thanks for your help..
    Sam

    Hang on, you have a 9i OEM OMS setup and you want to give x access to this so x can add targets onto the oms?
    If I've understood you correctly, you do not need to create a database account on the repository. You need to create a user on the OEM9i Console (probably a super admin to add targets is required) for x.
    A 9i or 8i agent is required for the OEM9i OMS to discover the target server and associated databases.
    9i and 8i agents require an entry in the listener.ora on the target server. You do not need an entry where you OEM9i OMS is.
    Download the 9i documentation, all this info is there.

  • Multiple repositories for one OMS?

    Can you use one Oracle Management Service with multiple backend repositories? Or does each respository require its own, dedicated OMS?
    In other words, is the OMS web application flexible so it can use two separate repository 11G databases? Or is it a 1:1 relationship between OMS and OMR?
    Thanks in advance.
    Jeff

    No you cannot have multilpe repositories for one OMS.
    Please check:
    Oracle® Enterprise Manager Concepts
    *11g Release 11.1.0.1*
    *3 Overview of Enterprise Manager Grid Control*
    http://download.oracle.com/docs/cd/E11857_01/em.111/e11982/overview.htm#CEGBFJIC
    regards
    Rob
    http://oemgc.wordpress.com

  • 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

  • Enterprise manager 12 installation fails: oms:WebTier Could Not Be Started

    During installation on EL6_64 I've got an exception :
    Start Oracle Management Service:
    INFO: oracle.sysman.top.oms:Executing command: /u01/app/oracle/product/oem12/oms/bin/emctl start oms
    INFO: oracle.sysman.top.oms:Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    INFO: oracle.sysman.top.oms:Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.
    INFO: oracle.sysman.top.oms:Starting WebTier...
    INFO: oracle.sysman.top.oms:WebTier Could Not Be Started
    INFO: oracle.sysman.top.oms:Error Occurred: WebTier Could Not Be Started
    INFO: oracle.sysman.top.oms:Please check /u01/app/oracle/product/oem12/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log for error details
    From /u01/app/oracle/product/oem12/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log:
    +2011-10-20 09:55:21,771 [main] INFO util.WebTierUtil execCmd.407 - Running the command: /u01/app/oracle/product/oem12/gc_inst/WebTierIH1/bin/opmnctl stopall+
    +2011-10-20 09:55:21,806 [main] INFO util.WebTierUtil getProcessResult.467 - opmnctl cmd output: opmnctl stopall: opmn is not running.+
    +2011-10-20 09:55:21,806 [main] INFO util.WebTierUtil getProcessResult.475 - opmnctl cmd error: Can not resolve localhost.localdomain for interface any+
    +2011-10-20 09:55:21,807 [main] INFO util.WebTierUtil getProcessResult.479 - opmnctl cmd exited with code 0+
    +2011-10-20 09:55:21,808 [main] INFO util.WebTierUtil execCmd.407 - Running the command: /u01/app/oracle/product/oem12/gc_inst/WebTierIH1/bin/opmnctl startall+
    +2011-10-20 09:55:21,839 [main] INFO util.WebTierUtil getProcessResult.467 - opmnctl cmd output: opmnctl startall: starting opmn and all managed processes...+
    opmnctl startall: failed.
    +2011-10-20 09:55:21,840 [main] INFO util.WebTierUtil getProcessResult.475 - opmnctl cmd error: Can not resolve localhost.localdomain for interface any+
    +2011-10-20 09:55:21,840 [main] INFO util.WebTierUtil getProcessResult.479 - opmnctl cmd exited with code 2+
    +2011-10-20 09:55:21,841 [main] INFO wls.OMSController startOMS.864 - WebTier Could Not Be Started+
    +2011-10-20 09:55:21,841 [main] ERROR wls.OMSController main.374 - OMSController failed for start oms+
    +2011-10-20 09:55:21,843 [main] ERROR wls.OMSController main.375 - OMSController Error: WebTier Could Not Be Started+
    Thank you

    Hi,
    I observed the same problem and can add more detail if required.
    In short, I required an entry in /etc/hosts for my.hostname that was declared against my actual interface IP address (192.168.0.x). I believe this is due to the behaviour of a call to getHostByName() in the weblogic platform startup sequence when initialising the web tier.
    Error:
    *2011-12-11 15:35:39,343 [main] INFO util.WebTierUtil getProcessResult.475 - opmnctl cmd error: Can not resolve my.hostname for interface any*
    This caused the web tier startup to fail and thus the subsequent agent registration to fail.
    _/etc/hosts when install failed with_
    127.0.0.1          localhost.localdomain localhost
    ::1          localhost6.localdomain6 localhost6
    127.0.0.1     my.hostname     my.hostname
    _/etc/hosts addition that succeeded_
    127.0.0.1          localhost.localdomain localhost
    ::1          localhost6.localdomain6 localhost6
    127.0.0.1     my.hostname     my.hostname
    192.168.0.x my.hostname my.hostname
    Note that my.hostname in /etc/hosts matches the HOSTNAME value in /etc/sysconfig/network
    (also note that my.hostname is not actually my hostname ;)
    Nick

Maybe you are looking for