Establishment of an ODI Agent

Hello

I followed this tutorial to create an ODI Agent.
http://St-curriculum.Oracle.com/OBE/FMW/ODI/odi_11g/Setup_ODI_Agent/Setup_ODI_Agent.htm

I m of the problems on the password stage encodes.
I m this error:
http://ImageShack.us/photo/my-images/269/encode.jpg/

I'm doing something wrong?

In the Environment Variables, I have the following settings:

ODI_JAVA_HOME: E:\Hyperion\jdk160_21
Path: E:\Hyperion\jdk160_21\bin

Thank you

Ruben

Published by: Ruben on Set/16/2011-01:52

I am happy that I was able to help.

If everything is resolved, remember to mark the "correct" answer and the thread as "answered".

Thank you.

Tags: Business Intelligence

Similar Questions

ODI agent oracle and mysql

Hello.
I use 11.1.1.7.0 ODI, I supported oracle and mysql, ODI workflows configured ODI agent to help odiparams recognize the oracle drivers and I was able to start the workflow [without the guests and the agent is able to invoke automatically]. However, in odiparams, can we specifies the mysql drivers both oracle with credentials and start the agent?
Please advice how to do? I need odiparams configured to manage the agent for mysql and oracle drivers and must call workflow ODI without a manual.

You simply add jar drivers required for the drivers directory and you can use it in ODI agent

read http://docs.oracle.com/cd/E28280_01/install.1111/e16453/configure.htm#ODING297-

3.1.1 adding additional drivers and tools Open to autonomous Agent and ODI Studio

Install the new FDMEE 11.1.2.4 - ODI Agent does not start

After the installation and configuration of EMP 11.1.2.4, components (including the FDMEE) on a Windows 2008 (single-server installation), I ran diagnosis of EPM system and found the only test that failed was to the Agent of ODI.
ODI Agent availability check: http://server1:6550 / oraclediagent
Error: com.hyperion.cis.utils.BadResponseCodeException: bad response with the GET method code: 404
Recommended action: check the application of the FDM Enterprise Edition is started and the database schemas exist.
FDMEE and all the other components of the EMP seem to work and open in the workspace. The only problem is that ODI Agent will not start. Re-installation and configuration of FDMEE has not fixed this problem. I also tried to start manually in the WebLogic administration server, but it has not started and I found the following error in ErpIntegrator0.log.
# < 18 June 2015 3:47:13 AM PDT > < error > < hats > < server1 > < ErpIntegrator0 > < ExecuteThread [ASSET]: '9' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1434624433908 > < BEA-149265 > < error has occurred in the execution of the request for deployment with the ID ' 1434624127664 'for task ' 0'. Error is: "weblogic.application.ModuleException: [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: 'oraclediagent'."
com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
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)
to 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)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
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)
to 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)
to 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)
to 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)
to 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)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
'
weblogic.application.ModuleException: [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: "oraclediagent."
com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
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)
to 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)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
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)
to 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)
to 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)
to 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)
to 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)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
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)
to 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)
to 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)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster
Set of members = MasterMemberSet)
ThisMember = null
OldestMember = null
ActualMemberSet = MemberSet (Size = 0
)
Member ID | ServiceVersion | ServiceJoined | Member State
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)
to 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)
to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
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)
to 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)
to 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)
to 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)
to 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)
in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)
to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)
to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
# < 18 June 2015 3:47:13 AM PDT > < error > < hats > < server1 > < ErpIntegrator0 > < ExecuteThread [ASSET]: '9' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1434624433916 > < BEA-149202 > < encountered an exception while trying to commit Task 7 for the application "oraclediagent". >
During my research of these errors, I found results indicating the problem could be related to multiple NIC cards or enforceable, but I don't know if this is the reason of my problem and how to check it. Any help would be appreciated!

In your case, it seems that the list of the WKA is formed using the IP 127.0.0.1 loopback address but consistency has bound to the IP address of 10 points. Finally, make sure that they match so that ODI Agent can start, but given that it's a DHCP box you well then that tends to add another layer of complication.

What we tend to do in support with DHCP boxes to avoid problems with name resolution is to simulate a static IP address by adding a loopback adapter (google, you can add a loopback adapter Server 2008 for instructions) with a static IP address (I often use smth like setting IPv4 10.10.10.10 (, netmask 255.255.255.0 & no gateway) then add an entry to the hosts file to map the IP address for the host name of the host name for example, 10.10.10.10

You must make sure that the host name resolution works as expected in Java according to this link as well (which I think is why we go to the "loopback hack" first place in support): https://docs.oracle.com/cd/E40248_01/epm.1112/epm_install/frameset.htm?ch06s02s01.html

I would start by looping config tbh as I remember seeing someone with a box of AWS, earlier when helping a colleague where host name resolution was not working with that tool and they had problems with the Agent of ODI.

Concerning

Craig

FDMEE requires ODI agent for simple file loading?

Hello
I have my agent ODI isn't working because of a problem with OS. I am trying to upload a simple file using FDMEE. When I try to run data load rule he says this ODI agent fails.
My question is:
FDMEE requires ODI agent even for simple file loading? FDM does not require us agent of ODI for simple file loading.
Concerning

Yes, as I mentioned in my previous post THAT FDMEE is built on top of the ODI, so she run ODI scenarios for all flows of integration

How to change the name of the ODI agent and port number

I installed ODI standalone agent (11g) on a linux server. We now realize that we need to change the name and port number of the agent. Is it possible to change these or do we need to re - install odi agent?
I know that I can change the name in the ODI, but I can't change the port number. I would like everything to be consistent in all of our environments. That's why we need to change the name of the agent and the port number.

How do you start the agent? Which command you use to start?

There are two ways, either by directly calling agent.bat and passing name agent and port don't start or you can run the sh/bat file created during installation (present in oracledi\agent\bin). The file name that is created should look like this (agent_localagent11g) where localagent11g is the name given during installation time and 'agent' is the prefix that was added by ODI.

There is no configuration file to configure the port number and agent. Make sure that the port number and name you pass to agent.sh must match what is configured in odistudio.

Agent.bat '-PORT = 20910 ""-NAME = localagent11g.

ODI agent cannot connect to the ODI Studio

We install ODI via subsequently EPM using FDMEE. We have installed using the version 11.1.2.3
We can connect via Studio ODI and surf around. We started seeing a problem where we can't get into some places. Especially if we try to select Show agent planning, we get a message unable to connect.
, We looked at the log file and find the following line. ODI-1424 host Agent or the port can be reached using http:// xxxxxxxxx
What we have noticed is that the URL it uses is the original no SSL url. So, my question is where this configuration change? Since then, we have installed an ODI via EMP/FDMEE I don't know where to look for the configuration.
We tested the same on our environment no SSL is enabled and it works without any problem.
Any help would be greatly appreciated.

A patch that you run of FDMEE, the reason why I ask if dans.520 default because what follows is fixed

18547248

FDMEE connects to the port ODI Agent evil in a SSL configuration is enabled.

See you soon

John

http://John-Goodwin.blogspot.com/

Not able running Maxl, if ODI Agent is running under & managed by OPMN

Error thrown when in the execution of Oracle Essbase Interface Inteface using IKM SQL for Hyperion Essbase (DATA) and by calling a MAXL clear script in PRE_LOAD_MAXL_SCRIPT.
Execution of the Interface is done correctly if the same agent ODI runs directly from the command prompt (using agent.bat). But when we start the agent the instance of OPMN, the following error:
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: cannot run the program "essmsh": CreateProcess = 2 error, the system cannot find the file specified
The agent of ODI running fine and complete any execution of the interface without MAXL. But if we use PRE_LOAD_MAXL_SCRIPT, it generates an error.
We have already created two environment variables such as ESSBASEPATH and ARBORPATH, also set to day the Path variable. We are able to start maxl using the command "essmsh" directly from the command prompt.
I would like to know how can we call MAXL scripts through successful ODI agents OPMN.
All the suggestions/help will be appreciated.
Thank you!!

Hi Ashish,

Some time ago I saw it, so I forgot a few other env variables that must report in opmn.xml. It also needed a little more env vars the overall environment for OPMN is very limited. You can try the steps Note 1556801.1 as well. If all goes well, that should do the trick.

Concerning

Craig

ODI Agent for a repository created in ODI Studio

Hello world
I will say that I know very little of the ODI agents. Sorry if my question is stupid!
I followed the instructions in "http://docs.oracle.com/middleware/1212/odi/ODING/configure_jee.htm#BABHADCA" to create a repository using the RCU tool and the rest of the configuration required to install an agent. And's done it successfully with deposits created by the remote control.
I have another repository that is created using the ODI Studio itself as well as a project on this subject. How can I install agent on this repository? I want to say creating repository using ODI Studio creates all necessary diagrams? Or should I use the instructions in the document and then import my project on the new repository?
Thank you

Hi elebal,

You will need to ensure that appropriate schemes have been created for the Agent of JEE (assuming it's the agent that you are interested in the configuration). See the screenshot to the company's facility, which shows the necessary schemas and 3 creating the Oracle Data Integrator Master and referential work (12 c (12.1.2)) scheme . If they do not already exist in your repository, just run RCU to add. You should not recreate the ODI repository, as it already exists.

Kind regards
Michael Rainey

ODI Agent as a Windows service
Hello

I am trying to create 11.1.1.6 ODI agent as a windows (jhon followed blog) services but fail with errors below.

Opmn configured OSH of Hyperion 11.1.2.1.

(I am able to configure in 11.1.1.5 but I hope that there is no difference in 11.1.1.6 of ODI)

ODI-1604: unable to parse the Xml extracted from Opmns
ODI-1600: cannot update Opmn Xml file.java.io.FileNotFoundException: C:\Oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin\Oracle_Ho
me Directory\oracledi\agent\bin\odi_opmn_standaloneagent_template.xml (the system cannot find the path specified)
ODI-1600: cannot update Opmn Xml file.java.lang.NullPointerException
opmnctl reload: reconfiguration opmn...

Here are the updates in the files

agentcreate. Property

ORACLE_ODI_HOME = directory Oracle_Home
INSTANCE_HOME = INSTANCE_HOME directory
Component_type = odiagent
NAME OF THE COMPONENT = ODIAGENT
ODI_MASTER_DRIVER = Oracle.JDBC.OracleDriver
ODI_MASTER_URL=JDBC:Oracle:thin:@xyz.ABC.com:1521:dev
ODI_MASTER_USER = ODI_Repo
ODI_MASTER_ENCODED_PASS = e3yHXTyLvogAGJYiddyU4ZVg
ODI_SECU_WORK_REPO = WORKREP
ODI_SUPERVISOR_ENCODED_PASS = d, yHvBA9Vb79z3f4w86cnZ0Fa
PORTNO = 20910
JAVA_HOME=C:/PROGRA~1/Java/JDK1.6.0_33
ORACLE_OPMN_HOME = D: / Oracle/Middleware/Oracle_WT1
JMXPORTNO = 21910

odi_opmn_addagent.bat

If "% ODI_HOME" == "" set ODI_HOME=C:\Oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent
REM call '% ODI_HOME%\bin\odiparams.bat '.

If "% OPMN_HOME" == "" set OPMN_HOME = D:\Oracle\Middleware\Oracle_WT1
If "INSTANCE_HOME %" == "" set INSTANCE_HOME = D:\Oracle\Middleware\Oracle_WT1\instances\instance1

REM set CLASSPATH = % ODI_CLASSPATH %; frequency PMN_HOME%\opmn\lib\opmneditor.jar
Set CLASSPATH=%ODI_HOME%\lib\odi-standalone-agent.jar;%O PMN_HOME%\opmn\lib\opmneditor.jar;%O DI_HOME%\...... \setup\manual\oracledi-sdk\oracle. ODI - SDK - jse_11.1.1.jar

Java - classpath % CLASSPATH % oracle.odi.AddAgentToOpmn % *.
I tried it today, it works well, in general, the problem is caused home do not set correctly.
on the platform of the window for all roads please use / not--------.

odi_opmn_addagent.bat
If "% ODI_HOME" == "" set ODI_HOME =...
REM call '% ODI_HOME%\bin\odiparams.bat '.

If "% OPMN_HOME" == "" set OPMN_HOME = C: / Oracle/Middleware/Oracle_WT1
If "INSTANCE_HOME %" == "" set INSTANCE_HOME = C: / Oracle/Middleware/Oracle_WT1/forums/instance2.

agentcreate. Properties
# Use / as a separator of path to specify the path in Unix and Windows.
ORACLE_ODI_HOME = C: / Oracle/Middleware/Oracle_ODI1
INSTANCE_HOME = C: / Oracle/Middleware/Oracle_WT1/forums/instance2.
Component_type = odiagent
Name of the component = myagent
ODI_MASTER_DRIVER = Oracle.JDBC.OracleDriver
ODI_MASTER_URL=JDBC:Oracle:thin:@jjpeng-Lab10.us.Oracle.com:1521:oditest01
ODI_MASTER_USER = jini_01pfx
ODI_MASTER_ENCODED_PASS = hpfX, DC, hJLYSgD.m, LnNr9zf
ODI_SECU_WORK_REPO = JINI_01PFX_WORK
ODI_SUPERVISOR_ENCODED_PASS = hpfX, DC, hJLYSgD.m, LnNr9zf
PORTNO = 9787
JAVA_HOME=C:/java_64bit/JDK1.6.0_29
ORACLE_OPMN_HOME = C: / Oracle/Middleware/Oracle_WT1
JMXPORTNO = 21910
PROXY_PORT = 98767
MASTER_REPO_EXTERNAL_ID = 1329894428167

ODI Agents version 10 and 11
Hello fellow users ODI.

I don't install ODI frequently and I do not install the ODI Agents frequently either. I want to what has changed about the installation agents.

==================

In April 2010, I installed agents and here are my notes for the process:

1 edit the 'odiparams.bat' file in the \ODI\oracledi\bin directory. There are some notes and directives in the file. It is important to put the environment at the good MASTER repository as follows:

REM
REM the Repository connection information
REM
Set ODI_SECU_DRIVER = oracle.jdbc.driver.OracleDriver
Set ODI_SECU_URL=jdbc:oracle:thin:@pax401ce032:1523:hypbgprd
Set ODI_SECU_USER = ODIM
Set ODI_SECU_ENCODED_PASS = hZyHWYZQhuThIa8ge32UYf
Set ODI_SECU_WORK_REP = PROD
Set ODI_USER = SUPERVISOR
Set ODI_ENCODED_PASS = hZyHUQyZV.V6N4tzMspFRr

2. start the Agent listening and planning as a Windows Service

AgentService - i - s PROD_ESSBASE 20910

3. make the appropriate topology changes and to verify that the agent is running correctly

==================

So now its December 2011. I heard about our infrastructure consultant that the agent is no longer running as a service as we have defined above. I also read on the deployment of the Agent of the ODI as Java EE Application as described in the following link.

http://www.Oracle.com/WebFolder/technetwork/tutorials/OBE/FMW/ODI/odi_11g/setup_jee_agent/setup_jee_agent.htm

==================

Here's what I want to know:

1: how many ways can I deploy the agent for ODI_11g? (I see not the command "agentservice" more.)

2: is there a simple way to run the Agent of ODI as a Windows Service?

3: I remember the old agentservice to be rather meager in terms of memory usage. Does this new J2EE / WebLogic service use more memory?

Thanks for your thoughts.

-Chris Rothermel
Yes it is about the correct summary, I can't really comment on the use of memory by using the agent Java EE that I have not really had to use.

See you soon

John
http://John-Goodwin.blogspot.com/

QUESTION: Extracting data Essbase and ODI Agent installation?
To extract the data of Essbase cubes, ODI has 'LKM Hyperion Essbase DATA to SQL'.
We can use (1). ReportScript, or (2). An MDX query or (3). CalcScript

For the extraction of data by using CalcScript, ODI Agent must be running on the same server as the Essbase server.

Anyone know if there is a need for ODI Agent on the Essbase machine if we use the method of MDX query for the extraction of the data?

We would like to avoid the installation of Agent ODI for Essbase-extraction of data.

.
It's just for the Calc script method because it has access to the exported file, you should be fine with the other methods.

See you soon

John
http://John-Goodwin.blogspot.com/

QUESTION: Extracting data Essbase AND the ODI Agent installation?
To extract the data of Essbase cubes, ODI has 'LKM Hyperion Essbase DATA to SQL'.
We can use (1). ReportScript, or (2). An MDX query or (3). CalcScript

For the extraction of data by using CalcScript, ODI Agent must be running on the same server as the Essbase server.

Anyone know if there is a need for ODI Agent on the Essbase machine if we use the method of MDX query for the extraction of the data?

We would like to avoid the installation of Agent ODI for Essbase-extraction of data.

.
It's just for the Calc script method because it has access to the exported file, you should be fine with the other methods.

See you soon

John
http://John-Goodwin.blogspot.com/

ODI agent and virtual servers (VMWare)
Hello

We plan to move on to virtual servers (product VMware) in the near future.

Anyone had experience ODI agent running on a virtualized server. I can't imagine all the problems, but Oracle does not specificallly supports running on VM Ware (because they have their own VM product!).

Wondering just if theres someone out there who has tried this?

Thanks for looking
I agree, ODI and agents running on VMWare without any problems on many occasions.

See you soon

John
http://John-Goodwin.blogspot.com/

ODI Agent startup failure
Hi all

I installed and configured ODI 11g I've done as a result of tasks

(1) created Master repository
(2) user connected to the ODI
(3) created work Rep
(4) created both physical and logical agent

Until I started agent I've done as a result of tasks

1) updated my ODI PARAMS

Updated master Rep info:
Updated my relational db information associated with master rep

Encode the password:
My main repository is ODI_MASTER and password password1

Command: encode password1

I've updated my ODI params with the new encoded password

Similarly, I have updated the coded SUPERVISOR password.

I have udpated my info from repository work as well.

But when I start the agent from the command line, I get 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 ODI-1128 NOTIFICATION Agent PRODAGENT begins. App
Planning Server: AUTONOMOUS. 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 PRODAGENT Agent encountered an error: ODI
-1404: agent PRODAGENT start failure: an authentication error occurred when con
momentary to the master repository.
2010-11-01 12:50:07.771 unavailable WARNING
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 wrong at any point.

Thank you
KRK
Error Message - Agent PRODAGENT start failure: an authentication error occurred when connecting to the master repository.

KRK please re check in the odiparams if the ODI_SECU_USER and the ODI_SECU_ENCODED_PASS are correct and also if you are using the correct ODI_SECU_URL
Also did you set the agent in the topology with the same PHYSICAL NAME of the AGENT - PRODAGENT and port no-20910?

where would the ODI agent
Where would the ODI agent. In Source Server or target

App
The reason to be on the server target, is that since ODI creates the C$, I$ and also the target tables. ODI may take some time to read from the Source Server, but once done its will empty into the server target and when the performance will be faster since all other operations, processing will be done on the server side target making the action faster else if the agent is another place that it might have to travel a lot in terms of network resources. So its has suggested to go to the server target for the creation of the Agent.

Establishment of an ODI Agent

Similar Questions

Maybe you are looking for