In order to extract the committed transactions from the source Oracle database's online redo logs, as a minimum the database must be configured for supplemental logging on Primary Key columns. This can be enabled at database level using the following DDL executed as SYSDBA:

[oracle@dbserver1 ggs]$ sqlplus '/as sysdba'
SQL> alter database add supplemental log data (primary key) columns;

Database altered

Initiate a log file switch to start supplemental logging:

SQL> alter system switch logfile;

System altered.

The following SQL shows the result of enabling the supplemental logging:

SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;

SUPPLEME SUP SUP
-------- --- ---
IMPLICIT YES NO

We now need to configure GoldenGate to add supplemental log data to the source tables using GGSCI's ADD TRANDATA command. This is shown in the following example for the SCOTT.DEPT and SCOTT.EMP tables:

[oracle@dbserver1 ggs]$ ggsci
GGSCI (dbserver1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
Successfully logged into database.

GGSCI (dbserver1) 2> ADD TRANDATA scott.DEPT

Logging of supplemental redo data enabled for table SCOTT.DEPT.

GGSCI (dbserver1) 3> ADD TRANDATA scott.EMP

Logging of supplemental redo data enabled for table SCOTT.EMP.

The source database is now ready for data replication!

If you have a lot of tables in your source schema that you wish to replicate, then you could use SQL to generate the ADD TRANDATA statements. Log on to the source database schema using SQL*Plus and execute the following commands:

SQL> set pages 0
SQL> select 'ADD TRANDATA SRC.'||tname from tab;