6 Configuring Capture in Integrated Mode
Note:
To switch an active Extract configuration from classic to integrated mode, perform these configuration steps and then see Administering Oracle GoldenGate.
In case the Integrated Extract is running from a remote system, Oracle GoldenGate automatically enables cross endian interoperability. This implies that if the endian value where Integrated Extract is running is different from the endian value where the Oracle database is running, then the cross endian support is automatically enabled.
Topics:
- Prerequisites for Configuring Integrated Capture
You must adhere to the guidelines provided in this topic before configuring an Extract in integrated mode. - What to Expect from these Instructions
These instructions show you how to configure a basic Extract parameter (configuration) file for the primary Extract, which captures transaction data from the data source, and for a data-pump Extract, which propagates captured data that is stored locally in a trail from the source system to the target system. - Configuring the Primary Extract in Integrated Capture Mode
The mining database from which the primary Extract captures log change records from the logmining server, can be either local or downstream from the source database. - Configuring the Data Pump Extract
A data pump can perform data filtering, mapping, and conversion, or it can be configured in pass-through mode, where data is passively transferred as-is, without manipulation. - Next Steps
A parameter file is a plain text file that is read by an associated Oracle GoldenGate process. Oracle GoldenGate uses two types of parameter files: a GLOBALS file and runtime parameter files.
Prerequisites for Configuring Integrated Capture
You must adhere to the guidelines provided in this topic before configuring an Extract in integrated mode.
-
Create the Oracle GoldenGate instance on the source system by configuring the Manager process. See Administering Oracle GoldenGate.
-
Additionally, review the guidelines in Administering Oracle GoldenGate.
Parent topic: Configuring Capture in Integrated Mode
What to Expect from these Instructions
These instructions show you how to configure a basic Extract parameter (configuration) file for the primary Extract, which captures transaction data from the data source, and for a data-pump Extract, which propagates captured data that is stored locally in a trail from the source system to the target system.
Your business requirements probably will require a more complex topology, but this procedure forms a basis for the rest of your configuration steps.
By performing these steps, you can:
-
get the basic configuration files established.
-
build upon them later by adding more parameters as you make decisions about features or requirements that apply to your environment.
-
use copies of them to make the creation of additional parameter files faster than starting from scratch.
Parent topic: Configuring Capture in Integrated Mode
Configuring the Primary Extract in Integrated Capture Mode
The mining database from which the primary Extract captures log change records from the logmining server, can be either local or downstream from the source database.
These steps configure the primary Extract to capture transaction data in integrated mode from either location. See Configuring a Downstream Mining Database and Example Downstream Mining Configuration for more information about capturing from a downstream mining database.
Note:
One Extract group is generally sufficient to capture from a single database or multiple pluggable databases within a multitenant container database. See Configuring Oracle GoldenGate in a Multitenant Container Database.
Parent topic: Configuring Capture in Integrated Mode
Configuring the Data Pump Extract
A data pump can perform data filtering, mapping, and conversion, or it can be configured in pass-through mode, where data is passively transferred as-is, without manipulation.
Note:
If you want to perform this task using microservices, see How to Add a Path in Using the Oracle GoldenGate Microservices Architecture.Parent topic: Configuring Capture in Integrated Mode
Next Steps
A parameter file is a plain text file that is read by an associated Oracle GoldenGate process. Oracle GoldenGate uses two types of parameter files: a GLOBALS file and runtime parameter files.
Once you have created a basic parameter file for classic capture, see the following for related configuration steps.
Configuring Oracle GoldenGate Apply
Configuring Oracle GoldenGate in a Multitenant Container Database
Additional Oracle GoldenGate Configuration Considerations
Configuring DDL Support (to use Oracle GoldenGate DDL support)
Creating Process Groups (to use Oracle GoldenGate DDL support)
Instantiating Oracle GoldenGate Replication
Optional Parameters for Integrated Modes
Configuring a Downstream Mining Database
Parent topic: Configuring Capture in Integrated Mode