Académique Documents
Professionnel Documents
Culture Documents
1 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Integrating Oracle Data Integrator 12c (ODI) and Oracle GoldenGate 12c (OGG)
Purpose
This tutorial covers integrating Oracle Goldengate (OGG) with Oracle Data Integrator 12c (ODI). ODI knows about and can control OGG, OGG does not know about ODI.
Time to Complete
Approximately 2 hours, depending on whether you use the pre-built VM or not (see Software Requirements below).
Introduction
In this tutorial, you will create the sample database users and tables, configure the OGG manager and agents, configure the ODI data servers, models, datastores, maps, agents, and
packages, and then start/stop/control the processes. There will be both OGG replication (capture and delivery) and ODI replication (Change Data Capture via Journaling). The OGG will run
near-real-time, the ODI will run in micro-batches of one row of changed data polling once/second.
Scenario
Suppose the Example Corporation has an Orders Application system that has a Customer table. You want to keep an up-to-date copy of that information on the Sales administration system.
As changes are made to the Orders Customer table, OGG in near-real-time replicates those changes to the Sales Customer table. However, the Sales system requires the format of the data
to be transformed into a slightly different layout. ODI will do the transformation of only the rows that have changed.
When showing terminal sessions of the above scenario, the logical and physical E-LT flow will be as follows:
Source will be the Orders Application OGG_ODI_DEMO_SRC.OGG_CUSTOMER table shown with a BLUE banner.
Staging will be the Sales Administration ODI_DEMO.OGG_CUSTOMER table shown with a RED banner.
Target will be the Sales Administration ODI_DEMO.TRG_CUSTOMER table shown with a GREEN banner.
Prerequisites
Before starting this tutorial, you should:
Have access to or have installed Oracle Data Integrator 12c. The prerequisites for that are a FMW home with WLS installed, a database with RCU configured to create the ODI
repositories.
Have access to or have installed sample schemas and repositories. This example uses the ODI_DEMO schema which is available online at: ODI Getting Started. If you are using the VM,
then this schema is already included.
Normally an ODI environment would have two or three hosts. The source database would be on one host (usually the smaller host) and the target database on another host (usually the larger
host). The staging area would be on the more powerful of the two hosts, or possibly on a third host. The configuration used for this demonstration was done on one large host (rather unusual),
so there are some issues with multiple $ORA_HOME definitions that would not normally surface in a "real" environment.
21/10/2014 22:30
ODI+OGG Integration
2 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
In real life you would also set up foreign key relationships to other tables.
2. Populate the source table. (There is a procedure supplied in the VM to do this any time later in the lab.)
21/10/2014 22:30
ODI+OGG Integration
3 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
35 rows created.
SQL_SOURCE > exit
If you want to make sure they worked, you can: SELECT * FROM SRC_CUSTOMER;
The source database is now prepared.
21/10/2014 22:30
ODI+OGG Integration
4 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
ODI Staging
Normally an OGG environment would have two or more hosts. The source database would be on one host and the target database on another host. The configuration used for this
demonstration was done on one large host (rather unusual), so there are some issues with multiple $OGG_HOME definitions that would not normally surface in a "real" environment. To solve this
on one host, OGG must be completely installed twice, the two instances cannot share any code.
21/10/2014 22:30
ODI+OGG Integration
5 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
OGG Source
It is a good convention to have comments with the double-dashes as the first few lines in a parameter file. The keywords (for example, EnableMonitoring) are case-insensitive,
so EnableMonitoring is the same as ENABLEMONITORING is the same as enablemonitoring. For readability, you may want to use MixedCase by word.
2. Configure (or verify) the source Manager and mgr.prm file. Edit the file to look like the following view. (You may want to issue the GGSCI command set editor gedit if you don't like
to use vi.)
OGG Source
The source and target jagent.prm files are the same (except for the comments).
4. Configure (or verify) the source JAgent configuration and ./cfg/Config.properties file.
OGG Source
The reason you need to exit GGSCI is so that the new parameters can take effect the next time you start GGSCI.
You also need to DBLogin and then Add TranData for any tables that OGG will extract from. The source GoldenGate instance is now prepared.
21/10/2014 22:30
ODI+OGG Integration
6 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
OK
to continue.
Physical Architecture > Technologies > Oracle GoldenGate, right-click, then New Data Server.
If the OGG_Source and OGG_Target already exist, then open them to verify that they match the screens shown.
4. On the JAgent tab, create (or verify) the OGG_Source JAgent Server.
The RMI Port 5559 should match the value in OGG source Config.properties, the Manager Port 7010 should match the value in OGG source mgr.prm. Save
the New Data Server OGG_Source tab.
and close
5. On the JAgent tab, create (or verify) the OGG_Target JAgent Server.
21/10/2014 22:30
ODI+OGG Integration
7 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
The RMI Port 5561 should match the value in OGG target Config.properties, the Manager Port 7020 should match the value in OGG target mgr.prm. Save
New Data Server OGG_Target tab.
Physical Architecture > Technologies > Oracle, right-click, then New Data Server.
If SRC_ODIDEMO and TRG_ODIDEMO already exist, then open them to verify that they match the screens shown.
2. On the Definition tab, create (or verify) the SRC_ODIDEMO Data Server.
21/10/2014 22:30
ODI+OGG Integration
8 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
3. On the JDBC tab, create (or verify) the JDBC Driver and JDBC URL.
Be careful not to lose the colons between the parameters (they are hard to see...)
4. Test JDBC connectivity by clicking
Click
Test
to continue.
5. On the Definition tab, create (or verify) the TRG_ODIDEMO Data Server.
Be careful not to lose the colons between the parameters (they are hard to see...)
7. Test JDBC connectivity by clicking
Click
Test
to continue.
21/10/2014 22:30
ODI+OGG Integration
9 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
The Physical Architecture is only half of the Topology definition. You still have to do the Logical Architecture.
9. Go to the Topology Navigator tab, and expand
Logical Architecture > Technologies > Oracle, right-click, then New Logical Schema.
You are going to do this three times for three logical schemas.
10. Create a Logical Schema named ODI_DEMO_SRC with a Context of Global and a Physical Schema of SRC_ODIDEMO.ODI_DEMO as shown.
Save
11. Create a Logical Schema named ODI_DEMO_TRG with a Context of Global and a Physical Schema of TRG_ODIDEMO.ODI_DEMO as shown.
Save
12. Create a Logical Schema named OGG_ODI_DEMO_SRC with a Context of Global and a Physical Schema of SRC_ODIDEMO.OGG_ODI_DEMO_SRC as shown.
Save
13. When you are all done, it should look like this:
21/10/2014 22:30
ODI+OGG Integration
10 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
In the demo VM, all three of these Logical Schemas are on the same database on the same host in the same context. That is very unusual. In real life they would probably be on
different hosts or at least different technologies.
The ODI Data Servers now have physical and logical definitions.
The Description is optional. It is a good convention to put the modification history in here. Save
3. Returning to the Designer tab, click the pull-down again and select New Model.
Note that new with ODI version 12.1.3 is the option to do all this on one screen: the New Model and Topology Objects screen.
4. Create the Orders Application model using the parameters shown.
21/10/2014 22:30
ODI+OGG Integration
11 sur 36
Save
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Reverse Engineer
to read the table metadata. You will see the following pop-up briefly:
Save
Reverse Engineer
to read the table metadata. You will see the following pop-up briefly:
You may have additional datastores (tables) as well. The three datastores that you care about are:
21/10/2014 22:30
ODI+OGG Integration
12 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Save
Save
5. Click the pull-down and select New Folder again. Name the folder Sync data.
Save
21/10/2014 22:30
ODI+OGG Integration
13 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
You may accidentally import CKM Hive (a known bug), you can safely ignore it.
9. Expand
Next you will create a mapping to do the initial load of Sales Administration OGG_CUSTOMER table.
10. Right-click Mappings, select .
21/10/2014 22:30
ODI+OGG Integration
14 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Sales Administration.
a. Drag both OGG_CUSTOMER datastores onto the workspace. Make sure the Orders one is on the left and the Sales one is on the right.
b. Hook the output of the source to the input of the target.
c. Accept Auto Mapping of Attributes.
You can check which OGG_CUSTOMER is which by clicking the title bar and looking at the Properties > General.
12. Select the target OGG_CUSTOMER title bar and change the Target > Integration Type to Control Append.
21/10/2014 22:30
ODI+OGG Integration
15 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
If it already is LKM Oracle to Oracle Pull (DB Link).GLOBAL, then just confirm it. Save
14. Click Run
Click
OK
in the top menu bar to run the mapping to populate the table.
OK
Session List > Agent > Local > ?? - Initial Load Staging. Make sure that the overall mapping was successful. The "??" on this
21/10/2014 22:30
ODI+OGG Integration
16 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Click
Close
to continue.
18. If you are using the VM, you can use the enclosed ODI and OGG Demo Client to see that two of the three customer tables are populated.
21/10/2014 22:30
ODI+OGG Integration
17 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
2. Click
OK
OK
Projects > Sync Data > Mappings, then select Load TRG_CUSTOMER. Click Run
21/10/2014 22:30
ODI+OGG Integration
18 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Notice this Physical Mapping Design: Bulk Load, whereas the previous one was Physical Mapping Design: Physical.
. Expand Session List > Agent > Local > ?? - Load TRG_CUSTOMER_Bulk Load. Make sure that the overall mapping was
6. Go to the Operator Navigator tab, click Refresh
successful. The "??" on this example is 62, your number may be different.
7. Use SQL*Plus or the enclosed ODI and OGG Demo Client to see that all three customer tables are populated.
Note that CUST_NAME is concatenated from FIRST_NAME||UPPER(LAST_NAME), and DEAR is resolved into Mr., Mrs., and so on. Also, a few of the rows are missing from the
target: 203, 207, and so on.
The initial load of the Target table is complete.
ODI communicates with OGG via agents. The agents are defined by keywords in an ASCII text file. ODI configures an extract, datapump, and replicat via the Studio GUI. This creates the text
files mentioned previously. ODI places the text files in their proper OGG directories.
21/10/2014 22:30
ODI+OGG Integration
19 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
There are lots of options you can configure, but the most important is Technology Type: ODI Connector.
2. Expand Oracle GoldenGate > OGG_Source, then open (double-click) CAP (capture, also known as extract). The difference between CAP and CAP_IL is the "_IL" suffix stands for
"Initial Load." This demonstration uses an ODI mapping rather than OGG's _IL here to do the initial load. You can use either one.
Note the Trail File Paths and file suffixes you pick, such as oc (odi capture) and op (odi pump).
3. Expand
Logical Architecture > Technologies > Oracle GoldenGate, and open (double-click) CAP_LS (abbreviation for CAPture Logical Schema). It should look ike this:
21/10/2014 22:30
ODI+OGG Integration
20 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Change Data Capture (CDC) is configured with a Journalizing Knowledge Module (JKM). You define it for a model by adding subscribers, and then start it for a datastore. The transfer from the
Journal to a mapping is handled by a package in a loop.
2. Select the Journalizing tab. Note that the JKM is at the Model level, not the datastore level.
The Journalizing Mode: Consistent Set matches the JKM Oracle to Oracle Consistent. The (OGG Online) means that the ODI-created OGG parameter files are placed into
the OGG directories automatically rather than having to be copied manually.
The difference between CAP and CAP_IL is the "_IL" suffix stands for "Initial Load." This demonstration uses an ODI mapping rather than OGG's _IL here to do the initial load.
You can use either one.
3. Back on the Designer Navigator tab, right-click Orders Application, and select Changed Data Capture > Add to CDC.
21/10/2014 22:30
ODI+OGG Integration
21 sur 36
4. Click
Yes
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
5. Right-click Orders Application, and select Changed Data Capture > Subscriber > Subscribe.
A subscriber is an alias representing a process that is interested in changed data. Since you can have multiple processes interested in the same changed data, you can define
multiple subscribers. Each subscriber can move the changed data when needed without impacting the other ones.
6. In the List of Subscribers to Add, enter ODIDEMO.
Click
OK
to continue.
7. This starts a session that creates the journalizing environment and adds the user.
21/10/2014 22:30
ODI+OGG Integration
22 sur 36
Click
OK
Click
OK
to continue.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Session List > Agent > Local > ?? - Orders Application. Make sure that the overall mapping was successful. The
9. Back on the Designer Navigator tab, right-click Orders Application, and select Changed Data Capture > Start Journal.
This starts a session that starts the journalizing environment. This is where the OGG CAPture and DELivery processes and parameter files are actually run. Confirm the Run and
Information pop-ups as you did in the previous step 7.
10. Go to the Operator Navigator tab, and click Refresh
. Expand
"??" on this example is 64, your number may be different.
Session List > Agent > Local > ?? - Orders Application. Make sure that the overall mapping was successful. The
21/10/2014 22:30
ODI+OGG Integration
23 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
The warnings
you may see are the tasks that were already completed in the previous step 8. For example, the Operator is telling you on line 5 that you cannot "create" a
subscribers table because there already is one. You can ignore all of the warnings here.
11. Depending on how you have your preferences set, you may or may not see a change in the icon for the datastore. If you want to see the icon indicating CDC activity, go to the main
(top) tool bar and click Tools > Preferences, then expand ODI > User Interface > Designer. Select Show the CDC Modifications in the tree.
Click
OK
to continue.
Models > ODI_DEMO > Orders Application, you may see a very tiny change on the icon: a yellow clock face.
21/10/2014 22:30
ODI+OGG Integration
24 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
If the clock is yellow, that indicates waiting; a green clock indicates something else.
ODI CDC is now configured and started.
Note that OGG_CUSTOMER used in this Mapping is coming from the Orders Applications source model. It is the actual source table and not the replicated copy used by OGG
(located in the Sales Administration model). ODI will transparently know which table to use based on the Journalizing settings of the Mapping.
2. Click the Physical tab. Click Trickle Feed to display the incremental load Physical Design.
21/10/2014 22:30
ODI+OGG Integration
25 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Even though the mapping says to use the source model, selecting Journalized Data Only causes ODI to use the target journal of only changed records.
The mapping has the power to do a transformation. That is why OGG alone is not a complete solution, you also need ODI.
Projects > Sync Data > Packages, then open Sync Data.
This package will run continuously. This package will wait for new changes to be replicated by OGG and upon detection it will move and transform the replicated data from the
staging table into the target table using ODI.
2. The ODI Tool step Wait for Changes is doing the CDC detection using OdiWaitForLogData. It is waiting for some changed records to be published by OGG.
21/10/2014 22:30
ODI+OGG Integration
26 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Parameters of Note:
Global Row Count=1 says to only wait for one row to be changed before proceeding to the next step (i.e., a "micro-batch").
Polling Interval=1000 milliseconds, i.e., 1 second (basically near-real-time).
Logical Schema=ODI_DEMO_TRG and Subscriber=ODIDEMO match previous configuration values.
3. Once the detection of one changed row is successful, the next package step Extend and Lock will logically lock the records that will be moved for your ODIDEMO subscriber. "Locking"
is what makes this a Consistent Journalizing set versus a Simple set.
Parameters of Note:
Subscribers=ODIDEMO match previous configuration values.
Consumption=Extend, Lock. This second step does the first two Consumption options; the fourth step does the last two Consumption options.
4. The Mapping Load TRG_CUSTOMER will load the changed data using the Trickle Feed physical design and the ODIDEMO Subscriber
21/10/2014 22:30
ODI+OGG Integration
27 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
It would be a good practice to have an unsuccessful path ("ko" red arrow) to trap possible errors.
5. This is the opposite of package step 2, "Extend and Lock."
Parameters of Note:
Subscribers=ODIDEMO match previous configuration values.
Consumption=Purge, Unlock. The second step does the first two Consumption options; this fourth step does the last two Consumption options.
6. The Package ends with a step executing a Scenario, the same scenario, recursively.
21/10/2014 22:30
ODI+OGG Integration
28 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
It allows essentially looping through the same Package creating a new Session for every execution. This is a best practice rather than creating the loop directly in the Package as
this allows you to better control the overall execution.
7. Go to the Designer Navigator tab, and expand
journaling data to the target table.
Click
OK
OK
Projects > Sync Data > Packages, then select Sync Data. Click Run
in the top menu bar to run the package to move the CDC
Session List > Agent > Local > ?? - Sync Data. Make sure that the package is running/waiting (green arrow
). The
Now all the pieces are in place. Check what the ODI and OGG status looks like before anything has changed, then start changing data, and observe what changes.
21/10/2014 22:30
ODI+OGG Integration
29 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
OGG Source
Status
RUNNING
RUNNING
RUNNING
RUNNING
Group
Lag at Chkpt
CAP
DELP
00:00:00
00:00:00
00:00:00
00:00:05
These were created by ODI. If you are curious, you can do:
GGSCI > View Param CAP
GGSCI > View Param DELP
Status
RUNNING
RUNNING
RUNNING
Group
Lag at Chkpt
DEL1
00:00:00
00:00:01
3. You can verify the contents of the tables with SQL*Plus, SQL Developer, or the Demo Client.
Note that customer 104 has a first name of Joe. It says so in all three tables.
Now you have seen what the processes and data looks like before anything has changed.
21/10/2014 22:30
ODI+OGG Integration
30 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Status
RUNNING
RUNNING
RUNNING
RUNNING
Group
Lag at Chkpt
CAP
DELP
00:00:00
00:00:00
00:00:00
00:00:06
0.00
3.00
0.00
0.00
3.00
21/10/2014 22:30
ODI+OGG Integration
31 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Status
RUNNING
RUNNING
RUNNING
Group
Lag at Chkpt
DEL1
00:00:00
00:00:07
0.00
3.00
0.00
0.00
3.00
Even though the ODI CDC creates many sessions (micro-batches of 1 record each), OGG is just one big session.
The OGG processes are still running, waiting for more changes.
You can see the five steps (numbered 0-4) of the SYNC_DATA package for each session.
2. If you want, you can check the OGG reports:
OGG Source
21/10/2014 22:30
ODI+OGG Integration
32 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Models > ODI_DEMO > Orders Application. Right-click OGG_CUSTOMER and select Changed Data Capture > Journal Data.
This is not very interesting because no data shows up at this time! Had there not been a consumer, then the Journal would have the three prepended fields of Journal Flag
(Insert/Update/Delete), Date, and Subscriber, then the full row of new data for the table being captured. As it is, the data is in this journal for less than a second before being
consumed.
4. If you want to inspect the data with SQL*Plus, do the following queries:
E-LT Source (OGG Source)
The above is for the target table. All three should be the same, with a first name of Harry.
If the ODI side seems inefficient, you can always change the batch size to be increased from the current value of 1 to something larger, for example, 10.
21/10/2014 22:30
ODI+OGG Integration
33 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
At this point the OGG replication and the ODI CDC will continue to run/wait indefinitely (barring any error conditions). If you ever wish to stop it gracefully, perform the following steps:
This stops the package abruptly, breaking out of the infinite loop.
Click
OK
2. You do not have to remove the objects from CDC, at this point they are stopped. if you did want to completely clean up, then you go through the same steps to remove from CDC as you
did to add it, only in reverse order. The order is important. You can do it at the datastore level or the model level. For the datastore: First drop the journal.
21/10/2014 22:30
ODI+OGG Integration
34 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Click
Yes
to continue.
21/10/2014 22:30
ODI+OGG Integration
35 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
Click
Yes
to continue.
All objects have been removed from CDC. The tiny yellow clock icon should have been removed as well from the OGG_CUSTOMER label in the Models list.
Status
RUNNING
RUNNING
Group
Lag at Chkpt
Note that the password is in clear text. You may want to change that to an alias if you have OGG version 12.1.2 or higher.
2. On the OGG target, note that the replicat process is stopped and removed (unregistered), but the parameter file persists.
21/10/2014 22:30
ODI+OGG Integration
36 sur 36
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/o...
OGG Target
Status
RUNNING
RUNNING
Group
Lag at Chkpt
INSERTAL
Note that the password is in clear text. You may want to change that to an alias if you have OGG version 12.1.2 or higher.
It might be a good idea to View Report CAP (the completed report) just to make sure that nothing unusual is in there.
Following the business scenario posed in the Introduction section, you had three databases (actually one database with three schemas): a source, staging, and target database being used for
E-LT. OGG was used to make an exact replicate of the OGG_CUSTOMER table, from schema OGG_ODI_DEMO_SRC on the source to schema ODI_DEMO on the staging database. Then ODI was
used to make a transformation from OGG_CUSTOMER table to TRG_CUSTOMER table, changing some columns on the fly. ODI was copying only changed (inserted, updated, or deleted) rows in
micro-batches of 1 every 1 second.
In this tutorial, you learned to:
Prepare an Oracle Database for ODI and OGG replication
Prepare ODI for CDC
Prepare OGG for replication
Start, Monitor, Stop ODI and OGG integration
Resources
Here is a list of conceptual or procedural Help topics relevant to this tutorial:
ODI 12c full Documentation online (includes past versions).
ODI 12c and OGG Integration Documentation .
ODI 12c and OGG Webcast, specifically Integration.
Specific courses where ODI is discussed in detail:
[D82167GC10] "Oracle Data Integrator 12c: Integration and Administration"
[D82171GC10] "Oracle Data Integrator 12c: New Features"
[DxxxxxGC10] "Oracle Data Integrator 12c: Advanced Integration and Development"
[D78191GC10] "Oracle Data Integrator 11g: Advanced Integration and Development"
Specific courses where OGG is discussed in detail:
[D84357GC10] "Oracle GoldenGate 12c: Fundamentals for Oracle"
[D76689GC10] "Oracle GoldenGate 11g: Advanced Configuration for Oracle"
External Web sites for related information: A-Team Blogs
To learn more about ODI and OGG, refer to additional OBEs in the free Oracle Learning Library:
A long list of ODI general OBEs here.
Here is the same ODI+OGG tutorial but for ODI 11g.
Credits
Lead Curriculum Developer: Steve Friedberg
Other Contributors: Julien Testut, Product Manager; Alex Kotopoulis, Product Manager, Tom Mangiacapre.
21/10/2014 22:30