ODI with agent

Hi Experts,
I'm newbie for ODI, sorry for this basic question, we have a requirement to use ODI for data transformation on oracle database. our database configuration is Non RAC , we would like to install ODI on DB server,
the question is , can we install Java ee agent on non rac environment,? or standalone is enough without WLS? which agent is recommended for Non Rac environment , please guide on this.  Thanks in Advance.

Thanks SH, We would like to install ODI on database server itself without WLS , can we use this approach for production? can we maintain HA in non cluster env without WLS? please confrm?

Similar Messages

  • ERROR ODI-1134 Agent  encountered an error: ODI-1217: Session PRC_CALL_JAVA_GEO_CDC (472) fails with return code 7000. Caused by: ODI-1226

    ODI-1590: The execution of the script failed. Caused By: org.apache.bsf.BSFException: BeanShell script error: Sourced file: inline evaluation of: ``import oracle.odi.km.exception.OdiKmException; import GeoHub_migrator;  com.Data . . . '' : Typed variable declaration : Class: com.DataMigrator not found in namespace : at Line: 4 : in file: inline evaluation of: ``import oracle.odi.km.exception.OdiKmException; import migrator;  com.Data . . . '' : com .DataMigrator BSF info: PRC_CALL_JAVA_GEO at line: 0 column: columnNo                 at bsh.util.BeanShellBSFEngine.eval(Unknown Source)                 at bsh.util.BeanShellBSFEngine.exec(Unknown Source)                 at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:357)                 at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:173)                 at oracle.odi.runtime.agent.execution.interpreter.SessionTaskScriptingInterpretor.scripting(SessionTaskScriptingInterpretor.java:173)                 at oracle.odi.runtime.agent.execution.SessionTask.scripting(SessionTask.java:117)                 at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)                 at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:19)                 at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)                 at oracle.odi.runtime.agent.execution.SessionTask.processTask(SessionTask.java:214)                 at oracle.odi.runtime.agent.execution.SessionTask.doExecuteTask(SessionTask.java:135)                 at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:856)                 at oracle.odi.runtime.agent.execution.SessionExecutor$SerialTrain.runTasks(SessionExecutor.java:2004)                 at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:544)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:709)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:624)                 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:789)                 at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:570)                 at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1182)                 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:177)                 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:64)                 at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)                 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:78)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:149)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:140)                 at oracle.odi.runtime.agent.RuntimeAgent.startScenario(RuntimeAgent.java:884)                 at oracle.odi.runtime.agent.InternalRuntimeAgent.startScenario(InternalRuntimeAgent.java:84)                 at com.sunopsis.dwg.tools.StartScen.startScenOnLocalAgent(StartScen.java:1224)                 at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java:324)                 at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:192)                 at oracle.odi.runtime.agent.execution.SessionTask.execIntegratedFunction(SessionTask.java:942)                 at oracle.odi.runtime.agent.execution.SessionTask.executeOdiCommand(SessionTask.java:575)                 at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:44)                 at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:20)                 at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)                 at oracle.odi.runtime.agent.execution.SessionTask.processTask(SessionTask.java:214)                 at oracle.odi.runtime.agent.execution.SessionTask.doExecuteTask(SessionTask.java:135)                 at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:856)                 at oracle.odi.runtime.agent.execution.SessionExecutor$SerialTrain.runTasks(SessionExecutor.java:2004)                 at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:544)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:709)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:624)                 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)                 at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:789)                 at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:570)                 at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1182)                 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:177)                 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor

    This is the wrong forum for an ODI question.

  • Scenario is not running in ODI Standalone agent from OPMN

    when i am trying to run my scenario using ODI standalone agent it is not running and it is giving below error in opmn log file.
    VARNING: Error retrieving ID statistics for repository WORKREP1.
    ODI-1406: Agent Agent_ODI started with warning: JDBC connection error occurs while connecting to the work repository WORKREP1.
    Caused By: oracle.odi.core.config.WorkRepositoryResourceFailureException: ODI-10182: Uncategorized exception during repository access.     
    Could not get JDBC Connection; nested exception is java.sql.SQLException: Ett undantag uppstod när anslutning hämtades: oracle.ucp.UniversalConnectionPoolException: Kan inte hämta anslutning från datakälla: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
         at oracle.odi.core.repository.Repository.getWorkRepository(Repository.java:195)
         at oracle.odi.core.OdiInstance.createWorkRepository(OdiInstance.java:504)
         at oracle.odi.runtime.agent.utils.AgentOdiInstance.createWorkRepository(AgentOdiInstance.java:60)
         at oracle.odi.core.OdiInstance.<init>(OdiInstance.java:581)
         at oracle.odi.runtime.agent.utils.AgentOdiInstance.<init>(AgentOdiInstance.java:28)
         at oracle.odi.runtime.agent.utils.AgentOdiInstance.createInstance(AgentOdiInstance.java:32)
         at oracle.odi.runtime.agent.utils.OdiInstanceCache.getWorkInstance(OdiInstanceCache.java:181)
         at oracle.odi.runtime.agent.support.InternalAgentUtils.getAuthenticatedTargetOdiInstance(InternalAgentUtils.java:336)
         at oracle.odi.runtime.agent.servlet.AgentServlet.verifyAllIdStatistics(AgentServlet.java:988)
         at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:361)
         at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:239)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
         at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
         at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
         at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
         at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
         at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
         at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
         at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
         at org.mortbay.jetty.Server.doStart(Server.java:224)
         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
         at oracle.odi.Agent.startAgent(Agent.java:204)
         at oracle.odi.Agent.main(Agent.java:538)
    Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Ett undantag uppstod när anslutning hämtades: oracle.ucp.UniversalConnectionPoolException: Kan inte hämta anslutning från datakälla: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
         at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:82)
         at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:524)
         at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:588)
         at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:613)
         at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:645)
         at org.springframework.jdbc.object.SqlQuery.execute(SqlQuery.java:111)
         at org.springframework.jdbc.object.SqlQuery.execute(SqlQuery.java:121)
         at org.springframework.jdbc.object.SqlQuery.execute(SqlQuery.java:136)
         at oracle.odi.core.repository.support.RepositoryUtils$RepositoryInfoSource.loadRepositoryInfo(RepositoryUtils.java:182)
         at oracle.odi.core.repository.support.RepositoryUtils.loadWorkRepositoryInfo(RepositoryUtils.java:382)
         at oracle.odi.core.repository.Repository.getWorkRepository(Repository.java:174)
         ... 25 more
    Caused by: java.sql.SQLException: Ett undantag uppstod när anslutning hämtades: oracle.ucp.UniversalConnectionPoolException: Kan inte hämta anslutning från datakälla: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
         at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
         at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:79)
         ... 35 more
    Caused by: java.sql.SQLException: Ett undantag uppstod när anslutning hämtades: oracle.ucp.UniversalConnectionPoolException: Kan inte hämta anslutning från datakälla: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
         at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:488)
         at oracle.ucp.util.UCPErrorHandler.throwSQLException(UCPErrorHandler.java:163)
         at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:943)
         at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:873)
         at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:863)
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.ucp.UniversalConnectionPoolException: Kan inte hämta anslutning från datakälla: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
         at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:368)
         at oracle.ucp.util.UCPErrorHandler.throwUniversalConnectionPoolException(UCPErrorHandler.java:49)
         at oracle.ucp.util.UCPErrorHandler.throwUniversalConnectionPoolException(UCPErrorHandler.java:80)
         at oracle.ucp.jdbc.DriverConnectionFactoryAdapter.createConnection(DriverConnectionFactoryAdapter.java:122)
         at oracle.ucp.common.UniversalConnectionPoolImpl$UniversalConnectionPoolInternal.createOnePooledConnectionInternal(UniversalConnectionPoolImpl.java:1610)
         at oracle.ucp.common.UniversalConnectionPoolImpl$UniversalConnectionPoolInternal.access$600(UniversalConnectionPoolImpl.java:1446)
         at oracle.ucp.common.UniversalConnectionPoolImpl.createOnePooledConnection(UniversalConnectionPoolImpl.java:514)
         at oracle.ucp.jdbc.oracle.OracleJDBCConnectionPool.createOnePooledConnection(OracleJDBCConnectionPool.java:129)
         at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnectionWithoutCountingRequests(UniversalConnectionPoolImpl.java:297)
         at oracle.ucp.common.UniversalConnectionPoolImpl.borrowConnection(UniversalConnectionPoolImpl.java:142)
         at oracle.ucp.jdbc.JDBCConnectionPool.borrowConnection(JDBCConnectionPool.java:157)
         at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:931)
         ... 9 more

    i have tried to change the all the ways in odiparms file but i am getting the same error message....

  • Issues with agent.

    Here is the script:
    import os
    retVal = os.system(r'sqlldr odi_stage/test1234@devodi control=E:\Hyperion\DRM\ODI\Scripts/DRM_ESSBASE_PLANNING.ctl log=E:\Hyperion\DRM\ODI\Logs/DRM_ESSBASE_PLANNING2.log')
    when i excecute this script from studio with agent=local(noagent) it runs fine and when i run same script with an agent=d1odiagent_dev it fails with error Traceback (innermost last). it seems like its not able to recognise local drives. anyone came across this issue?
    Thanks.
    Sri.

    Phil..
    Here is the script I have added to capture the message:
    if retVal == 1 or retVal > 2:
    str1 = 'SQLLDR FAILED. Please check logs for details '
    raise str1
    else:
    str1 = 'SQLLDR SUCCESSFULL'
    and please find the error message below.
    Thanks.
    ODI-1217: Session PROC_LD_ESSBASE_PLANNING_SQLLDR_T (841001) fails with return code 7000.
    ODI-1226: Step PROC_LD_ESSBASE_PLANNING_SQLLDR_T fails after 1 attempt(s).
    ODI-1232: Procedure PROC_LD_ESSBASE_PLANNING_SQLLDR_T execution fails.
    Caused By: org.apache.bsf.BSFException: exception from Jython:
    Traceback (innermost last):
    File "<string>", line 7, in ?
    SQLLDR FAILED. Please check logs for details
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2374)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1615)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1580)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:619)

  • Integration ODI with Siebel EIM.

    Hi ODI forum's
    I have installed ODI 11g version in linux platform and I am doing POC on this
    The POC like this : Integration ODI with Siebel EIM(I am very new to the ODI)
    For this I have installed below softwares.
    --- Oracle Database 11.2.0.1.0
    --- RCU
    --- ODI 11g
    --- WebLogic 10.3.5.0
    --- OS - Red Hat Linux
    The above softwares are installed prefectly..
    I have configured the below components after installation was completed.
    Configure a WebLogic Domain
    Starting the Administation Server
    Starting the Managed server
    Manually configure the Standalone agent
    Question 1 Does we need the configure these components like Java EE Agent, Oracle Data Integrator Console and Oracle Enterprise Manager.
    2 Do we need to install Data quality and data profiling (as per my knowledge these are not required )
    3 There is file called topology.sh should be created in ODI installation directory, but it was not created.
    4. what is the purpose of this file.
    Please share me some docs or ppt on how to integrate the ODI with siebel EIM.
    Please clarify my doubts and get back me soon.

    Hi User;
    For your issue i suggest close your thread here as changing thread status to answered and move it to Forum Home » System Management and Integration » Data Integrator which you can get more quick response
    Regard
    Helios

  • ODI11G:Network MSaccessfile throgh DSN executing Locally but not with Agent

    Hi,
    We able to access Network MSaccessfile and running fine using loca(No agent) agent from our dev machine but when we configured the MS acess DSN on Agent machine and trying to execute the packageusing agent , it is failing with below error.
    Even when we connect to agent machine and try to execute the package from agent machine locally(no agent) it is working( the same case as mentioned above i.e. able to execute locally from our dev machine) but execution using agent not able to run from our dev/Agent machine. Throwing the below error.
    What could be the problem?? I gueseed this would be a access issue as our customer has given network access on agent machine using some different user and this user might not be having proper access on ODI machine as package is failig for local execution if we execute the package from Agent machine
    While accesing ODBC\Remote file ODI uses which account to access those files ?
    does it needs to create any specific account for that ? or something like that?
    Error on excutinng using Agent-->
    oracle.odi.runtime.agent.invocation.InvocationException: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Access database engine cannot open or write to the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view and write its data.
    at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:279)
    at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeTestDataServer(RemoteRuntimeAgentInvoker.java:653)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.remoteTestConn(SnpsDialogTestConnet.java:847)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.remoteConnect(SnpsDialogTestConnet.java:820)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.jButtonTest_ActionPerformed(SnpsDialogTestConnet.java:758)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.connEtoC1(SnpsDialogTestConnet.java:137)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.access$1(SnpsDialogTestConnet.java:133)
    at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$IvjEventHandler.actionPerformed(SnpsDialogTestConnet.java:87)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
    at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
    at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
    at java.awt.Component.processMouseEvent(Component.java:6267)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
    at java.awt.Component.processEvent(Component.java:6032)
    at java.awt.Container.processEvent(Container.java:2041)
    at java.awt.Component.dispatchEventImpl(Component.java:4630)
    at java.awt.Container.dispatchEventImpl(Container.java:2099)
    at java.awt.Component.dispatchEvent(Component.java:4460)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
    at java.awt.Container.dispatchEventImpl(Container.java:2085)
    at java.awt.Window.dispatchEventImpl(Window.java:2478)
    at java.awt.Component.dispatchEvent(Component.java:4460)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
    With Thanks,
    Shilpa
    Edited by: shilpa on Feb 6, 2012 2:00 AM

    Hello Surya,
    As on ODI development machine(BDVMD122) where we configured the MS access DSN for remote file, the package with local Agent(No agent) is executing perfectly. So I dont think its a Topology-context issue.
    Please let me know if my statement is wrong
    Venkat,
    There is a very less possibility of 'file is open somewhere' as it is executing locally perfectly.
    The package execution in PROD is done using Agent(not with Local agent).
    Dev environment-
    Machine-----------------------------DSN-Configuration-----------ODI Execution------------------------------------Status
    BDVMD122- ODIdevMachine-----On BDVMD122-------------on BDVMD122 with Local(No agent)----------Success in execution
    BDVMD122- ODIdevMachine-----On BDVMD122------------- same as above but in UATwithUAT login--- Success
    BDVMD122- ODIdevMachine-----On devAgent - BDVMD100---on BDVMD122 using agent BDVMD100-----Failure with the msg mentioned above
    UAT Environment-after code movement to different repository
    BDVMD122- ODIdevMachine Local(No agent)     on BDVMD122 with Local(No agent) Failure with the msg mentioned above
    Comment on your point
    1> Make sure the file is accessible from the server(where its failing). if possible create an an agent on the server specifying host as your desktop. use this agent to execute the interface.
    <Shilpa> We have created the DSN on ODI agent where we are able to access the network file. As we dont have any thing to check for the exact permission on ODI agent, we are unsure of what type of access we have on ODI agent machine. We raised this as a query to our customer. But when we RDP ODI agent machineand try to execute the ODI package from ODI Agent machinre With Local ( No agent), it is giving the same error.
    Our customer has given remote access to file on ODI agent's machine using some different user and we have created the DSN on ODI agent machine by logging into ODImachine using our dev id's( through RDP). I guess, this could be the permission issue also
    I did not get your point-"if possible create an an agent on the server specifying host as your desktop. use this agent to execute the interface"-
    What does here server means, how to host desktop?
    2> There is another option..use an intermediary system to pile all your source files and load from. however you will have to install odi on this system and create an agent , again.
    <Shilpa>
    We have to access files from remote server only.
    With Thanks,
    Shilpa Dhote
    Edited by: shilpa on Feb 7, 2012 4:52 AM
    Edited by: shilpa on Feb 7, 2012 5:14 AM
    Edited by: shilpa on Feb 7, 2012 5:19 AM
    Edited by: shilpa on Feb 7, 2012 5:19 AM
    Edited by: shilpa on Feb 7, 2012 5:20 AM
    Edited by: shilpa on Feb 7, 2012 5:20 AM
    Edited by: shilpa on Feb 7, 2012 5:20 AM
    Edited by: shilpa on Feb 7, 2012 5:21 AM
    Edited by: shilpa on Feb 7, 2012 5:21 AM
    Edited by: shilpa on Feb 7, 2012 11:12 PM
    Edited by: shilpa on Feb 8, 2012 2:46 AM

  • ODI-1274: Agent Exception Caused by: PermGen space

    Hi All,
    I am trying to execute loads from designer, the below exception pops up
    oracle.odi.runtime.agent.invocation.InvocationException: ODI-1274: Agent Exception Caused by: PermGen space
         at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:265)
         at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartSession(InternalRemoteRuntimeAgentInvoker.java:192)
         at com.sunopsis.graphical.dialog.SnpsDialogExecution.runStartSession(SnpsDialogExecution.java:1573).
    However I am able to run the loads through unix.
    Can some pls help?
    Thanks,
    Ashok

    Hi Bhabani,
    JDK Version in unix is 1.6_26 and the agent is a Stand-Alone agent.
    Let me include few more observations.
    1) I am able to run the loads through unix( Stand-Alone agent)
    2) I am able to run the loads through designer using Local agent, only when i choose the unix agent to run the loads through designer, i get the above mentioned error.
    3) Because of 2 , i thought something is wrong with designer setup. But i connected to a different repository and i was able to execute the loads through unix agent(We have seperate unix agent installion for each repository).
    Thanks,
    Ashok

  • OBIEE 11G: Issue with Agent

    Hello All,
    I am trying to make agent work in OBIEE 11G together with Active Directory settings but the agent are failling for some users. Some users are not able to send the ibots:
    We get the following message with Agent Failed:
    Agent ID: XXXXXXX
    No devices for user: XXXX
    Agent ID: XXXXXXXX
    No Content for user: XXXX
    Kindly note that I have already checked the My Account of these users and the email address is well present there.
    Can anyone help us investigate on this issue.
    Thanks and Regards

    Where do you have your LDAP configured
    Is it in RPD or in Weblogic?

  • Error: Result of agent resolution does not agree with agents of task

    Hi,
    I'm getting the error "Result of Agent Resolution does not agree with agent of Task".  I'm passing the agents in Expression which I'm getting from Method in my previous step and passing to workflow container and it is getting passed to Expression. The userid is present in that container. And the Task is assigned as General Task but still I dont know what might be the problem. The ID is with 'US' prefix. Even if I give the userid directly in the Task, it shows the same error.
    Regards,
    JMB

    Hi
    Incase you are using different clients for development and testing, make sure in testing client, task is assigned as general task.
    You may check the way the userid is passed. Please note that the US is object type and Object ID(user id) is different. Both of them should not be part of one string. So while you test, just pass the user id without a prefix US. Hope it will work for u.
    Regards
    Waz

  • Result of agent resolution does not agree with agents of task

    Hello Experts,
       I am trying to configure a workflow for Employee Travel expense, the Business object am using is BUS2089 for event CREATED.
      And am configuring workflow task WS20000040 (Approve trip). and in the work flow builder I am assigning User as an Agent and fixing it to a user say "USER1" for Task 404 (Check trip facts) and for Task 416 (Approve trip facts) again am assigning User as an Agent and fixing it to user say "USER2"
    Now when the Trip is saved using PR05, this work flow is triggerred - which is what i want and it sends work item to USER1,  now when USER1 says Trip facts are consistent the work item should go to USER2 but here it is failing and the log says "Agent determination for step 0000000416 failed" and details say "Result of agent resolution does not agree with agents of task" which is  SWF_RUN 544
    Can you guys help me by telling where am going wrong.  Am i missing some configuration somewhere.
    I have changed the Task properties - Attributes i have changed the task as a General Task,(i did it by navigating through Control Tab of the task)
    appreciate your response.. Thanks
    Usman

    Thanks Novjot
        I made the task as a general task and i see a gree light adjacent to it, but still it doesn't work.
    the way i made it as a general task is as follows:
    1. in the navigation area - select task 416
    2. In the right hand side, on Control Tab in Task properties, click on the Red button and maintain Agent assignment
    3. In Agent Assignment change attributes to General Task - instead of General Forwarding allowed.
    save and activate, and generate runtime version
    Is this correct or any other way?
    Thanks
    Usman

  • Installation of ODI with SQL Server 2005

    Hi
    I am trying to install ODI with MS Sql Server 2005.
    I created a database in Sql Server & created a user with db_owner rights for logging into the database.
    While trying to install Master Repository, i selected Sql Server with following details
    Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
    URL: jdbc:microsoft:sqlserver://<myhostname>:1433;SelectMethod=cursor
    The repository does not get created giving error:
    *com.sunopsis.core.q: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown*
    Now if i change the URL to jdbc:microsoft:sqlserver://<myhostname>:1433, the repository gets created successfully. But at the time of login into the topology manager using the same Master repository, it again prompts me the same error.
    Has anyone faced the same issue?

    Hi,
    You are using SQL server 2005 but trying to connect using the SQL server 2000 connection details you should be using
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    jdbc:sqlserver://ServerName:1433;databaseName=DBNAME;SelectMethod=cursor
    You will also need to make sure you are using the correct SQL server 2005 driver, if you are using a version of Java before 1.5 for ODI then you will need the SQL Server 2005 1.2 JDBC driver.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Result of Agent resultion doesnot agree with agents of task

    Hi,
    i am getting the following error for Zdecission task Result of Agent resultion doesnot agree with agents of task .
    This may be due to possible agents for task.
    where i need to do possible agents classification for task.

    You go to transaction Code
    PFTC->Standard Task->Provide respective standard Task->Change->Additional Data from menu->Agent assignment->Maintain->Create Agent assignment button top left
    Thanks
    Arghadip

  • Agent resolution does not agree with agents of task

    Hi Guys,
    I extended B.O-IDOCAPPL to ZIDOCAPPL to catch the inbound error for the IDOC.
    The workflow gets triggered correctly when we get the inbound error.
    In the workflow i created a custom display method....this is a dialog method. Now when the workflow comes to this point it gives the message in the technical log
    <i>" Result of agent resolution does not agree with agents of task"    </i>  
    <b>Now instead of calling this method if i just put a user decision it shows up fine in the users inbox.</b>
    I have tried SWU_OBUF , Refresh from SWUS , Refresh from Inbox
    Nothing seems to work, anyidea as to what's happening here ?
    Message was edited by:
            Abhishek Dhoundiyal

    I have tried :
    1.) hardcoding user ID
    2.) using a role
    3.) using WF initiator...
    This is set up as a general task......
    One interesting observation that i had... (If the below is irrelevant please ignore)
    If i run the task via SWUS it executes but still does not evaluate the agents.. and then if i execute the workitem in SWIA it lets me execute...
    Now if i trigger the workflow it executes but still does not evaluate the agents but it does not allow me to execute the workitem in SWIA , the technical log says workitem not found.

  • UCCX 8.0.2 - Call in stuck with Agent status ready

    Hi Guys,
    I would like know what is the best log about RTMT I can use to analyze the calls stayed stuck with agent. Was verified in Real Time Report that there are agent available (state ready), but, the call was transfered for queue.
    Thanks
    Wilson                  

    To find the root cause of stuck calls you need to Check MIVR/CCX engine logs
    below is the link to read MIVR/CCX engine logs
    http://docwiki.cisco.com/wiki/Guide_to_reading_MIVR_logs_for_Telephony_Issues_-_ICD_Call_Flow
    I hope this will help

  • ODI-01266: Agent {0} detected Session as stale session and set to error

    Hi
    I am a beginner in odi
    I scheduled a package to run . but this error came up :" ODI-01266: Agent {0} detected Session as stale session and set to error status"
    what is this error and what should i do???
    thanx
    medi

    Cleaning Stale Sessions
    Stale sessions are sessions that are incorrectly left in a running state after an agent or repository crash.
    The Agent that started a session automatically detects when this session becomes stale and changes it to Error status. You can manually request specific Agents to clean stale sessions in Operator Navigator or Topology Navigator.
    To clean stale sessions manually:
    Do one of the following:
    From the Operator Navigator toolbar menu, select Clean Stale Sessions.
    In Topology Navigator, from the Physical Architecture accordion, select an Agent, right-click and select Clean Stale Sessions.
    The Clean Stale Sessions Dialog opens
    In the Clean Stale Sessions Dialog specify the criteria for cleaning stale sessions:
    From the list, select the Agents that will clean their stale sessions.
    Select Clean all Agents if you want all Agents to clean their stale sessions.
    From the list, select the Work Repositories you want to clean.
    Select Clean all Work Repositories if you want to clean stale sessions in all Work Repositories.
    Click Clean to start the cleaning process.

Maybe you are looking for