Oracle GoldenGate Reviews

Our primary use is to transfer data or tables in databases from one server to another.

GoldenGate can connect and collect data from multiple sources, such as SQL Server.

There are some DDLs that have problems with GoldenGate. These issues detract from stability and it is something that should be improved.

I would like to see the interface more graphical and easier to use. I like Microsoft products, for example, because they are easy to use. When I work in SQL Server, which is integrated with Oracle GoldenGate, I find it better to work in than Oracle.

We have been using Oracle GoldenGate for the past three or four years.

GoldenGate is a stable product.

Usually, it works with no problems. Sometimes there are issues, but we have been able to solve them.

It is easy to scale once you learn it.

This product has been working well in our environment so we haven't had the need to contact technical support.

The initial setup was straightforward. It took three or four months to complete.

The implementation was done by the Oracle team.

My advice for anybody who is considering this product that its suitability depends on the environment. If Oracle is being used then it is a good solution but otherwise, another product would be a better choice. I would suggest using a solution by the same vendor as the database that is being used.

I would rate this solution an eight out of ten.

On-premises

We implement this solution for our customers, and our most recent deployment was for a client in France. The solution involved one central database and ten replicas that were distributed to the local offices. The central database is automatically updated as the replicas are changed, and similarly, when the central database is modified, each of the local copies is updated accordingly.

Using this solution has improved both the speed and efficiency of the data replication process. Prior to this, I used packages with merge functionality for replication. The process was very slow, and sometimes had negative effects on the production database. This solution provides us with real-time replication and it does not affect the performance of other operations, which is very important to us.

The most valuable feature is the CDC (Changed Data Capture), which captures only the changes that are made to the data. This has the lowest load on the production database, and it runs very quickly in the background.

Reading directly from the log file makes updating the databases very fast.

I find the user interface to be difficult for non-technical people. It was suggested to me that I use the command prompt, which is fine for me because I am a technical person. However, when showing others, such as managers, how to use the product to provide details such as the system status, it is a bit difficult.

The inclusion of monitoring and management tools would be very nice.

The Oracle documentation is very complex, and some of the documents are very long. I prefer to use sites that are on the topic of Oracle, but in fact, are not run by Oracle itself.

In our experience, there is zero technical support for this solution.

Between four and five years.

This is a very stable solution, and I haven't had any problem with the tools.

This solution scales easily. It's dependent on the files and configuration, and you can do anything you want.

This solution is being used on a daily basis. We have approximately one thousand users on the production database, including both developers and end-users. We do have plans to increase our usage, although the interface for monitoring and managing becomes difficult to use when it grows to a certain point.

I have contacted technical support, but could not get any support. I would say that the support is zero.

Prior to this solution, we had a package that used an SQL process. It had come from Oracle Scheduler. We switched because it negatively impacted our production database, making it very slow. If there was downtime and the production database had transactions then it would take days to recover from the lag.

The initial setup of this solution is of medium difficulty. It is not straightforward; however, it is not as complex as it looks.

For a single deployment that has two sites, I would expect the process to take less than two hours, although it depends on the complexity of the replication.

An example of a more complicated configuration is where only a subset of the tables are being replicated, and the flow of data is different in both directions. Setting this up can take a very long time, and incur a large cost because of coding time.

We have three people to manage and maintain this solution. This includes making changes to the database. For the monitoring and altering, one person is sufficient and it will not take one hundred percent of their time.

We handled the implementation of this solution in-house.

We do like the price of this solution.

We did not evaluate other options when we chose this solution, although I am now considering other tools.

This solution is priced well, is fast, and doesn't have any impact on our production database.

I would rate this solution and eight out of ten.

The primary usage of the product is to transform data from one database to another, for an application.

If you have one environment that is for some application and it has a lot of data, and you need this information not only for the application but also for a warehouse - to do some analytics later - you just transform all that data to the warehouse and then you can work with it.

You can put data together from a few databases into one database or the other way, from one database into several. It transforms data in real-time. In my experience, it is able to transform a large amount of data within a few seconds.

I would like it to be simplified, easier to manage.

This is the tricky part. It's stable but you have to know how to maintain it. That's why it's not 10 out of 10 for me. There are some bugs, there are some issues here and there. All of a sudden your process is not working and you have to figure out why, and sometimes it's not so clear.

Maybe they can simplify it. You learn the tool, you learn how to work with it. Now we have a very stable environment but it took like a few months until it became stable.

You have scalability. If you have a database and you have all sorts of objects inside and you want to transform them, you can add more objects.

I would recommend Oracle GoldenGate, of course.

• Replication by SCN
• Ability to perform basic data transformation/call user-defined functions
• Exception handling
• CDC capabilities when used with ODI

• Ability to implement zero-downtime migrations
• Ability to scale horizontally
• Ability to use ODI and Goldengate for real-time ETL

Current features:

None

New features:

Offer basic process monitoring out-the-box

Offer a (CLI) wizard for quickly creating and configuring (extract, pump, replicat) table replication

3 years

Base versions where a bit buggy particularly during recovery after there were machine/host crashes or unexpected shutdowns. Latest patches/versions resolved these issues.

Only in Windows were there a few GoldenGate crashes, but we suspect these were due to insufficient memory.

No, although we haven't applied parallelism to any of our processes yet.

Customer Service:

Very good. I have often spoken directly with support personal and P1 issues are handled swiftly.

Technical Support:

Excellent for above P3.

Straightforward

Initially through a vendor, Michael Rainey from RittmanMead, and we were able to support the product on our own after that. Michael's level of expertise is very high.

Hard to calculate, but GoldenGate offers an excellent ROI if you use the product cleverly.

NA

No

Reduce the price to compete with products like DBVisit because once customers see the power behind this product, they will be locked in forever.

We are a reseller, and we implement this solution for our clients. They are generally either government or financial institutions. These clients use other Oracle technologies for tasks such as identity management and business intelligence. This solution is used to replicate the data for purposes such as disaster recovery and high availability.

The most valuable feature of this solution is data replication. When we are replicating data between similar databases then it is straightforward.

We are having a challenge in that we want to replicate different types of data, from one database to another, that have different types of elements. The process of transforming the data between two different databases is inefficient and needs to be improved.

Technical support for this solution could be improved.

The integration is not straightforward and should be made simpler.

We have been using this solution for two years.

This solution is stable and we aren't facing any issues.

Scalability of this solution depends on the licensing from Oracle.

We have had trouble with the Oracle technical support. When we need them to reply to us, we need to open a 24/7 ticket. If we open a critical ticket instead, then nobody replies and it takes a lot of time. Consequently, whenever we are facing an issue and we need to open a Service Request (SR), we use the 24/7 support. This leads to three people working in parallel to resolve our problem. Otherwise, we will not get a resolution.

The initial setup of this solution is straightforward. For the installation, you need only follow the steps in the documentation.

There are a lot of tricks when it comes to licensing.

This is a good solution for data replication, but there are some areas that need to be improved.

I would rate this solution a seven out of ten.

This product is meant to replace Oracle's Data Guard replication. The setup is simple and it can handle bi directional replication very easily. Training cost is minimal and most DBAs self learn this product. replication between various types of databases is supported and software foot print is very small . Change trails are not very big and easy to manage and store.

DDL (data definition language) replication is still to mature and can be an issue. Supplemental logging causes extra redo log generation in the log storage. Licensing cost is higher as compared to other replication products. Configuration of Golden Gate in HA (High Availability) mode needs setup of extra VIPs which can be challenging in a RAC environment.

Integration of Golden Gate with monitoring tools like OEM (Oracle Enterprise Manager) is still not available and most DBAs monitor this with custom scripts. We chose this product mostly on it's bidirectional replication feature and easy setup. Some applications are using this as a messaging mechanism between multiple databases.