OS Command Exception - ODI Agent?

Is there any exception for using OS Command in packages/scenario with an agent on Windows?
I have a package that has an OS Command to execute a remote task (using SCHTASKS /Run /S <Server> /TN <TaskName>)
Here is the thing: if I run the package/scenario without using an agent, the OS command is executed; if I run package/scenario using an agent I get an error: "Wrong process return code"
Then I tried to move this code into a batch script on the local drive so in the OS Command I have to call this batch but still it doesn't work.
Any ideas? Thank you.

I am trying to run a maxl statement via the ODI OS Command and am getting the same error . Wrong Process Return Code. It works fine if I execute as Local but errors if i run it through wiht the agent. The windows service is started with a network account and is still giving me the error.
My command is below.
CMD /c "essmsh \\vmds3wo95\F$\ODIFileStore\Scripts\export_to_ALLOC.mxl"
Any ideas.

Similar Messages

  • Do we need a ODI agent to be running for using the startscen command

    Do we need a ODI full installation(both server and client) for using the Startscen command or just the client install should be enough. And also do we need a ODI agent to be configured and running for using this StartScen command
    Thanks

    ODI client is an agent.
    So you don't need to declare one more if not needed on your infrastructure.
    But to run odistartscen you need to configure the odiparams.bat with your repository connexion.
    If not it will try to connect by default to the demo repostory on HSQL.
    best regards,
    Brice

  • ODI Agent 11g Exception in Linux

    Hi,
    I set up an agent agent_test in topology and used the correct parameters in odiParams.sh ( with encoded password)
    When i try to run using ./agent.sh -NAME=agent_test Port=8080
    I'm getting following strange exception
    2011-08-03 11:34:52.797 NOTIFICATION ODI-1128 Agent agent64 is starting. Application Server: STANDALONE. Agent Version: 11.1.1.3.0 - 23/06/2010. Port: 8080. JMX Port: 9080
    2011-08-03 11:35:04.982 WARNING unavailable
    oracle.odi.agent.logging.logFramework.OdiAgentException.getLocalizedMessage(OdiAgentException.java:68)
    oracle.odi.agent.logging.logFramework.OdiAgentException.toString(OdiAgentException.java:162)
    java.lang.Throwable.<init>(Throwable.java:242)
    java.lang.Exception.<init>(Exception.java:77)
    java.lang.RuntimeException.<init>(RuntimeException.java:77)
    oracle.odi.core.exception.OdiRuntimeException.<init>(OdiRuntimeException.java:56)
    oracle.odi.agent.logging.logFramework.OdiAgentException.<init>(OdiAgentException.java:57)
    oracle.odi.runtime.agent.processor.impl.CleanStaleSessionsUtils.cleanStaleSessionsAllWorkRepositories(CleanStaleSessionsUtils.java:218)
    oracle.odi.runtime.agent.servlet.AgentServlet.cleanStaleSessions(AgentServlet.java:371)
    oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:332)
    oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:226)
    javax.servlet.GenericServlet.init(GenericServlet.java:241)
    org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
    org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
    org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
    org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
    org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
    org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    org.mortbay.jetty.Server.doStart(Server.java:224)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    oracle.odi.Agent.startAgent(Agent.java:200)
    oracle.odi.Agent.main(Agent.java:493)
    I have ran and scheduled agents before but this strange exception to me. please help.
    Thanks
    John

    Did you try a different port number.
    8080 is commonly used as an alternative to the HTTP port 80
    Also, do you have a 64 bit linux ? If thats the case, then you have to install ODI using 32 bit version of Java on 64 bit linux

  • Problem With UNIX command in ODI Environment.

    A procedure is used in our package which involves moving a file from a folder to another in a UNIX server.
    The procedure uses an OS command - 'os.system' to execute unix command.
    The unix command is a grep command which seems to work fine when executed alone.
    But when this procedure is executed ,it fails.
    The following code raises an error and the procedure fails.:
    if os.system(cmd) <> 0:
    raise "command fails","see agent output for details";
    Whenever we are trying to reverse,we get "file not Found " error.
    We tried to execute the jython code by placing the files in local directories. The same error appears both when the file is in local and when it is in a remote directory.
    This is the error we get:
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (innermost last):
    File "<string>", line 20, in ?
    HeaderCmd failed:: See agent output for details      at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)      at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcScriptingOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(SnpSessTaskSqlS.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)      at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.g.y(g.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)

    Hi,
    The unix command is a grep command which seems to work fine when executed alone. :-
    I guess you executed this from your Unix server , so it work fines.
    And when you are trying to execute outside from this (using ODI) , its failing , right ?
    Can you please check the permission settings for that script file (sh).
    Please try by giveing the full permission (specifically execution permission) for all users connecting from other machines.
    This can be one of the reason for the failure .
    please let me know if this is not working
    Regards,
    Rathish

  • ODI Agent error

    Hi John,
    I am using my ODI agent as a windows service. It was working fine.
    But now it is not running fine and when i have seen the log for it the following error is given
    Starting Oracle Data Integrator Agent...
    Version : 10.1.3.5 - 10/11/2008
    com.sunopsis.tools.core.exception.SnpsRuntimeException: java.sql.SQLException: Io exception: Invalid connection string format, a valid format is: "host:port:sid"
    at com.sunopsis.dwg.cmd.n.a(n.java)
    at com.sunopsis.a.f.run(f.java)
    at com.sunopsis.dwg.cmd.i.y(i.java)
    at com.sunopsis.dwg.cmd.i.run(i.java)
    When i trie to launch the agent from the batch file the command prompt is opening and shutting down immediately.
    Please let me know the solution

    If it is not working from batch then you need to check the odiparams.bat file, it is more than likely some of the information is not correct in it.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • ODI AGENT STARTUP FAILED

    Dear All,
    While starting ODI agent,its failing with the below error
    2011-07-06 10:05:41.104 NOTIFICATION ODI-1128 Agent ODI_AGENT is starting. Application Server: STANDALONE. Agent Version: 11.1.1.5.0 - 22/04/2011. Port: 4999. JMX Port: 5999.
    2011-07-06 10:05:55.170 NOTIFICATION ODI-1136 Starting Schedulers on Agent ODI_AGENT.
    2011-07-06 10:06:55.677 WARNING 2006 Error occurred while computing schedules for work repository [WORKREP]. Error message : org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is oracle.odi.jdbc.datasource.ConnectionTimeoutException: A login timeout occured while connecting to the database
    2011-07-06 10:06:55.729 ERROR ODI-1131 Agent ODI_AGENT encountered an error: ODI-1406: Agent ODI_AGENT started with warning: JDBC connection error occurs while connecting to the work repository WORKREP. Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is oracle.odi.jdbc.datasource.ConnectionTimeoutException: A login timeout occured while connecting to the database
    Need help in order to solve this case.

    Hi
    Make sure that JDK 1.6.0_21 or higher version insatlled in your PC.
    Have you installed RCU 11g before ODI 11g installation.
    If not, please installed it and later start the ODI 11g installation.
    Open odiparams.bat/sh file.
    encode the master repository password using enocde.cmd/sh and paste the same encoded password on odiparams.bat/sh file
    check MASTER DB Crredentials/Master repository login credentials/ work repository details are properly setuped or not.
    check JDBC URL
    check ODI_JAVA_HOME path seted in your PC
    ODI_JAVA_HOME=d:\Oracle\Middleware\jdk160_21 in case weblogic installed before ODI 11g other wise
    ODI_JAVA_HOME=c:\Program files\Java\jdk1.6.0_21\bin at Windows (setup it on environment variable) at linux export the ODI_JAVA_HOME path using "export" command
    run the ODI agent and check whether it is running or not.
    Hope this may helps you.
    Thanks,
    Phani

  • ODI agent creation issue

    Hi,
    I am trying to create ODI agent in Windows. I have followed the steps in ODI set up document. It has launched the server. Now I am trying to create that as a windows service. But I am getting following error message.
    I ran the followiing the command line
    <ODI_HOME>\bin\agentservice -i -s Sched_Agent 20910
    The error I am getting is
    "FATAL | wrapper | The argument 'Files\Java\jdk1.5.0_12\bin\java.exe' is not a valid property name-value pair."
    I have 10.1.3.5.5
    My ODI_JAVA_HOME is pointing to C:\Program Files\Java\jdk1.5.0_12. Is this the issue for the error
    Anyone knows why its happening.
    -app
    Edited by: user6401072 on Jul 28, 2010 11:35 AM

    The reason is becuase you JDK path is some thing like this c:\program files\Java\jdk1.5.0_12\bin\java.exe'
    so what is the happening becuase of space between program and files its not picking up the correct JDK path .
    Either change the path of JDK installation or
    go to your odiparam path and go to this line
    if "%ODI_JAVA_HOME%" == "" set ODI_JAVA_HOME="c:\program files\Java\jdk1.5.0_12"
    or
    if "%ODI_JAVA_HOME%" == "" set ODI_JAVA_HOME='c:\program files\Java\jdk1.5.0_12'
    i dont remember exactly whether single or double quotes but try and let me know if that helps you

  • ODI Agent Test Start is Wrong

    Hi,
    I've been following John's excellant blog. I've created the master repository. In topology manager, I have created the connection, the dataserver, the work repository, the agent and context. I've updated odiparams.bat (http://john-goodwin.blogspot.com/2008/09/odi-series-part-2-agent.html)
    I try to test of start ODI Agent I get this error:
    C:\ODI>C:\ODI\oracledi\bin\agentscheduler.bat "-port=20300" "-NAME=ODI_Agent"
    The system cannot find the path specified.
    OracleDI: Starting Scheduler Agent ...
    'oracle.odi.Agent' is not recognized as an internal or external command, operable program or batch file.
    My start agent .bat file:
    C:\ODI\oracledi\bin\agentscheduler.bat "-port=20300" "-NAME=ODI_Agent"
    My odiparams file:
    rem
    rem Repository Connection Information
    rem
    set ODI_SECU_DRIVER=oracle.jdbc.driver.OracleDriver
    set ODI_SECU_URL=jdbc:oracle:thin:@oradbserver:1521:TEST;selectMethod=cursor;databaseName=ODI_MASTERREP;integratedSecurity=false
    set ODI_SECU_USER=ODI_MASTERREP
    set ODI_SECU_ENCODED_PASS=erfa,mE7dy,q8gPvKnjVAb.n8a
    set ODI_SECU_WORK_REP=ODI_WORKREP
    set ODI_USER=SUPERVISOR
    set ODI_ENCODED_PASS=LELKIELGLJMDLKMGHEHJDBGBGFDGGH
    set ODI_INIT_HEAP=128m
    set ODI_MAX_HEAP=1024m
    set ODI_JAVA_EXE="%ODI_JAVA_HOME%\bin\java.exe"
    set ODI_JAVAW_EXE="%ODI_JAVA_HOME%\bin\javaw.exe"
    set ODI_JAVAC_EXE="%ODI_JAVA_HOME%\bin\javac.exe"
    OS Win 2003R2 32bit
    ODI 10.1.3.5.0 has been updated to 10.1.3.5.5 via Oracle Data Integrator Cumulative Patch and Application Adapters for Data Integration Media Pack.

    Hi,
    If you look in agentscheduler.bat the first lines are :-
    if "%ODI_HOME%" == "" set ODI_HOME=..
    call "%ODI_HOME%\bin\odiparams.bat"
    echo OracleDI: Starting Scheduler Agent ...
    In your output you have :-
    The system cannot find the path specified.
    It is trying to call "%ODI_HOME%\bin\odiparams.bat
    and it can't find the file.
    Do you have an windows environment variable set for ODI_HOME
    If not create one and set its value to C:\ODI\oracledi
    or update it to the path above
    It should then find odiparams.bat
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • ODI Agents and EPM

    Hello!
    I use EPM 11.1.2.1.0, ODI 11g, Solaris SPARC
    The situation is as follows:
    On a single server X is installed Hyperion Essbase, on another server (Y) - the application server (Hyperion Planning, Shared Services, etc.), the third (Z) - ODI
    In Oracle Data Integrator creates the following packages:
    1) Load the actual values from the Oracle DWH to Hyperion Essbase and execution of business rules using the Hyperion Planning console utility - CalcMgrCmdLineLauncher.sh
    2) Extract planning values from the Hyperion Essbase to Oracle DWH, using KM - LKM Hyperion Essbase Data to SQL, which is specified EXTRACTION_QUERY_FILE - report script Essbase.
    My question is, do I need to install ODI agents on both servers: X and Y. On Y must be exactly as it is called a command line utility, located on the hyperion planning server. Be sure to install the agent on the server X, where Essbase. (called report script)
    If I need the agents on both servers, I can somehow relate them so as not to break the existing chain of steps in the ODI package?

    If it is the report script extract then it should still work even if there is no agent on the essbase server.
    An agent will be required on the running the calc manager utility though.
    Even if you did multiple agents you can generate a scenario for each step and call the scenarios from a package.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • ODI Agent - when do i need to use?

    can anybody explain me the perpose of ODI Agent? and when do i need to use Agent?
    Edited by: knidhi on Oct 5, 2009 3:31 PM
    Edited by: knidhi on Oct 5, 2009 4:07 PM

    If I could finesse your answer slightly, hopefully to help (or confuse):
    There are multiple agent types:
    - the Local (No agent): this opens additional threads in the current GUI process. The agent will just run as additional threads in your current process, using the same settings as your GUI environment.
    - a standalone agent: if you start an agent from the commandline using the agent.sh/bat. This will start a "listener agent". It starts up and passively listens for execution requests. When a request is passed to the agent, it includes all the necessary information to connect to the repository etc. All this information is there in the invocation package. (for more information on what is passed look at the documentation for the invocation API or at the ODIInvoke webservice)
    - a scheduler agent: when you start a scheduler agent from the commandline with the agentscheduler.bat/sh file, it will read from the odiparams.sh/bat file the connectivity paramaters for the repository, where it will "look itself up" based on the agent name passed, to find out what scenarios it should be scheduling. This agent may also take requests, just like the standalone agent described above.
    - a task may also be invoved at the opertaing system command level using startscen.bat/sh. This will start a standlone agent for the duration of this execution only, which not listen for other requests, it reads its parameters from the command line (for which sceenario, version and context) and from the odiparams file for the repository connectivity parameters as to where to find the requested scenario and where the execution will be logged.

  • Managing ODI Agent through OPMN - Install Issue

    Hi
    I am attempting to set up my ODI agent so that I can manage it through my OPMN service but I keep getting an error "java is not recognised as an internal or external command, operable program or batch file" when I run the command "odi_opmn_addagent.bat agentcreate.properties".
    I have installed EPM 11.1.2.2 and my essbase service is currently managed through the OPMN.
    I have updated the odiparams, agentcreate.properties and odi_opmn_addagent.
    In the agentcreate file I set my JAVA_HOME to E:\Oracle\Middleware\jdk160_29
    Any ideas what could be wrong?
    Thanks
    M

    Copy your jdk path as given below. Change it if you have different.
    C:\Program Files\Java\jdk1.6.0_33\bin
    Right click on my computer->go to properties->advanced system setting->environmental variable->system variables
    Scroll down. you will get a variable names as "Path"
    Double click on it. then single click on variable value. Then press home key in your keybord. (better take backup of it)
    now pest above code that is C:\Program Files\Java\jdk1.6.0_33\bin;
    Give a semicolon at the end as i have given. Click ok,ok,ok
    Now go to cmd and type javac. let me now the output.

  • ODI agent status shown prepared in Weblogic

    hi,
    I have installed FDMEE 11.1.2.4. When i start services everything is ok except ODI Java EE agent. I haven't configured it ( i think it was preconfigured).
    I have tried starting ODI agent from enterprise manager but i am getting an error; will paste below.
    I have seen that in weblogic server under erpi integrator server my odi console status is active and odi agent status is prepared. I don't know how to start JAVA EE agent.
    Any help?
    Error:
    Invoking Start Up operation for application oraclediagent on target ErpIntegrator0.
    [Deployer:149193]Operation 'start' on application 'oraclediagent' has failed on 'ErpIntegrator0'
    [Deployer:149034]An exception occurred for task [Deployer:149026]start application oraclediagent on ErpIntegrator0.: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
    com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=MasterMemberSet(
        ThisMember=null
        OldestMember=null
        ActualMemberSet=MemberSet(Size=0
        MemberId|ServiceVersion|ServiceJoined|MemberState
        RecycleMillis=1200000
        RecycleSet=MemberSet(Size=0
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
    at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
    at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
    at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
    at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
    at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
    at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
    at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
    at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
    at oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache.<init>(OdiAgentCoherenceCache.java:52)
    at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
    at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
    at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
    at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
    at javax.servlet.GenericServlet.init(GenericServlet.java:242)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    :com.tangosol.net.RequestTimeoutException:Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=MasterMemberSet(
        ThisMember=null
        OldestMember=null
        ActualMemberSet=MemberSet(Size=0
        MemberId|ServiceVersion|ServiceJoined|MemberState
        RecycleMillis=1200000
        RecycleSet=MemberSet(Size=0
    Operation Start Up on target oraclediagent Failed. Please see error logs for details.
    Regards

    Hi JanGLi,
    The ODI Agent is completely failing to start here from the error that you initially pasted so agent tests are not going to work wherever you try them. Port 6550 should have something listening on it as that's the port that the FDMEE managed server listens on so that would only prove that the FDMEE managed server is up. I can't see the connection closed error having anything to do with running out of connections in the connection pool either as it's simply a message saying that a connection was closed (not that the connection pool is exhausted).
    On the plus side though I have seen the 'Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent"' error in the past (I get a lot of the really nice issues coming my way). Which operating system are you using here? I've seen this happen on Windows when there are multiple network interfaces and an incorrect interface has been put to the top of the bind order (e.g. an interface that has fallen back to a link local address in the 169.254.0.0/16 range as DHCP has failed).
    Regards
    Craig

  • Asking about ODI agent ?

    Hi...
    Based on my system, I have created about 50 scenarios and 6 ODI agent. Each of the ODI agent will be handled about 8 scenarios. This is my configuration for the ODI agent:-
    ODI_INIT_HEAP=32m
    ODI_MAX_HEAP=256m
    Then, based on my configuration, each of ODI agent is set as 256M.
    My question is which one better if I am using 1/2 agent with bigger MAX_HEAP size or used 6 agent with the config as above.
    Please advise me..
    TQ,
    baharin

    hi..
    I have tried used only one agent with 2048 max size.. but after i start until 30 scenarios.. than i got an error msg as below:-
    java.sql.SQLException: Io exception: Got minus one from a read call
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
         at com.sunopsis.sql.SnpsConnection.u(Unknown Source)
         at com.sunopsis.sql.SnpsConnection.c(Unknown Source)
         at com.sunopsis.sql.i.run(Unknown Source)
    why ?

  • Passwords in ODI agent trace

    Hi,
    In ODI agent trace, I found the passwords which is used as parameters in nzload (netezza load command). It is viewable to all. Is there any way to suppress the password.
    like nzload -host servername -u produsr -pw password -db NZDB -t C_0NZ_MRP_SAFETY_STOCK
    Thanks,
    Priya

    In the KM , if you are able to find <%odiRef.getInfo("SRC_PASS")%> , try changing to <%odiRef.getInfo("SRC_ENCODED_PASS")%> and see if that works and help you to encode the password .
    Hope that helps.

  • ODI Agent Start Up Failure

    Hi All,
    I have installed and configured ODI 11g I have performed following tasks
    1) Created Master Repository
    2) Connected User for the ODI
    3) Created Work Rep
    4) Created Physical as well as logical agent
    Before I have started the agent I have performed following tasks
    1) Updated my ODI PARAMS
    Update Master Rep info:
    Updated my relational db info related to master rep
    Encode Password:
    My master repository is ODI_MASTER and password is password1
    Command: encode password1
    I have updated my ODI params with the new encoded password
    similarly I have updated the encoded SUPERVISOR password.
    I have udpated my work repository info as well.
    But when I start the agent from the command line I receive following error
    E:\ODI_HOME\oracledi\agent\bin>E:\ODI_HOME\oracledi\agent\bin\agent.bat "-NAME=P
    RODAGENT" "-PORT=20910"
    OracleDI: Starting Agent ...
    2010-11-01 12:50:05.490 NOTIFICATION ODI-1128 Agent PRODAGENT is starting. Appli
    cation Server: STANDALONE. Agent Version: 11.1.1.3.0 - 23/06/2010. Port: 20910.
    JMX Port: 21910
    2010-11-01 12:50:07.771 ERROR ODI-1131 Agent PRODAGENT encountered an error: ODI
    -1404: Agent PRODAGENT start failure: an authentication error occurred while con
    necting to the master repository,
    2010-11-01 12:50:07.771 WARNING unavailable
    oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
    javax.servlet.GenericServlet.init(GenericServlet.java:241)
    org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
    org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
    org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
    org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
    org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
    org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    org.mortbay.jetty.Server.doStart(Server.java:224)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    oracle.odi.Agent.startAgent(Agent.java:200)
    oracle.odi.Agent.main(Agent.java:493)
    Please let me know if Iam going wrong at any point.
    Thanks,
    KRK

    Dev,
    Thanks for your quick reply
    I have updated my ODI_USER password then I have recieved new error message
    But I have created my physical and logical agent in the topology manager but this error shows up that its not defined
    E:\ODI_HOME\oracledi\agent\bin>E:\ODI_HOME\oracledi\agent\bin\agent.bat "-NAME=P
    RODAGENT" "-PORT=20910"
    OracleDI: Starting Agent ...
    2010-11-01 13:21:12.271 NOTIFICATION ODI-1128 Agent PRODAGENT is starting. Appli
    cation Server: STANDALONE. Agent Version: 11.1.1.3.0 - 23/06/2010. Port: 20910.
    JMX Port: 21910
    2010-11-01 13:21:14.240 ERROR ODI-1131 Agent PRODAGENT encountered an error: ODI
    -1405: Agent PRODAGENT start failure: the agent is not defined in the topology f
    or master repository.
    2010-11-01 13:21:14.240 WARNING unavailable
    oracle.odi.runtime.agent.servlet.AgentServlet$1.doAction(AgentServlet.java:734)
    oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplat
    e.java:193)
    oracle.odi.runtime.agent.servlet.AgentServlet.getSnpAgentForAgentInstance(AgentS
    ervlet.java:726)
    oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:323)
    oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:226)
    javax.servlet.GenericServlet.init(GenericServlet.java:241)
    org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
    org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
    org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
    org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
    org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
    org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
    org.mortbay.jetty.Server.doStart(Server.java:224)
    org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
    oracle.odi.Agent.startAgent(Agent.java:200)
    oracle.odi.Agent.main(Agent.java:493)
    Thanks,
    KRK
    Edited by: 794835 on Nov 1, 2010 1:22 PM
    Edited by: 794835 on Nov 1, 2010 1:24 PM

Maybe you are looking for