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.

Tags: Business Intelligence

Similar Questions

Ask questions on the ODI agent?
Hello...

Based on my system, I've created about 50 scenarios and 6 ODI agent. Each of the agent of the ODI is treated approximately 8 scenarios. It comes to my setup for the ODI agent: -.

ODI_INIT_HEAP = 32 m
ODI_MAX_HEAP = 256 m

Based on my configuration, each agent ODI is then defined as 256 M.

My question is that one better if I use 1/2 agent basically MAX_HEAP or used 6 agent with the above configuration.

Please advise me...

TQ,
balleur
Go to the topology.
Physical architecture open / Agents.
Open your agent by double-clicking.
At the bottom left of the window, you will see the Maximum number of sessions. Set this value to 25 (or whatever the number)

When you submit more runs than that number already parallel execution, then ODI will be automatically queued for execution place in the order of presentation.

Press on apply. Restart your agent in the operating system. (ODI reads only the settings and schedules at startup. Appendices can be updated at other times perform the "Update calendar" button in the definition of the topology, or when the ODIUpdateAgentSchedule tool is used.)

Hope this helps

Where would the agent?
Hello

We currently have ODI 11.1.1.7 development environment on Windows 7 Professional and everything works fine. I am loading the data from SQL server using BCP and other windows controls are used in Interfaces.

I have to prepare my production environment on OEL 6.3 X86_64. I'm afraid that utilities in windows and OS commands will fail on Linux that these commands will be unavailable to the agent that runs on Linux. Someone you suggest architecture that runs on Linux and can also benefit from utility windows. I know that some utilities windows like MSSQL (BCP) is also available for Linux, but all of them we need will be available on Linux.

Second question is that we can connect to our work and the master repository hosted on Linux; and can do the development locally on ODI studio installed on any client windows then why do we need to install the studio on the Linux server?

Waiting for your kind answers.

Best regards
Muhammad
Again, you have reason. You can have a single agent specified by interface. In this scenario, you will need to ensure that the two utilities were on the server where the chosen agent is installed. In this case, you may have both the bcp & sqlldr utilities installed on each server and then run the interface this agent. Otherwise if limited by your environment you might break out the flow in the multiple interfaces using the utilities installed on different servers. Of course, this 2nd obtion would have any impact on the performance and it is dependent on your needs if this would be acceptable.

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.

Programming using the ODI agent?
Hello

I want to program an interface using the scheduling option in ODI11g. For this, I saw somewhere that I need to have the agent that is running. I was able to start the agent of
command line and run the interface. How can program the interface without going through this process. I also noticed that we can run as a windows agent
service in 10g. But I don't see any script or info for 11g. Any ideas on that?

Thanks in advance!

PM
If you do not want to start the agent command line then you can use OPMN to control agent - http://john-goodwin.blogspot.co.uk/2010/12/managing-odi-11g-standalone-agents.html
Your other option is to deploy the J2EE agent in WebLogic, but you would still need start the server managed by a mechanism for management nodes for example or manually create a one-stop service.
Once you have the agent running, you can simply set the interface/scenario of in the designer or operator.

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/

Location of the Agent of the ODI

I hope it's a simple question.
I have Essbase and planning on a Unix machine. ODI Studio is on a windows machine. If I install the ODI Agent on the windows box, I should be able to load to the correct planning and Essbase? Are there other necessary elements in the box of Windows ODI to connect with planning?
Thanks in advance.

Well are you talking about using the standalone ODI or one that comes with the FDMEE?

FDMEE install an ODI in the machine were you install the FDMEE.

If you install ODI agent in the Windows box, it should be able to talk to the planning & Essbase on Linux (you can also use the agent to stand alone).

End of the day, that the ODI studio connects to the database/schema & work-repository master to run the interface.

Make sure that apply you all necessary patches (in 11.1.2.3, it is mandatory to apply a patch ODI if planning is a target)

Kind regards

Deker P.

Cannot start the agent of the ODI JAVA EE on Linux

Hello
I have installed/configured EMP 11.1.2.4 on exalogic (VM linux 5.8). When I start my services I get everything right except agent ODI; It does not start and when I try to start from console FUSION EM I get this error
[Deployer: 149034] An exception has occurred for task [Deployer: 149026] start application oraclediagent on ErpIntegrator0. : [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: "oraclediagent."
I checked on the oracle support and they say that we must change the binding order. I changed the binding order by twisting in files located in /etc./sys-config/network-scripts. But I still get the same error.
My questions are,
1 - is the right way to change the binding order?
2 - How can I see which NIC is chosen by the agent of the ODI; is there a way I can change the NIC ODI agent chooses?

Concerning
Note: Please see the bulletin first response to show my ifconfig file.

Thanks for the help guys.

I am able to start the ODI agent with the help of oracle support.

Enter these lines in

Start WLS_Admin_Console-> domain_name-> Servers-> ErpIntegrator0-> configuration-> Server-> Arguments:

'- Doracle.odi.coherence.wka1 =server_ip - 9088 = Doracle.odi.coherence.wka1.port - Dtangosol.coherence.localhost =server_ip - Dtangosol.coherence.localport = 9088.

without the quotes. Restart the server of the ERPI.

Concerning

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 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/

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

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/

Agent of the ODI and repository
Hello

I would like to know what exactly the role of agent of ODI and repository?
If I create a new ODI environment using an OLD having slight chages to target database can I use the same Agent to two repositories of th?

Thank you
Mahesh
How to create data servers and how do I use it?

In terms ODI, database server is connecting to one or multiple data store present under a connection.
You need to create the server from the topology data.

You must create a physical database server where you must provide the physical connection information.
You must have a logical data created authentintion that will connect to the physics dataserver via a given context.

Installing TB31.3.0 on a W8.1 workstation; I want to delete the messages on the user agent of TB, but prevent deletion on the server. Where is the switch? When to install

Hello!

I have already installed a TB user agent on my workstation 'primary': I can create, read, and DELETE messages ON the workstation and the server.
I want now to install a user of TB on a "secondary" workstation agent, where I can create, read and DELETE messages on the workstation. But I don't want the secondary workstation to delete messages on the server. (In short: I want that the function "delete" ONLY allowed to my primary workstation).
Is this possible? Where is the switch ON / OFF? (For example, this feature is available on the agent on my WindowsPhone).
When I install it?

Thanks for your support!
Rgds
Flamboyant

Using Thunderbird on your second workstation - the only option would be to create a Pop email account
so before you download anything, you must configure the account settings to "leave a copy on the server.

Tools > account settings > account for Pop mail server settings.
or
Menu icon > Options > account settings > server settings
- Letter: look for the e-news at startup
- Letter: arrival of new messages every xx minutes
- Select: automatically download new messages
- Letter: Leave messages on the server '
- Click OK
E-mail POP accounts can only download the mail from the Inbox server.
This will allow you to remove off the coast of the secondary workstation and leave it on the server.
However, Pop cannot see or download other folders on the server: IMAP only can see other folders these are read remotely. But in IMAP because records are a same as server, removing in TB will remove also off server.

location of the journal folder of ODI odi agent installed in weblogic server 11g

I installed odi in a weblogic server. So, I use a Java EE officer. Workload ODI newspapers get generated in the agent folder. Could you please tell me the location of the folder of the agent in this situation. The ODI 11 g is used for BI Oracle 11.1.1.8.1 applications.

Hi 2782749,

I think BI Apps use FOAD: http://docs.oracle.com/cd/E25178_01/core.1111/e10105/logs.htm

But I think really that it would be easier to retrieve the result of the execution of the repository.

What are your needs?

Do not forget to close your other topics (comparison of interfaces, email exception, several master repository, the ETL statistics,...)

Kind regards

JeromeFr

where would the ODI agent

Similar Questions

Maybe you are looking for