With introduction of GoldenGate Studio, replication solution can be pre-configured and deployment templates can be created by dragging and dropping data services and replication paths to the solution diagram.
Prior to GoldenGate studio, for data mapping we need to create mapping configuration manually for schema, tables and column mapping by analyzing respective schema and tables. By using GoldenGate Studio all of this can be achieved by GUI and deployment templates and profiles can be created to redeploy same solutions across different projects.
Through project/solution creation wizard a unidirectional replication configuration is created. OGG Studio displays the solution in the editor. Data source (DS) 01 shows an arrow that points to data source (DS) 02. That is the high level, logical view of the replication solution we are going to deploy.
Click the First Deployment tab. The visual representation of the deployment shows the two data sources with an exclamation point sign over a yellow background, to signify a warning. OGG Studio knows about the Oracle GoldenGate instances because we define them in the global resources section of the OGG Studio editor, and we associated them to the source and target sides of the replication environment while filling in the parameters required by the wizard. OGG Studio correctly displays the source and target hostnames and the OGG instances “OGG Source” and “OGG Target.” But DS 01 and DS 02 are generic and undefined data sources, not associated to any specific database
To remove any ambiguity, as far as the data sources are concerned, we must create two database entries in the global resource library, one for the replication source, and one for the replication target. In GoldenGate environment, we have an Oracle GoldenGate user (GGADMIN) which is used by the GoldenGate instances to connect to the database to perform replication. Rows are moved from the Source user (West)/schema to the Target user(East)/schema. The pictorial representation of your replication environment, as shown by OGG Studio, now looks correct after removing ambiguity. The replication source runs on “localhost,” the Oracle data source “West” has its data extracted by the “OGG Source” GoldenGate instance through the data capture process “c01aa” which checkpoints the data into the “aa” trail file. The data pump process “p02aabb” transmits the “aa” trail file to the target host “localhost”, where the “OGG Target” GoldenGate instance runs, creating the “bb” trail file. The replication target runs the apply process “r01bb” storing the data into the replication target data source “East.”
Let’s create mapping groups and define what data is going to be replicated. Right-click Mapping Groups then click New to configure a new mapping group called as First Map. The mapping group “First Map” is displayed in the editor. A call-out text informs you that you should drag and drop schemas and tables from the Global Resource Library.
In the “Resources” pane select the “Global Resource Library” then right click on the West Database to expand its nodes. As shown below drag those three tables in the “Source” section of the mapping group.
Repeat the same operation for the target section of your mapping group. In the “Global Resource Library”, we will use the “East” database, drag those three tables in the “Target” section of the mapping group.
Click the AutoMap button to instruct OGG Studio to automatically map the tables in the source and target sections of the mapping group.
Save the mapping group definition to store this definition in the OGG Studio repository. Let’s now assign the mapping group “First Map” to the solution “First Solution”. In the editor, click the “First Solution” tab, then drag the “First Map” mapping group onto the “DS 01” data source.
Upon successful assignment of the mapping group to the solution, in the message log window the message “The selected map (First Map) is successfully assigned to the replication path” will be displayed.
In the “First Solution” tab, click the arrow which connects the two data sources. In the “Properties” pane, you see the map “First Map” associated to the replication path comprising the “DS 01” and “DS 02” data sources.
There are some configuration items we have to change in this deployment. We will add checkpoint table on both source and target, change Extract, Pump and Replicat properties to reflect correct database environments and validate it. Now this Firdt Deployment can be deployed as shown below.
OGG Studio deploys the replication environment you visually configured in the various editors. OGG Studio, while deploying, prints many messages to the “Message Log” window. Look for the message “Deployment process finished” for a confirmation that deployment was completely carried out by OGG Studio.
Caveat: No tool is perfect, and while OGG Studio can assist in streamlining a deployment, it’s still a great idea to have the experts available to assist if needed. Contact Cintra now and we’ll help explain where OGG Studio is a fit, and where a more traditional manual approach is more appropriate.
Written by Vishwajit Ilamkar, Senior Oracle DBA – Cintra NY, August 2017