Oracle Data Integrator (ODI) has good stability. It's much more stable compared to how it was ten years ago.

Oracle Data Integrator is a stable product.

ODI is stable and it's good to work with.

Oracle ODI is stable. 

Stability is good, better than 10g and 11g.

The solution is stable. 

ODI is very stable.

The product is stable if you have a working site. It offers great flexibility.

I rate the solution’s stability a ten out of ten.

Oracle Data Integrator (ODI) is a stable solution.

This is a very, very stable product. It's reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

At this point in time, we are not satisfied with the stability. However, this is not because of the solution, but because of the deployment which was done in 2017, and the maintenance and upgrades that needed to be done, which were not done over time.

The stability of Oracle Data Integrator is very good.

Stability-wise, I rate this solution a seven out of ten.

I've experienced no issues with performance. Since sky is the limit, you can do what you want to do within ODI in several ways.

It’s a perfectly stable product and we’ve not experienced any issues.

We used the solution, and we didn't have any problems with that.

I rate the solution’s stability a six out of ten.

The tool’s stability is good. I rate the stability an eight out of ten. We need to do a lot of engineering to understand the ODI mappings, knowledge modules, and how to load them. We need to learn a lot of other things, too.

There were issues mainly because of a Java memory leak.

It is pretty good.

Since we moved to the new version, ODI has been very stable, and we haven't had any unplanned outages. We only have had planned outages, I'm pretty happy with it.

The only issue we have had recently was when we patched ODI all the jobs that were supposed to be scheduled at 6:00, it ran seven hours earlier. It's a result of the patch. We were working with Oracle and they gave us a fix.

I've never had any issues with stability.

So ODI is actually quite a stable product. As a testament to the product team that develops it, they're not going to release something that is extremely buggy or things like that. So, I do see that often they will release features that are highly anticipated and highly sought after. And they might release them a little early. So there's definitely patching that comes into play there, to kind of get the full solution there.

As far as stability, the Oracle Data Integrator has agents that run either in WebLogic, as a Java deployment there, or on a server as a Java agent, or a Java deployment. As long as a client has had the product implemented, with no issues there. So that's kind of the key there, you don't want to have those agents have a blip or any issues.

Good.

The stability of the solution is pretty good. It doesn't crash or freeze on us. We don't have any bugs or glitches. 

12cR2 is a new version, and there are a few issues with stability, but I expect most to be resolved in the first patch.

When you start integrating products, it's not that stable. For example, if you upgrade other applications, like Hyperion Planning, it's going to break ODI.

We have had no issues with the stability.

I think that ODI 11g is very stable. I've had no issues with instability.

Any stability issues I've had, have been related to the data itself. It really depends on how whomever has implemented the product. If it stands up, it works well.

There have been no performance issues.

There were no issues with stability.

It is still not as stable as the old BI Apps and ELT tools were, but it's getting there. BI Apps doesn't come with the latest ODI yet, but in the future, it might be better.

I encountered many problems with the ODI web agent (service that actually executes all the integration tasks) in the 11g version, which was not stable. For this reason, I always suggest using the standalone agent instead of the web one, mostly due to the fact that they do not have significant differences.

ODI 12 version is very stable. It can manage several parallel executions/large volumes without much trouble.

The solution is stable. 

We've experienced no issues with performance.

Now that I am balancing my agent, it's been running for 2-3 months without any issues. It's been pretty stable. Prior to that, the agent was falling. I was having to check it all the time to see if the jobs ran.

One other thing that I would like to be improved – it might just be me, probably user error – is when I try to set up the feature to have it email me the notifications of what happened; I haven't been able to figure that out. I set it up but I don't get an email when it does fail.

We have had no issues with the stability.

So far it has provided what we need, it's working fine.

Migrating from 12.1.2 to 12.1.3 did not go as smooth as it should.

Sometimes the ODI agent shows running in WebLogic (middleware), while it cannot be reached by the ODI clients.

If it has a client that demands more thick clients than thin clients, that means that you need to give more memory and more CPU for your desktops that are also using those same resources.

We had issues with the early versions but lately the product is performing well.

There have been no stability issues.

A bit unstable and buggy in the 12.1.2 release, but most of it is fixed in 12.1.3, so I would definitely recommend to jump to that version.

We have had no issues with the stability.

It used to crash with large datasets.

The stability and performance are good and our customers use the solution on a daily basis. 

My impressions are good in terms of the stability.

The stability of the ODI studio is not strong enough. It crashes occasionally. 

We've experienced no issues with performance.

ODI is a proven product with high performance in large-scale data processing.

I did not encounter any stability issues.

No issues.

We've experienced no issues with performance.

When developing on huge internal repositories, the performance is often quite poor.

We have had no issues with the stability.

There have been no performance issues.