This post provides a comprehensive step-by-step guide to configuring Oracle GoldenGate unidirectional replication for Oracle Database 19c.
The configuration demonstrates how to set up a source and target database, enable supplemental logging, create the required GoldenGate users and privileges, configure Manager, Extract, Data Pump, and Replicat processes, and establish real-time data replication between the environments.
Environment
=========
Source & Target Oracle DB Version : 19.27
Source & Target OGG Vesrion : 19.1
Source & Target DB Type: Multitenant, CDB with one PDB
GoldenGate Architecture: Classic Architecture
GoldenGate Replication Mode: Unidirectional, homogeneuos (Oracle DB to Oracle DB)
GoldenGate Home: /app/ogg19c
Source DB name: oggsrc (CDB), oggsrcpdb1 (PDB)
DB Home: /u01/app/oracle/product/19c/db
Note: Oracle GoldenGate and the databases were already installed on both the source and target servers prior to this configuration. For Oracle GoldenGate installation steps, refer to the post below.
Installing Oracle GoldenGate 19c for Oracle Database 19c on Linux server
1. Update the /etc/hosts file and tnsnames.ora configuration on both the source and target servers with the host entries and TNS aliases for the source and target pluggable databases.
–On Source Server
[oracle@oggsrc admin]$ cat tnsnames.ora
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/19c/db/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
GGSRC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggsrc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ggsrc)
)
)
GGSRCPDB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggsrc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ggsrcpdb1)
)
)
LISTENER_GGSRC =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggsrc)(PORT = 1521))
[oracle@oggsrc ~]$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.56.172 oggsrc
192.168.56.173 oggtgt
–On target Server
[oracle@oggtgt admin]$ cat tnsnames.ora
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/19c/db/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
GGTGT =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggtgt)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ggtgt)
)
)
GGTGTPDB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggtgt)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ggtgtpdb1)
)
)
LISTENER_GGTGT =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggtgt)(PORT = 1521))
GGSRCPDB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oggsrc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ggsrcpdb1)
)
)
[oracle@oggtgt ~]$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.56.173 oggtgt
192.168.56.172 oggsrc
2. On the source database, create a c##ggadmin at the CDB level.
To capture data from a multitenant database, configure the Extract process at the root container (CDB$ROOT) using a common user account prefixed with C##.
A single Extract group can capture changes from multiple pluggable databases (PDBs) and write them to a single trail file.
–Create dedicated tablespace for common user at CDB level
SQL> CREATE TABLESPACE ggadmin DATAFILE ‘/u01/app/oracle/oradata/GGSRC/ggadmin_01.dbf’ SIZE 2G;
Tablespace created.
–Create dedicated tablespace for common user at PDB level.
SQL> alter session set container=ggsrcpdb1;
Session altered.
SQL> CREATE TABLESPACE ggadmin DATAFILE ‘/u01/app/oracle/oradata/GGSRC/ggsrcpdb1/ggadmin_ggsrcpdb1_01.dbf’ SIZE 2G;
Tablespace created.
–create common user at CDB root level
SQL> CREATE user c##ggadmin IDENTIFIED BY ggadmin DEFAULT TABLESPACE ggadmin QUOTA UNLIMITED ON ggadmin;
User created.
3. On the source database, grant the necessary privileges to the the OGG admin common user.
–Grant below privileges to the OGG admin common user at CDB root level
SQL> GRANT CREATE SESSION, CONNECT, RESOURCE, ALTER SYSTEM, CREATE VIEW, ALTER USER, CREATE ANY TABLE, CREATE ANY VIEW, SELECT ANY DICTIONARY, SELECT ANY TRANSACTION to c##ggadmin container=all;
Grant succeeded.
–-The following command grants Oracle GoldenGate Capture Administrator privileges to the common user C##GGADMIN:
SQL> EXEC DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => ‘c##ggadmin’, privilege_type => ‘*’, grant_select_privileges => TRUE, do_grants => TRUE, container => ‘ALL’);
PL/SQL procedure successfully completed.
–Verify the granted privileges
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE GRANTEE=’C##GGADMIN’ ORDER BY 2;
GRANTEE PRIVILEGE ADM COM INH
———- —————————————- — — —
C##GGADMIN ALTER SYSTEM NO YES NO
C##GGADMIN ALTER USER NO YES NO
C##GGADMIN CREATE ANY TABLE NO YES NO
C##GGADMIN CREATE ANY VIEW NO YES NO
C##GGADMIN CREATE SESSION NO YES NO
C##GGADMIN CREATE VIEW NO YES NO
C##GGADMIN SELECT ANY DICTIONARY NO YES NO
C##GGADMIN SELECT ANY TRANSACTION NO YES NO
8 rows selected.
4. On source database, Configuring Logging Properties at CDB level.
–Oracle databases must be configured in ARCHIVELOG mode to enable Extract to read and process archived redo logs.
SQL> SELECT name, log_mode FROM v$database;
NAME LOG_MODE
——— ————
GGSRC ARCHIVELOG
–Oracle databases must be configured in FORCE LOGGING mode to ensure that all database changes are recorded in the redo logs.
SQL> SELECT name,force_logging FROM v$database;
NAME FORCE_LOGGING
——— —————————————
GGSRC NO
SQL> ALTER DATABASE FORCE LOGGING;
Database altered.
SQL> SELECT name,force_logging FROM v$database;
NAME FORCE_LOGGING
——— —————————————
GGSRC YES
–Enable the Oracle GoldenGate replication capabilities in the database.
SQL> ALTER SYSTEM SET ENABLE_GOLDENGATE_REPLICATION=TRUE SCOPE=BOTH;
System altered.
–Enable minimal supplemental logging to add row-chaining information to the redo log.
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
Database altered.
–Enable Subset Database Supplemental Logging mode at PDB level
SQL> alter session set container=GGSRCPDB1;
Session altered.
SQL> ALTER PLUGGABLE DATABASE GGSRCPDB1 ADD SUPPLEMENTAL LOG DATA SUBSET DATABASE REPLICATION;
Pluggable database altered.
–Run the following command to validate the data dictionary
SQL> set linesize 300
col MINIMAL for a14
col SUBSET_REP for a14
col PRIMARY_KEY for a14
col UNIQUE_INDEX for a14
col FOREIGN_KEY for a14
col ALL_COLUMN for a20
SELECT con_id, MINIMAL, SUBSET_REP, PRIMARY_KEY, UNIQUE_INDEX, FOREIGN_KEY, ALL_COLUMN FROM CDB_SUPPLEMENTAL_LOGGING;
CON_ID MINIMAL SUBSET_REP PRIMARY_KEY UNIQUE_INDEX FOREIGN_KEY ALL_COLUMN
———- ————– ————– ————– ————– ————– ——————–
1 YES NO NO NO NO NO
3 YES YES NO NO NO NO
The output for SUBSET_REP should be YES for pluggable database.
–Switch the logfile
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
5. On the target database, create a c##ggadmin at the CDB level.
–Create dedicated tablespace for common user at CDB level
SQL> CREATE TABLESPACE ggadmin DATAFILE ‘/u01/app/oracle/oradata/GGTGT/ggadmin_01.dbf’ SIZE 2G;
Tablespace created.
–Create dedicated tablespace for common user at PDB level.
SQL> alter session set container=GGTGTPDB1;
Session altered.
SQL> CREATE TABLESPACE ggadmin DATAFILE ‘/u01/app/oracle/oradata/GGTGT/ggtgtpdb1/ggadmin_ggsrcpdb1_01.dbf’ SIZE 2G;
Tablespace created.
–create common user at CDB root level
SQL> alter session set container=CDB$ROOT;
Session altered.
SQL> CREATE user c##ggadmin IDENTIFIED BY ggadmin DEFAULT TABLESPACE ggadmin QUOTA UNLIMITED ON ggadmin;
User created.
6. On the target database, grant the necessary privileges to the the OGG admin common user.
–Grant below privileges to the OGG admin common user at CDB root level
SQL> GRANT CREATE SESSION, CONNECT, RESOURCE, ALTER SYSTEM, CREATE VIEW, ALTER USER, CREATE ANY TABLE, CREATE ANY VIEW, SELECT ANY DICTIONARY, SELECT ANY TRANSACTION,INSERT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE,SELECT ANY TABLE to c##ggadmin container=all;
Grant succeeded.
–The following command grants Oracle GoldenGate Capture Administrator privileges to the common user C##GGADMIN:
SQL> EXEC DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE(grantee=>’c##ggadmin’, privilege_type=>’APPLY’, grant_select_privileges=>TRUE, do_grants=>TRUE, container=>’ALL’);
PL/SQL procedure successfully completed.
7. Enable GOLDENGATE replication in target database.
SQL> ALTER SYSTEM SET ENABLE_GOLDENGATE_REPLICATION=TRUE SCOPE=BOTH;
System altered.
8. Create credentialstore for both source and target GoldenGate.
–On source GoldenGate
[oracle@oggsrc ~]$ cd /app/ogg19c/
[oracle@oggsrc ogg19c]$ ./ggsci
GGSCI (oggsrc) 3> ADD CREDENTIALSTORE
Credential store created.
GGSCI (oggsrc) 4> ALTER CREDENTIALSTORE ADD USER c##ggadmin@GGSRC PASSWORD ggadmin ALIAS ggadmin
Credential store altered.
GGSCI (oggsrc) 6> DBLOGIN USERIDALIAS ggadmin
Successfully logged into database CDB$ROOT.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 7>
—
–On target GoldenGate
[oracle@oggtgt ~]$ cd /app/ogg19c/
[oracle@oggtgt ogg19c]$ ./ggsci
GGSCI (oggtgt) 1> ADD CREDENTIALSTORE
Credential store created.
GGSCI (oggtgt) 6> ALTER CREDENTIALSTORE ADD USER c##ggadmin@GGTGTPDB1 PASSWORD ggadmin ALIAS ggadmin
Credential store altered.
GGSCI (oggtgt) 3> DBLOGIN USERIDALIAS ggadmin
Successfully logged into database CDB$ROOT.
GGSCI (oggtgt as c##ggadmin@ggtgt/CDB$ROOT) 4>
9. Create a table in HR schema on both source pluggable database and target pluggable databases.
–On source pluggable database (GGSRCPDB1)
SQL> connect hr/hr@ggsrcpdb1
Connected.
SQL> create table test(id number(4),name varchar2(20));
Table created.
–On target pluggable database (GGTGTPDB1)
SQL> connect hr/hr@ggtgtpdb1
Connected.
SQL> create table test(id number(4),name varchar2(20));
Table created.
10. Configure the Oracle GoldenGate Extract and Data Pump processes on the source server.
–Update Manager parameter file of Source GoldenGate
[oracle@oggsrc ~]$ cd /app/ogg19c/
[oracle@oggsrc ogg19c]$ ./ggsci
GGSCI (oggsrc) 1> stop mgr
Manager process is required by other GGS processes.
Are you sure you want to stop it (y/n)?y
Sending STOP request to MANAGER …
Request processed.
Manager stopped.
GGSCI (oggsrc) 2> edit param mgr
GGSCI (oggsrc) 3> view param mgr
PORT 7809
ACCESSRULE, PROG *, IPADDR *, ALLOW
GGSCI (oggsrc) 4> start mgr
Manager started.
GGSCI (oggsrc) 5> info mgr
Manager is running (IP port TCP:oggsrc.7809, Process ID 77918).
–Create integrated extract process for source GoldenGate
GGSCI (oggsrc) 1> DBLOGIN USERIDALIAS ggadmin
Successfully logged into database CDB$ROOT.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 2> edit params extsrc1
EXTRACT extsrc1
USERIDALIAS ggadmin
DISCARDFILE /app/ogg19c/dirrpt/extsrc1.dsc, PURGE
EXTTRAIL /app/ogg19c/dirdat/es
SOURCECATALOG GGSRCPDB1
TABLE HR.TEST;
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 3> view param extsrc1
EXTRACT extsrc1
USERIDALIAS ggadmin
DISCARDFILE /app/ogg19c/dirrpt/extsrc1.dsc, PURGE
EXTTRAIL /app/ogg19c/dirdat/es
SOURCECATALOG GGSRCPDB1
TABLE HR.TEST;
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 4> REGISTER EXTRACT extsrc1 DATABASE CONTAINER(GGSRCPDB1)
2026-11-15 11:16:06 INFO OGG-02003 Extract EXTSRC1 successfully registered with database at SCN 2531542.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 5> ADD EXTRACT extsrc1,INTEGRATED TRANLOG, begin now
EXTRACT (Integrated) added.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 6> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXTSRC1 00:00:00 00:00:07
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 12> ADD EXTTRAIL /app/ogg19c/dirdat/es , EXTRACT extsrc1
EXTTRAIL added.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 7> start EXTRACT EXTSRC1
Sending START request to MANAGER …
EXTRACT EXTSRC1 starting
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 8> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXTSRC1 00:00:00 00:01:36
–Create pump process for source GoldenGate
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 16> edit params pmpsrc1
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 17> view params pmpsrc1
EXTRACT pmpsrc1
PASSTHRU
RMTHOST oggtgt, MGRPORT 7809
RMTTRAIL /app/ogg19c/dirdat/es
TABLE GGSRCPDB1.HR.TEST;
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 18> ADD EXTRACT pmpsrc1, EXTTRAILSOURCE /app/ogg19c/dirdat/es, BEGIN NOW
EXTRACT added.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 20> ADD RMTTRAIL /app/ogg19c/dirdat/es, EXTRACT pmpsrc1
RMTTRAIL added.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 22> START EXTRACT pmpsrc1
Sending START request to MANAGER …
EXTRACT PMPSRC1 starting
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 28> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXTSRC1 00:00:00 00:00:01
EXTRACT RUNNING PMPSRC1 00:07:30 00:00:09
11. Configure the GoldenGate replicat process for target Goldengate.
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 11> edit params reptgt1
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 12> view param reptgt1
REPLICAT reptgt1
USERIDALIAS ggadmin
DISCARDFILE /app/ogg19c/dirrpt/reptgt1.dsc, PURGE
SOURCECATALOG GGTGTPDB1
MAP GGSRCPDB1.HR.TEST, target GGTGTPDB1.HR.TEST;
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 13> ADD REPLICAT reptgt1,integrated exttrail /app/ogg19c/dirdat/es
REPLICAT (Integrated) added.
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 14> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
REPLICAT STOPPED REPTGT1 00:00:00 00:00:03
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 15> start REPTGT1
Sending START request to MANAGER …
REPLICAT REPTGT1 starting
GGSCI (oggtgt as c##ggadmin@ggtgt/GGTGTPDB1) 16> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
REPLICAT RUNNING REPTGT1 00:00:00 00:00:10
12. Test the replcation by inserting records in HR.TEST table of source PDB.
–On source GoldenGate, add trandata for the source table HR.TEST
GGSCI (oggsrc) 1> dblogin useridalias ggadmin
Successfully logged into database CDB$ROOT.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 2> add trandata GGSRCPDB1.HR.TEST
2026-11-15 12:15:54 WARNING OGG-06439 No unique key is defined for table TEST. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2026-11-15 12:15:54 INFO OGG-15130 No key found for table GGSRCPDB1.HR.TEST. All viable columns will be logged.
2026-11-15 12:15:55 INFO OGG-15132 Logging of supplemental redo data enabled for table GGSRCPDB1.HR.TEST.
2026-11-15 12:15:55 INFO OGG-15133 TRANDATA for scheduling columns has been added on table GGSRCPDB1.HR.TEST.
2026-11-15 12:15:55 INFO OGG-15135 TRANDATA for instantiation CSN has been added on table GGSRCPDB1.HR.TEST.
2026-11-15 12:15:55 INFO OGG-10471 ***** Oracle Goldengate support information on table HR.TEST *****
Oracle Goldengate support native capture on table HR.TEST.
Oracle Goldengate marked following column as key columns on table HR.TEST: ID, NAME
No unique key is defined for table HR.TEST.
GGSCI (oggsrc as c##ggadmin@ggsrc/CDB$ROOT) 3> INFO TRANDATA GGSRCPDB1.HR.TEST
2026-11-15 12:16:30 INFO OGG-10471 ***** Oracle Goldengate support information on table HR.TEST *****
Oracle Goldengate support native capture on table HR.TEST.
Oracle Goldengate marked following column as key columns on table HR.TEST: ID, NAME
No unique key is defined for table HR.TEST.
Logging of supplemental redo log data is enabled for table GGSRCPDB1.HR.TEST.
Columns supplementally logged for table GGSRCPDB1.HR.TEST: “ID”, “NAME”.
Prepared CSN for table GGSRCPDB1.HR.TEST: 2582073
–Insert records into the source table
SQL> conn hr/hr@GGSRCPDB1
Connected.
SQL> insert into test(id,name) values(1,’ABC’);
1 row created.
SQL> commit;
Commit complete.
SQL> insert into test(id,name) values(2,’XYZ’);
1 row created.
SQL> commit;
Commit complete.
–On target, check the table whether replication happened or not.
SQL> show con_name
CON_NAME
——————————
GGTGTPDB1
SQL> select * from hr.test;
ID NAME
———- ——————–
2 XYZ
1 ABC
Also, the commands below provide the information about record processing statistics.
stats EXTSRC1,table GGSRCPDB1.HR.TEST
stats PMPSRC1,table GGSRCPDB1.HR.TEST
stats REPTGT1,table GGTGTPDB1.HR.TEST
The unidirectional Oracle GoldenGate replication has been successfully configured, and the source and target databases are now synchronized.
Disclaimer:
Please note the above information is only for educational purpose and practised in personal test database only. Always test in test database before implementing in production database. The pre-requisites and ways of implementing may vary from one environment to another. Hence, not providing guarantee that it will work in your environment.