1. The main components of a GoldenGate architecture are the extract, trail files, data pump, server collector, manager, and replicat processes.
2. The extract collects changes from source databases and sends them to the manager. Trail files convert the data for replication and are written on both source and target systems.
3. The data pump sends data in large blocks across TCP/IP. The server collector accepts data on the target system and writes it to remote trails. The manager controls processes and stores change vectors in trail files. The replicat recovers changes and applies them to the target database.
1. The main components of a GoldenGate architecture are the extract, trail files, data pump, server collector, manager, and replicat processes.
2. The extract collects changes from source databases and sends them to the manager. Trail files convert the data for replication and are written on both source and target systems.
3. The data pump sends data in large blocks across TCP/IP. The server collector accepts data on the target system and writes it to remote trails. The manager controls processes and stores change vectors in trail files. The replicat recovers changes and applies them to the target database.
1. The main components of a GoldenGate architecture are the extract, trail files, data pump, server collector, manager, and replicat processes.
2. The extract collects changes from source databases and sends them to the manager. Trail files convert the data for replication and are written on both source and target systems.
3. The data pump sends data in large blocks across TCP/IP. The server collector accepts data on the target system and writes it to remote trails. The manager controls processes and stores change vectors in trail files. The replicat recovers changes and applies them to the target database.
1. The main components of a GoldenGate architecture are the extract, trail files, data pump, server collector, manager, and replicat processes.
2. The extract collects changes from source databases and sends them to the manager. Trail files convert the data for replication and are written on both source and target systems.
3. The data pump sends data in large blocks across TCP/IP. The server collector accepts data on the target system and writes it to remote trails. The manager controls processes and stores change vectors in trail files. The replicat recovers changes and applies them to the target database.
Download as TXT, PDF, TXT or read online from Scribd
Download as txt, pdf, or txt
You are on page 1/ 9
GoldenGate Setup
------------------ The main components of the GoldenGate architecture are :
EXTRACT : Collects the changes vectors from the redo logs and archive logs file from the source database, and send them to the manager process (like capture process for streams). It regulary checkpoints its R/W position to a file and Can have the following status : - STOPPED - RUNNING - STARTING - ABENED (abnormal end)
TRAIL FILES : GoldenGate converts data to replicate into a special format which is written to trail files both on the source and target systems. They are called local trail on the source system and remote trail on the target system.
DATA PUMP : On the local trail, GoldenGate requires an additional extract process called data pump to send data in large block accross TCP/IP.
SERVER COLLECTOR : This process runs on the target system and accepts data from the source and writes it to the remote trails (like propagation process for streams).
MANAGER : Runs on both source and target systems. Stores the change vectors in TRAIL files. It controls the starting, monitoring and restarting processes, the reporting errors and events. Can have the following status : - STOPPED - RUNNING REPLICAT : Recovers the change vectors from trail files and apply them to the target database (like apply process for streams). It regulary checkpoints its R/W position to a file. Can have the following status : - STOPPED - RUNNING - STARTING - ABENED (abnormal end)
GGSCI : GoldenGate Software Command Interface. It is a tool that provides a set of
commands to create, configurate and monitors GoldenGate.
5. Create a schema that will contain the Oracle GoldenGate DDL objects.
SQL> create tablespace gg_tbls datafile '/u02/oradata/OGG1/gg_tbls.dbf' size 100m
reuse autoextend on; Tablespace created.
SQL> create user ggate identified by oracle default tablespace gg_tbls quota unlimited on gg_tbls; User created.
SQL> grant create session, connect, resource to ggate;
Grant succeeded.
SQL> grant dba to ggate; -- just in case
Grant succeeded.
SQL> grant execute on utl_file to ggate;
Grant succeeded.
OR
GRANT CONNECT, RESOURCE TO ggate;
GRANT SELECT ANY DICTIONARY, SELECT ANY TABLE TO ggate; GRANT CREATE TABLE TO ggate; GRANT FLASHBACK ANY TABLE TO ggate; GRANT EXECUTE ON dbms_flashback TO ggate; GRANT EXECUTE ON utl_file TO ggate; GRANT CREATE ANY TABLE TO ggate; GRANT INSERT ANY TABLE TO ggate; GRANT UPDATE ANY TABLE TO ggate; GRANT DELETE ANY TABLE TO ggate; GRANT DROP ANY TABLE TO ggate; GRANT ALTER ANY TABLE TO ggate; GRANT ALTER SYSTEM TO ggate; GRANT LOCK ANY TABLE TO ggate; GRANT SELECT ANY TRANSACTION to ggate; ALTER USER ggate QUOTA UNLIMITED ON ogg_data;
6. Make sure you can tnsping both databases from each host listener.ora ------------ SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = OGG1) (ORACLE_HOME = /u01/app/oracle/product/11.2.0.4/dbhome_1) (SID_NAME = ogg1)) (SID_DESC = (GLOBAL_DBNAME = OGG2) (ORACLE_HOME = /u01/app/oracle/product/11.2.0.4/dbhome_1) (SID_NAME = OGG2)))
7. Change the directory on Golden Gate home directory and run scripts for creating all necessary objects for support ddl replication. [oracle@db ~]$ cd /u01/app/oracle/product/11.2.0/oggcore_1 [oracle@db gg]$ sqlplus / as sysdba
SQL> @marker_setup.sql SQL> @ddl_setup.sql SQL> @role_setup.sql SQL> grant GGS_GGSUSER_ROLE to ggate; SQL> @ddl_enable.sql
[oracle@OGG1 ~]$ cd /u01/app/oracle/product/11.2.0/oggcore_1
[oracle@OGG1 oggcore_1]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Fri Apr 15 04:09:32 2016
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @marker_setup.sql
Marker setup script
You will be prompted for the name of a schema for the Oracle GoldenGate database objects. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation.
Please enter the name of a schema for the GoldenGate database objects: Setting schema name to GGATE
MARKER TABLE ------------------------------- OK
MARKER SEQUENCE ------------------------------- OK
Script complete. SQL> @ddl_setup.sql
Oracle GoldenGate DDL Replication setup script
Verifying that current user has privileges to install DDL Replication...
You will be prompted for the name of a schema for the Oracle GoldenGate database objects. NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle 11g and later, it can be enabled. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation.
Enter Oracle GoldenGate schema name:ggate
Working, please wait ... Spooling to file ddl_setup_spool.txt
Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...
----------------------------------------------------------------------------------- ------------------------------------- SUCCESSFUL installation of DDL Replication software components
Script complete. SQL> @role_setup.sql
GGS Role setup script
This script will drop and recreate the role GGS_GGSUSER_ROLE To use a different role name, quit this script and then edit the params.sql script to change the gg_role parameter to the preferred name. (Do not run the script.)
You will be prompted for the name of a schema for the GoldenGate database objects. NOTE: The schema must be created prior to running this script. NOTE: Stop all DDL replication before starting this installation.
Enter GoldenGate schema name:ggate
Wrote file role_setup_set.txt
PL/SQL procedure successfully completed.
Role setup script complete
Grant this role to each user assigned to the Extract, GGSCI, and Manager processes, by using the following SQL command:
GRANT GGS_GGSUSER_ROLE TO <loggedUser>
where <loggedUser> is the user assigned to the GoldenGate processes.
SQL> grant GGS_GGSUSER_ROLE to ggate;
Grant succeeded.
SQL> @ddl_enable.sql
Trigger altered.
SQL>
SQL> alter system set enable_goldengate_replication=true;
System altered.
After that, add information about your Oracle GoldenGate DDL scheme into file GLOBALS. You should input this row into the file "GGSCHEMA ggate". [oracle@db gg]$ ./ggsci
Oracle GoldenGate Command Interpreter for Oracle
Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230_FBO Linux, x86, 32bit (optimized), Oracle 11g on Apr 23 2012 08:09:25
Copyright (C) 1995, 2012, Oracle and/or its affiliates. All rights reserved.
GGSCI (db.us.oracle.com) 1> EDIT PARAMS ./GLOBALS
GGSCHEMA OGG_USER
GGSCI (db.us.oracle.com) 2>
--Create the schemes for replication on both hosts (OGG1, OGG2).
Source database (OGG1):
SQL> create user source identified by oracle default tablespace users temporary tablespace temp; User created.
SQL> grant connect,resource,unlimited tablespace to source;
Grant succeeded.
SQL> Target database(OGG2): SQL> create user target identified by oracle default tablespace users temporary tablespace temp;
User created.
SQL> grant connect,resource,unlimited tablespace to target;
Grant succeeded.
SQL> grant dba to target; -- or particular grants
Grant succeeded.
SQL> Create the directory for trail files on ***BOTH HOSTS and create directory for ****discard file on OGG2 host only.
In this example the Data Pump process will be called dp1 On the source server create the parameter file for Data Pump process dp1: GGSCI (db.us.oracle.com) 10> add extract pump1, exttrailsource /u01/app/oracle/product/11.2.0/oggcore_1/dirdat/tr, begin now EXTRACT added.
Configure the manager process [oracle@OGG2 oggcore_1]$ ./ggsci
Oracle GoldenGate Command Interpreter for Oracle
Version 12.2.0.1.0 OGGCORE_12.2.0.1.0_PLATFORMS_151101.1925.2_FBO Linux, x64, 64bit (optimized), Oracle 11g on Nov 11 2015 01:38:14 Operating system character set identified as UTF-8.
Copyright (C) 1995, 2015, Oracle and/or its affiliates. All rights reserved.
