Oracle GoldenGate

Well-suited to work between Oracle databases. I worked before at Bank of America and there we used this to replicate from Oracle database to Oracle database. We just replicate the whole schema and enable DDL replication. It is really convenient. Another good example is to use it for zero downtime upgrades. I also believe the active-active is very useful, but haven't tried yet.

It was well suited when replicating data from DB2. And able to map 100% mapping of the tables and integrity of relational database

Replication is awesome, transformation of data which is key for reporting purpose, handling multiple data sources and targets.

One of many use cases is, GoldenGate can be used in an active-active database configuration, meaning, both source and destination databases can be operational in a bi-directional fashion.

Oracle GoldenGate is most appropriate where a relational database replication is involved. However, with changing times and Big Data advancement, we are moving away from relational to more distributed databases (NoSQL). Oracle GoldenGate yet needs to become more sophisticated to be useful in NoSQL environments.

It is particularly useful in situations where ACTIVE DATA GUARD cannot handle the desired outcome. It can be used to support cross-platform migrations not supported by Active Data Guard which is a far cheaper solution to DR. It is suited for migrations that require zero downtime as there is bi-directional capability built into the product. It is also useful when the source and target are of different databases such as Oracle to SQL Server as the target. It is overkill if all you require is a physical standby that is open read-only.

The product is well suited for managing real-time replication between Oracle databases. It is useful for keeping audit trails on transaction logs. It is difficult to configure if multiple database products are involved like IBM DB2 or Microsoft SQL server.

Disaster recovery is the best need for us.

Migrations and reporting

Oracle to Oracle is a good choice, but not for DB2 to DB2.

It's good for replicating sources on multiple RDBMS into one or more targets' databases. It can read from online transaction logs and backups. Also it's good for performing certain ETL-type transformations so you [can] standardize your data in a reporting/staging area.

It's not good for the sole purpose of disaster recovery. You have better options (DataGuard and/or storage disk replication) for that.

Oracle GoldenGate is well suited to do exactly what we are using it for. We move data from Oracle to Postgres.

GoldenGate is well suited in combination with Oracle DBs.

I think Oracle GoldenGate is well suited for replication when you want the data, in whatever form, to be available on the other side in a very short amount of time, the two use cases that I'm most familiar with, bi-directional replication to support multi-site applications and uni-directional to support a reporting DB Platform are two instances where Oracle GoldenGate is very appropriate. I feel its limitations, such as data types supported make it a less than optimal choice for migrations, unless all of your used data types fit in to the currently supported data types. I also feel that it is not a good choice to replace Oracle DataGuard for Disaster Recovery implementations due to the data types concern.