What is Integrated Capture
Instead of reading from the redo/archive logs, the Oracle GoldenGate Extract process interacts directly with a database logmining server to receive data changes in the form of logical change records (LCR).
Some of the benefits of Integrated Capture are :
- supports more data and storage types as compared to classic capture
- automatic integration with the RMAN log retention feature to ensure that required archive logs are not deleted
- transparent support with RAC for the addition or removal of nodes
- automatic support of Transparent Data Encryption
To support all Oracle data and storage types, the compatibility setting of the source database must be at least 220.127.116.11.0 with the 18.104.22.168 Database specific bundle patch for Integrated Extract 11.2.x (Doc ID 1411356.1).
Database User Privileges
In addition the privileges required for Classic Capture, two more privileges are required.
grant select on V_$DATABASE to ggate;
The GoldenGate installation for Integrated Capture is no different than if the Classic Capture was being used. In fact, you may run both types of extracts on the same server simultaneously. The differences are in the login and how the extract capture process is created. For a complete installation, you check look at one of my previous posts here. Let’s see how it works.
Adding the Capture Process
GGSCI> DBLOGIN USERID ggate, PASSWORD ggate GGSCI> MININGDBLOGIN USERID ggate, PASSWORD ggate GGSCI> REGISTER EXTRACT cname DATABASE GGSCI> add extract cname, <em><strong>integrated tranlog</strong></em>, begin now GGSCI> add exttrail /u01/app/oracle/product/gg/dirdat/lt, extract cname
The differences from Classic Capture are highlighted and italicized above.
In addition, you should put the miningdblogin in the capture parameter file as well.
TRANLOGOPTIONS MININGUSER ggate, MININGPASSWORD ggate
The capture process above was tested using GG 22.214.171.124.1 on an Oracle 126.96.36.199 database.