Oracle GoldenGate

Oracle GoldenGate is used as part of our business continuity plan. We use it to replicate in near realtime, transactions from the primary database to the BCP copy of the database. We also use it to maintain a reporting instance of our transactional database so we can offload read-only type queries in order to minimize performance impacts on the transactional database. We are experimenting with using GoldenGate to perform some transformations for us so that we can create data marts for various teams within the organization. That is still in the POC stage.

<p>GoldenGate (GG) is being used by the utility company I work for in various areas. </p> <p>Data Analytics is the main use of GG at the moment. Normally, the sheer level of database hits required by our daily Business Intelligence reports would place a heavy burden on the disk groups in our core ASM; however, with GG, we are able to seamlessly replicate that data in real-time into a separate database using separate resources. By doing this, we are able to alleviate potential bandwidth issues posed by our BI group’s database querying. It should be noted that GG does not require all tables to be replicated: we only replicate under 100 of the thousands of tables in the main databases. Our GG database is not normalized, so we are essentially combining disparate databases into one, which has its advantages and disadvantages.</p> <p>Another use we currently have for GoldenGate is on a large project level. As part of a data conversion effort, we are using GoldenGate to replicate data into a separate database in real-time. This will allow us to save 12+ hours during our conversion, as well will not need to execute an RMAN backup in order to move data into our target database. In other words, we are directly replicating data into our target database, so right when we are ready to switch servers/databases for the go-live of our project, we will be ready to immediately start to convert data.</p>

Our company in EMEA region has two data centers, working in the Active/Passive(standing by) mode. We use Oracle GoldenGate to "clone" the live data transactions from the master database (which resides in the currently active data center) to the standing-by database (which is in the limited read-only mode, and resides in our passive data center). If the active DC is down and DR is required, the standing-by database in the passive DC will be promoted to the master one which can take R/W transactions, and the OGG will reverse the uni-direction data copy. This pattern is applied on all business critical IT application's DB instances.

Currently [Oracle] GoldenGate is being used to replicate a backup database for disaster recovery and also integrating different data sources to a single database.

Oracle GoldenGate is being used by the departments as required and as needed. Especially we used for migration purpose. We are migrating the databases from on-premises to Cloud. The real problem is to complete the migration with zero-downtime. We need a revert plan (rollback strategy) when it fails. [Oracle] GoldenGate helped a lot in completing this migration task with Zero-downtime. [Oracle GoldenGate] is real-time data capture, continuous delivery of transaction data across different sources.

We implemented Oracle GoldenGate on at least 400 database environments. We have a large infrastructure with tons of applications to assign installation and repair jobs to field technicians. In some of the applications, we can't afford latency or replication errors. GoldenGate has been a great tool.

Oracle GoldenGate is used in a traditional manner for homogeneous data replication between production and non-production environments. This allows the different environments to be utilized for different purposes with the same source data. Some environments are for real-time data analysis while others are backend reporting and analysis.
Oracle GoldenGate allows us to split highly responsive, mission critical systems from lower environments while retaining clean copies of source data.

It's used by our Computer Services Department to create reporting databases as well as for DR. The replication is unidirectional and replicates data in four non-production environments. This enables us to perform long-running queries without affecting the performance of our production systems. We have a lot of clients using it. It can migrate data between databases in realtime.

Oracle GoldenGate is being used by our core software development team. We are using it as a real-time data replication solution to achieve high availability/disaster recovery for our data, to prepare a read-replica database to offload query-based requests, and to perform real-time business intelligence related operations on our synced data.

We use GoldenGate to sync up data from our customer and care system to Oracle Analytics Database

We use it for our core system to support our main database for courier services. The core system is used by all of the operations and sales teams, as well as the Board of Directors. All of the transactions should be backed up and maintained in our backup servers as well as our disaster recovery. We use GoldenGate to replicate our database.

GoldenGate is being used as a DR solution and as well as a method for replicating from a transactional to reporting DB. It is used across the whole organization. It addresses a need for disaster recovery on different data centers including the cloud.

We use Oracle GoldenGate for multiple reasons such as data replication, to maintain active/active databases for critical applications and not but least for database migration with zero downtime. We're happy with the usage and its purposes. It is being used across the whole organization. We use OEM monitoring to alert the monitoring team when there is a lag on the DB sync.

Oracle GoldenGate is used widely across the organization. We use it for heterogeneous replication, active-active and active hot standby, and offloading reporting.

We use it to move data between databases to a dw for reporting purposes. We also use it to transform data as it moves, and we use it to populate pdb's to enable our services architecture.

We use GoldenGate to replicate some of the data from the production database to a data warehouse. It is used by the IT department. By using GoldenGate we don't impact the production database. We can run queries or reports or any long queries from the replicated database using GoldenGate. At one time we even used GoldenGate as a DR database and replicated entire production database. By doing so, one time when we had an outage and lost the production database, this DR became available to us and switched it to the primary. So we have a lot of advantages when using GoldenGate. We can replicate some tables or all tables and different scenarios of replicating data using functions and triggers. The business problem it addressed was less impact on production databases, more realtime data available to the business without putting an overload on production databases.

We are using OGG to synchronize our UAT/Production database with Oracle Cloud. The set up is being done by administrators and used only by the channels manager and administrator. One of the problems we found is the product cost, specifically after moving from Oracle Classic to OCI. In addition, we didn't find clear documentation to describe what we exactly can do with sequences synchronization. The user interface is another product and we have to purchase it to be able to monitor GG performance and issues.

We have multiple data centers and all of them share the same copy of DB. We use GoldenGate to do cross datacenters replication for Oracle and My SQL DBs as an HA solution. As our DBs are one of the busiest in the world and have a very tight SLA for replication lag which we can achieve by GoldenGate. We have explored few other products like SharePlex but GG done the work for us. GoldenGate is a de-facto standard for replication in our organization.

We have built a data change pipeline using GG technology by plugging in Kafka in front. Also, it's helped us in fault tolerance as a live DR database is readily available in a separate DC in case current DC goes down. In both modes, it's been super helpful to ensure data is sent in an async manner to reporting systems. It's saved us in cases of DC failures.

It is being used by an existing product in one of the business units which supports the payment platform. We are also planning to use it for a new application pipeline which is currently under development using bi-directional replication.

GoldenGate is used across multiple departments to move data.

This is one of our DB products that are used for replication. I have used GoldenGate in the past before Oracle, and this product, though with its faults, is still one of the industry leaders. This product is used across banking, credit cards, CFO and Insurance LOB's.

We have been using Oracle GoldenGate (OGG) for our replication needs. We have a mix of database environments including Oracle, DB2 and Microsoft SQL Server. We use Oracle GoldenGate to replicate across the mix of these different RDBMS. OGG is reliable, fast, has high throughput and allows heterogeneous replication.

We also use OGG Management Pack which is an extra license cost and includes Oracle GoldenGate Monitor, Oracle GoldenGate Director and Oracle GoldenGate Veridata.

Oracle GoldenGate is used by organization, which provides high availability and real-time data integration solutions. To be specific, the company needs a platform that allows business applications to benefit from continuous access to real-time information in a diverse IT environment without compromising performance.

Goldengate is being used for production replication for an active-active application that is critical to business needs.