In terms of stability, I rate Oracle Identity Governance a seven out of ten due to some reported issues with the solution's stability. This is because Oracle's support is not as strong as its competitors in the market.

Stability is good.

Oracle Identity Governance is stable enough, even for large organizations.

Once you are in a production environment, Oracle Identity is stable however, every update is a risk and can be very time-consuming to apply the patches. 

The product is not stable and has issues even if conservation is managed accurately so it requires fixes and maintenance at the end of a project.

The stability of Oracle Identity Governance is good.  High availability has been implemented in each datacenter, failover is the DR solution.

The tool is stable.

Oracle Identity Governance is a stable product. It has many connectors, so you can plug it into many other products. You can do pre-processing, but you'll first need to do some programming, so stability wouldn't be an issue if that's taken care of. Oracle Identity Governance works well.

This is a stable platform.

Oracle Identity Governance is a very stable tool. It has good stability and my company didn't see any issues with it.

In our sandbox environment we had stability issues but only because all the components are on the same server. Once we worked out the kinks of first time R2 users, the platform seemed fairly stable.

Good!

Stability seems to depend on the day of the week. Overall, it's pretty stable, but it's software so, like anything else, it has problems.

This solution is stable. 

It's not so stable in our environment. It might have something to do with our old network. We're replacing the network now but it's very latency-sensitive.

Oracle Identity Governance is a stable solution.

This is a stable product.

Sometimes, it does not meet our expectations in terms of stability. I would give it a 3.5/5 for stability.

We've had some stability issues. We've worked closely with Oracle to resolve them. Just recently, we got performance issues. We're going to the new version. It was released last year. There are about a dozen customers that have it. We've discovered some performance issues. Oracle has worked closely with us. It's gotten to the point where it's ready to go. We're going live with it this weekend, the new version.

No, this has not been much of an issue for us.

We had some small issues with stability, particularly with memory leaks in some functions of this product. However, Oracle came up with the right patches.

Aside from a few bugs, Identity Governance is mostly stable.

It's very stable. Now, we do have it deployed with some high availability options on the back end, and we have multiple app servers, and that combination is very stable.

It's stable.

It's very stable. We haven't had any issues with instability that were big.

There are issues with stability in the long run.

No, we did not have any issues with stability, but it depends on how your system is integrated. If all requirements are integrated correctly, there should not be any issues with stability.

We don’t really have any issues with the platforms stability as it is up and running with minimal downtime that is caused by the OIM itself. I would rate the platform as very stable.

The current version is stable. Past versions have stability issues.

We've had very few issues with stability, I would say. But since we have the expertise and Oracle’s support to tackle from the product perspective, things are taken care of in such cases.

Once it is up and running it's okay, but it has many bumps.

They are always putting out fixes, but it's hard to get implemented without patching, so it's not great.

The stability is not a challenge. It depends on the size of the company. If we have one million users, it could be a challenge. But if you have up to 10,000 users, it's not a problem at all. 

You need to tune a lot because it's not a simple task. The product is not for everybody.I

Yes. First, the audit engine. They have not advanced their audit engines from where they started. In version 9.1 it was same issue on the JMS Queues. The audit engine was getting in to queues. I had two clients whose audit engine queue was more than a million. They were not able to process those records because the audit engine was taking too much time and the reconciliation and the amount of data which we used to import was huge.

And after getting in to a year of implementation or two years of implementation, UPA tables get to a stage where they are not able to process the records. We start getting timeouts while processing the records and Oracle was not able to troubleshoot the issue.

Second, is the availability. The moment you install Oracle Identity Manager, the biggest problem is system performance. Even if you go with 8GB or 10GB of RAM, eventually after a week or so, you need a restart for it to survive, even in production. You can see logs where things are failing and the server is responding very slowly.

These things happen often with Oracle but when you compare with SIM or SalePoint, you will not see the system usage or system CPU usage to that extent.

We had no issues with the performance.

This is a stable product, but the look and feel is not that great.

Once you get it working right, it turns out to be quite stable. 11gR2 PS2 can be considered as the first bug free stable release.

It was pretty stable. With the volume of data that we have at this point, it was stable.

Stability is as good as how you manage it. If it is in the hands of a bad administrator, it is only as good as how that administrator is.

We had some down time during the first release. We want to go to the next release. I spoke with the guys over there. It seems that it's easy to push the data that already exists in the new release. We will see. I think there will be more stability. We need to try.

Yes we did have issues with stability.

Yes. Every product has its drawbacks, and this one too has some stability issues. For these, either you could follow regular performance tuning, patch a bridge, or maybe use ESLs with Oracle.

The solution is stable.

One of the 5-6 consoles (Design Console) is a blast from the 1970's. It crashes constantly. The vendor is aware of it, but has stated that this is not a priority for them to fix.

Deployment of sandbox is a major concern, as its stability was underprivileged if implemented with multiple sandboxes from different out-of-sync locations.

Yes sometimes.

No issues were found related to stability.

We have had no issues with the stability.

Minor issues with stability and performance, but after tuning properly most of these were solved.

I did not encounter any issues with stability.

Password Sync had some issues, where some passwords from Active Directory use to fail while synchronization.

Stability is sometimes a challenge.

Yes, we encountered issues.

No issues encountered.

• We see a lot of Java exceptions in logs
• The task scheduler often doesn’t work.
• It loses its connection with BBDD clusters.
• We need to reboot the product very often.
• Data sources stop working after a few days of intensive use

Whether there are stability issues depends on the load of the system. Our system is a bit heavy and requires good hardware.

The product does have some issues with stability certain operations such as custom adapters and event handlers do not work properly.