PDF Oracle Goldengate Basic Architecture DL

1. Oracle GoldenGate Basic Architecture.
Source Database - GoldenGate extracts the information from the source database.
The source database may be from any of the following vendors.
- Oracle Database
- TimesTen
- MySQL
- IBM DB2
- Microsoft SQL Server
- Teradata
- Sybase
- Enscribe
- SQL/MX
Capture(Local Extract) - Capture is the primary process in which all the commited DML
and
DDL changes are extracted from the source database.
Source Trail - The data extracted from the source database is written to the source trail,
which is basically a staging file and will be used by other processes (Ex: datapump).
Datapump - The datapump which is a goldengate process(not to be confused with oracle

datapump), reads the information from the source trail, transfers it to the target host via
TCP/IP and writes it down to the remote trail.
Network - GoldenGate sends the data from the source trail via TCP/IP to the target host
and writes it in the remote trail.
Collector - The collector process is automatically started by the manager. This process
runs in the background, It captures and writes all the data received to the remote trail.
Remote Trail - Remote trail is similar to source trail. The only difference between the
two is that the remote trail is at the target host and the source trail is at the source
Database
host.
Delivery(Replicat) - The delivery process applies all the changes to the target database by
reading the remote trail. The changes are done to the target database in the same order as
they
were done in the source database.
Target Database - Target database is the database at which all the changes are applied.
It can be same or different from the source database.
GOLDEN GATE WORKFLOW:
1. Oracle 11g GoldenGate Installation.
Download the GoldenGate software from Oracle Edelivery.
Select a Product Pack: Oracle Fusion Middleware

Platform: Linux X86
Download the Oracle GoldenGate media pack.
Create the directory for GoldenGate.
$ mkdir -p /u01/app/gg
Make changes in your bash profile.
Add path variable.
PATH=/u01/app/gg:$PATH; export PATH
LD library entry should look something like this.
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib:/u01/app/gg; export LD_LIBRARY_PATH
Reload bash profile
$ . ./.bash_profile
copy the tar file to the "gg" directory and untar
tar -xvof fbo_ggs_Linux_x86_ora11g_32bit.tar
Invoke the GoldenGate Software Command Interface.
[oracle@canada gg]$ ggsci
Oracle GoldenGate Command Interpreter for Oracle

Version 11.1.1.1.2 OGGCORE_11.1.1.1.2_PLATFORMS_111004.2100
Linux, x86, 32bit (optimized), Oracle 11g on Oct 4 2011 23:53:33
Copyright (C) 1995, 2011, Oracle and/or its affiliates. All rights reserved.
GGSCI (canada) 1> create subdirs
Code:
Creating subdirectories under current directory /u01/app/gg
Parameter files /u01/app/gg/dirprm: created

Report files /u01/app/gg/dirrpt: created
Checkpoint files /u01/app/gg/dirchk: created
Process status files /u01/app/gg/dirpcs: created
SQL script files /u01/app/gg/dirsql: created
Database definitions files /u01/app/gg/dirdef: created
Extract data files /u01/app/gg/dirdat: created
Temporary files /u01/app/gg/dirtmp: created
Veridata files /u01/app/gg/dirver: created
Veridata Lock files /u01/app/gg/dirver/lock: created
Veridata Out-Of-Sync files /u01/app/gg/dirver/oos: created
Veridata Out-Of-Sync XML files /u01/app/gg/dirver/oosxml: created
Veridata Parameter files /u01/app/gg/dirver/params: created
Veridata Report files /u01/app/gg/dirver/report: created
Veridata Status files /u01/app/gg/dirver/status: created
Veridata Trace files /u01/app/gg/dirver/trace: created
Stdout files /u01/app/gg/dirout: created
GGSCI (canada) 2> exit
Before going any further make sure your database is in

archivelog mode.
Prepare your database for replication.
In order to extract committed transactions from the source database

the database must be configured with supplemental logging on primary
key columns.
SQL> alter database add supplemental log data (primary key) columns;
Database altered.
Do a logswitch to start supplemental logging.
SQL> alter system switch logfile;
System altered.
SQL> select supplemental_log_data_min, supplemental_log_data_pk,

supplemental_log_data_ui from v$database;
SUPPLEME SUP SUP

-------- --- ---
IMPLICIT YES NO
SUPPLEMENTAL_LOG_DATA_MIN: Ensures that logminer will have sufficient information.

SUPPLEMENTAL_LOG_DATA_PK: Indicates whether all columns of the primary key are placed
into
the redo log whenever an update is performed.
SUPPLEMENTAL_LOG_DATA_UI: Indicated whether all columns belonging to the unique key
are placed
into the redo log if any of the unique columns are modified.
Create a Tablespace and user for GoldenGate.
SQL> create tablespace golden datafile'/u01/app/oracle/oradata/orcl/golden01.dbf' size

100m
2 autoextend on
3 extent management local
4 segment space management auto;
Tablespace created.
SQL> create user ggs_admin identified by ggs_admin

2 temporary tablespace temp
3 default tablespace golden
4 quota unlimited on golden;
User created.
SQL> grant dba to ggs_admin;
Grant succeeded.
SQL> alter system set recyclebin=off scope=spfile;
System altered.
--Set recyclebin to off, Necessary for DDL Replication from Oracle 10g onwards.
SQL> shutdown immediate

SQL> startup
1. Oracle GoldenGate Basic DML Replication.
Schema to be replicated "SCOTT".
SOURCE DATABASE.
OS - Red Hat Enterprise Linux Server release 5.4
Hostname - canada
IP Address - 192.168.1.100
Database - Oracle 11g Release 2.

SID - orcl
GoldenGate Version - 11.1.1.1.2
Sample "/etc/hosts" file.
Code:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.1.100 canada canada

192.168.1.200 london london
TARGET DATABASE.
OS - Red Hat Enterprise Linux Server release 5.4
Hostname - london
IP Address - 192.168.1.200
Database - Oracle 11g Release 2
SID - dup
GoldenGate Version - 11.1.1.1.2
Sample "/etc/hosts" file.
Code:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.1.100 canada canada

192.168.1.200 london london
Install GoldenGate Software on both the machines.---link
--make sure supplemental log data is enabled only for the source database.
Ping from both the machines to ensure network connectivity.
--Do from both machines.
# ping canada
# ping london
Both the databases should be in archivelog mode.
ON SOURCE
[oracle@canada gg]$ export ORACLE_SID=orcl

[oracle@canada gg]$ ggsci

GGSCI (canada) 1> dblogin userid ggs_admin, password ggs_admin
Successfully logged into database.
--Add supplemental logging on the source database for tables

--in the SCOTT users schema.
GGSCI (canada) 2> add trandata SCOTT.*
Configure manager service on both Source and Target.
ggsci > edit param mgr
port 7980
purgeoldextracts dirdat/*, usecheckpoints, minkeepdays 2
-The above parameter instructs the GoldenGate software to

-delete all the trails which have been used by the Extract
-and Replicat process after 2 days.
ggsci > start manager
Manager started.
ggsci > info manager
Manager is running (IP port canada.7980).
Configure local extract on source.

ggsci> edit param ext1
extract ext1
userid ggs_admin, password ggs_admin
exttrail dirdat/t1
table SCOTT.*;
GGSCI (canada) 8> add extract ext1, tranlog, begin now

EXTRACT added.
GGSCI (canada) 9> add exttrail dirdat/t1, extract ext1, megabytes 100
EXTTRAIL added.
GGSCI (canada) 10> start extract ext1
Sending START request to MANAGER ...

EXTRACT EXT1 starting
GGSCI (canada) 13> info extract ext1
Code:
EXTRACT EXT1 Last Started 2012-03-15 20:47 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:03 ago)
Log Read Checkpoint Oracle Redo Logs
2012-03-15 20:48:15 Seqno 5, RBA 6204416
To stop the extract.
ggsci > stop extract ext1
Configure datapump on source.
GGSCI> edit param dpump1
extract dpump1
passthru
rmthost london, mgrport 7980
rmttrail dirdat/t2
table SCOTT.*;
--passthru parameter is used here because we are not using any data
--filteration or column mapping. The source and target data structures
--are identical.
GGSCI (canada) 15> add extract dpump1, exttrailsource dirdat/t1

EXTRACT added.
GGSCI (canada) 16> add rmttrail dirdat/t2, extract dpump1, megabytes 100
RMTTRAIL added.
GGSCI (canada) 17> start extract dpump1

EXTRACT DPUMP1 starting
To stop datapump.
GGSCI> stop extract dpump1
GGSCI (canada) 18> info extract dpump1
Code:
EXTRACT DPUMP1 Last Started 2012-03-15 20:58 Status RUNNING
Log Read Checkpoint File dirdat/t1000000
First Record RBA 943
GGSCI (canada) 19> info all
Code:
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING DPUMP1 00:00:00 00:00:00
EXTRACT RUNNING EXT1 00:00:00 00:00:02
Configure Replicat on target database.
[oracle@london gg]$ export ORACLE_SID=dup

[oracle@london gg]$ ggsci

-create checkpoint table
GGSCI (london) 3> dblogin userid ggs_admin, password ggs_admin

Successfully logged into database.
GGSCI (london) 4> add checkpointtable ggs_admin.chkpt
Successfully created checkpoint table GGS_ADMIN.CHKPT.
GGSCI (london) 1> edit param repl1
replicat repl1
handlecollisions
assumetargetdefs
discardfile dirrpt/repl1.dsc, append
discardrollover at 5:00 on sunday
map SCOTT.*, target SCOTT.*;
--handlecollisions helps in detection and resolution of DML errors, while applying

--changes to the target.
--assumetargetdefs parameter tells the GoldenGate software that source and

--target tables are identical.
--discardfile parameter instructs the GoldenGate software to write

--all the errors encountered to the file specified.
--discardrollover parameter instructs the goldengate software to create

--a new discardfile every sunday at 5:00.
--The old discard file can be safely deleted in order to avoid
--space constraints.
GGSCI (london) 5> add replicat repl1, exttrail dirdat/t2, checkpointtable ggs_admin.chkpt
REPLICAT added.
GGSCI (london) 6> start replicat repl1

REPLICAT REPL1 starting
To stop replicat service.
GGSCI> stop replicat repl1
GGSCI (london) 7> info replicat repl1

Code:
REPLICAT REPL1 Last Started 2012-03-15 21:28 Status RUNNING
Log Read Checkpoint File dirdat/t2000000
First Record RBA 0
GGSCI (london) 8> info all
Code:
Program Status Group Lag Time Since Chkpt
MANAGER RUNNING
REPLICAT RUNNING REPL1 00:00:00 00:00:03
Verify.
On Source
SQL> conn scott/tiger
SQL> update emp set sal=13000 where ename='MILLER';
1 row updated.
SQL> commit;
Commit complete.
On Target
SQL>conn scott/tiger
SQL> select sal from emp where ename='MILLER';
SAL
----------
13000
Also,
SQL> exit
[oracle@london gg]$ export ORACLE_SID=dup
[oracle@london gg]$ ggsci

GGSCI (london) 1> stats replicat repl1
Code:
Sending STATS request to REPLICAT REPL1 ...
Start of Statistics at 2012-03-15 21:35:11.
Replicating from SCOTT.EMP to SCOTT.EMP:
*** Total statistics since 2012-03-15 21:31:54 ***

Total inserts 0.00
Total updates 1.00
Total deletes 0.00
Total discards 0.00
Total operations 1.00
*** Daily statistics since 2012-03-15 21:31:54 ***

Total inserts 0.00
Total updates 1.00
Total deletes 0.00
Total discards 0.00
*** Hourly statistics since 2012-03-15 21:31:54 ***

Total inserts 0.00
Total updates 1.00
Total deletes 0.00
Total discards 0.00
*** Latest statistics since 2012-03-15 21:31:54 ***

Total inserts 0.00
Total updates 1.00
Total deletes 0.00
Total discards 0.00
End of Statistics.
--At this point your basic DML unidirectional replication is complete.
1. Oracle GoldenGate DDL Replication.
Points to consider before implementing DDl replication.
1) Recyclebin feature should be turned off(Oracle 10g onwards).
2) The source and target schemas must be identical.

3) DDL replication is supported only between two systems. Bi-directional DDL replication
is also supported. DDL replication between one to many systems is not supported.
4) DDl statements that are less than 2MB in length will be replicated automatically,
any statement longer than that will have to be manually processed by Golden Gate script.
5) Passthru paramater is to be configured while configuring datapump for tables that require
DDL replication.
Main differences when implementing DDL replication as compared to DML replication is

that you have to create GLOBALS file in both source and target schema.
Run certain scripts on source to facilitate DDL replication.
Add one additional parameter to the local extract

file (i.e ddl include mapped objname "SCOTT.*).
On Source
SQL> grant execute on utl_file to ggs_admin;
Grant succeeded.
[oracle@canada gg]$ export ORACLE_SID=orcl

[oracle@canada gg]$ sqlplus
SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 27 21:50:27 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter user-name: / as sysdba
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @marker_setup.sql
Code:
Marker setup 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:ggs_admin
Marker setup table script complete, running verification script...

Please enter the name of a schema for the GoldenGate database objects:
Setting schema name to GGS_ADMIN
MARKER TABLE
-------------------------------
OK
MARKER SEQUENCE
-------------------------------
OK
Script complete.
SQL> @ddl_setup.sql
Code:
GoldenGate DDL Replication setup script
Verifying that current user has privileges to install DDL Replication...
NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle
11g and later, it can be
enabled.
You will be prompted for the mode of installation.

To install or reinstall DDL replication, enter INITIALSETUP
To upgrade DDL replication, enter NORMAL
Enter mode of installation:INITIALSETUP
Working, please wait ...

Spooling to file ddl_setup_spool.txt
Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...
Check complete.
Using GGS_ADMIN as a GoldenGate schema name, INITIALSETUP as a mode of installation.
Working, please wait ...
DDL replication setup script complete, running verification script...

Please enter the name of a schema for the GoldenGate database objects:
Setting schema name to GGS_ADMIN
DDLORA_GETTABLESPACESIZE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
CLEAR_TRACE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
CREATE_TRACE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
TRACE_PUT_LINE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
INITIAL_SETUP STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
DDLVERSIONSPECIFIC PACKAGE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
DDLREPLICATION PACKAGE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
DDLREPLICATION PACKAGE BODY STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
DDL HISTORY TABLE

-----------------------------------
OK
DDL HISTORY TABLE(1)

-----------------------------------
OK
DDL DUMP TABLES

-----------------------------------
OK
DDL DUMP COLUMNS

-----------------------------------
OK
DDL DUMP LOG GROUPS

-----------------------------------
OK
DDL DUMP PARTITIONS

-----------------------------------
OK
DDL DUMP PRIMARY KEYS

-----------------------------------
OK
DDL SEQUENCE
-----------------------------------
OK
GGS_TEMP_COLS
-----------------------------------
OK
GGS_TEMP_UK
-----------------------------------
OK
DDL TRIGGER CODE STATUS:
Line/pos Error
---------- -----------------------------------------------------------------
No errors No errors
DDL TRIGGER INSTALL STATUS

-----------------------------------
OK
DDL TRIGGER RUNNING STATUS

-----------------------------------
ENABLED
STAYMETADATA IN TRIGGER
-----------------------------------
OFF
DDL TRIGGER SQL TRACING

-----------------------------------
0
DDL TRIGGER TRACE LEVEL

-----------------------------------
0
LOCATION OF DDL TRACE FILE

-----------------------------------------------------------------
/u01/app/oracle/diag/rdbms/orcl/orcl/trace/ggs_ddl_trace.log
Analyzing installation status...
STATUS OF DDL REPLICATION

------------------------------------------------------------------
SUCCESSFUL installation of DDL Replication software components
Script complete.
SQL> @role_setup.sql
Code:
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.)

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
where is the user assigned to the GoldenGate processes.
SQL> GRANT GGS_GGSUSER_ROLE TO ggs_admin;
Grant succeeded.
SQL> @ddl_enable.sql
Trigger altered.
Do Both on Source and Target
GGSCI>edit param GLOBALS
GGSCHEMA GGS_ADMIN
On Source
--parameter to include in local extract file ext1
GGSCI> edit param ext1
exttrail dirdat/t1
ddl include mapped objname "SCOTT.*"
table SCOTT.*;
Lets check
On Source
SQL> alter table emp add ncol varchar2(10);
Table altered.
SQL> desc emp;
Code:
Name Null? Type
----------------------------------------- -------- ----------------------------
EMPNO NOT NULL NUMBER(4)
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(4)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(2)
NCOL VARCHAR2(10)
On Target.
SQL> desc emp;
Code:
Name Null? Type
----------------------------------------- -------- ----------------------------
EMPNO NOT NULL NUMBER(4)
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(4)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(2)
NCOL VARCHAR2(10)
Also
On Source
SQL> create table test as select * from emp;
Table created.
SQL> select * from tab;

Code:
TNAME TABTYPE CLUSTERID
------------------------------ ------- ----------
BONUS TABLE
DEPT TABLE
EMP TABLE
SALGRADE TABLE
TEST TABLE
On Target
SQL> select * from tab;
Code:
TNAME TABTYPE CLUSTERID
------------------------------ ------- ----------
BONUS TABLE
DEPT TABLE
EMP TABLE
SALGRADE TABLE
TEST TABLE
1. Oracle Goldengate 11g Initial Load Using Direct Load Method.
This article focuses on initial synchronization of source and

target databases by using Golden Gate initial direct load method for the
purpose of zero downtime DML replication.
Prerequisites:
1) Target Tables should be empty. Otherwise you can get duplicate row errors.
2) Disable Foreign Key and Check Constraints. They can be enabled later on
when the initial load is complete.
3) (Optional) Remove indexes from target tables as they may slow down the
initial loading process.
4) To use handlecollisions function, each target table must have a
primary or unique key. If that's not possible use the KEYCOLS
option of the TABLE and MAP parameters. Even if that is not possible
then quiesce your database for the duration of intial load.
Schema to be replicated "SCOTT"
1) Install GoldenGate on both the machines.
2) Disable Foreign key and check constraints and triggers on target tables.
SQL> select CONSTRAINT_NAME,CONSTRAINT_TYPE,TABLE_NAME,status from

dba_constraints where owner='SCOTT';
Code:
CONSTRAINT_NAME C TABLE_NAME STATUS
------------------------------ - ------------------------------ --------
FK_DEPTNO R EMP ENABLED
PK_DEPT P DEPT ENABLED
PK_EMP P EMP ENABLED
SQL> alter table emp disable constraint fk_deptno;
Table altered.
3) Configure and start extract process on source.
4) configure and start Data Pump process on source.
5) Configure Initial load extract and replicat processes.
On Source
GGSCI (canada.example.com) 15> edit param iniload1
extract iniload1
rmthost newyork, mgrport 7980
rmttask replicat, group iniload2
table SCOTT.*;
#RMTTASK - Instructs the manager process on the target system to

#start the initial-load replicat process without manual intervention
#as a one time task.
GGSCI (canada.example.com) 18> add extract iniload1, sourceistable

EXTRACT added.
#SOURCEISTABLE - Tells the extract process to extract records directly

from the source tables rather than from the redo logs.
On Target
GGSCI (newyork.example.com) 5> edit param iniload2
replicat iniload2
assumetargetdefs
map SCOTT.*, target SCOTT.*;
GGSCI (newyork.example.com) 9> add replicat iniload2, specialrun

REPLICAT added.
#SpecialRun - Runs as a onetime process with distinct beginning and end,
#which is different from continuous processing as it does not have a
#specific end point.
On Source
Start initial load extract process on source. The replicat process

on target will start automatically.
GGSCI (canada.example.com) 19> start extract iniload1
Code:
EXTRACT INILOAD1 starting
GGSCI (canada.example.com) 30> info extract iniload1
Code:
EXTRACT INILOAD1 Last Started 2012-11-13 21:48 Status RUNNING
Checkpoint Lag Not Available
Log Read Checkpoint Table SCOTT.DEPT
2012-11-13 21:48:32 Record 1
Task SOURCEISTABLE
GGSCI (canada.example.com) 31> view report iniload1
Code:
2012-11-13 21:48:27 INFO OGG-01017 Wildcard resolution set to IMMEDIATE because
SOURCEISTABLE is used.
***********************************************************************
Oracle GoldenGate Capture for Oracle
Starting at 2012-11-13 21:48:27

***********************************************************************
Operating System Version:

Linux
Version #1 SMP Tue Aug 18 15:51:54 EDT 2009, Release 2.6.18-164.el5
Node: canada.example.com
Machine: i686
soft limit hard limit
Address Space Size : unlimited unlimited
Heap Size : unlimited unlimited
File Size : unlimited unlimited
CPU Time : unlimited unlimited
Process id: 7671
Description:
***********************************************************************
** Running with the following parameters **
***********************************************************************
extract iniload1
userid ggs_admin, password *********
rmthost newyork, mgrport 7980
rmttask replicat, group iniload2
table SCOTT.*;
TABLEWildcard resolved (entry SCOTT.*):
table SCOTT.BONUS;
2012-11-13 21:48:27 WARNING OGG-00869 No unique key is defined for table BONUS. All
viable columns will b
e used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to
define the key.
Using the following key columns for source table SCOTT.BONUS: ENAME, JOB, SAL, COMM.
table SCOTT.DEPT;
Using the following key columns for source table SCOTT.DEPT: DEPTNO.
table SCOTT.EMP;
Using the following key columns for source table SCOTT.EMP: EMPNO.
table SCOTT.SALGRADE;
2012-11-13 21:48:27 WARNING OGG-00869 No unique key is defined for table SALGRADE.
All viable columns wil
l be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used
to define the key.
Using the following key columns for source table SCOTT.SALGRADE: GRADE, LOSAL, HISAL.
CACHEMGR virtual memory values (may have been adjusted)

CACHEBUFFERSIZE: 64K
CACHESIZE: 2G
CACHEBUFFERSIZE (soft max): 4M
CACHEPAGEOUTSIZE (normal): 4M
PROCESS VM AVAIL FROM OS (min): 2.87G
CACHESIZEMAX (strict force to disk): 2.64G
Database Version:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
Database Language and Character Set:

NLS_LANG environment variable specified has invalid format, default value will be
used.
NLS_LANG environment variable not set, using default value AMERICAN_AMERICA.US7ASCII.
NLS_LANGUAGE = "AMERICAN"
NLS_TERRITORY = "AMERICA"
NLS_CHARACTERSET = "WE8MSWIN1252"
Warning: your NLS_LANG setting does not match database server language setting.
Please refer to user manual for more information.
Processing table SCOTT.BONUS
Processing table SCOTT.DEPT
Processing table SCOTT.EMP
Processing table SCOTT.SALGRADE
***********************************************************************
* ** Run Time Statistics ** *
***********************************************************************
Report at 2012-11-13 21:48:50 (activity since 2012-11-13 21:48:27)
Output to iniload2:
From Table SCOTT.DEPT:

# inserts: 4
# updates: 0
# deletes: 0
# discards: 0
From Table SCOTT.EMP:
# inserts: 14
# updates: 0
# deletes: 0
# discards: 0
From Table SCOTT.SALGRADE:
# inserts: 5
# updates: 0
# deletes: 0
# discards: 0
REDO Log Statistics

Bytes parsed 0
Bytes output 3473
6) Enable all the constraints and triggers on the target.
SQL> alter table emp enable constraint fk_deptno;
Table altered.
7) Configure and start Replicat process on target.

1. Delete or Remove Extract & Replicat Processes (Golden Gate 11g).
1) Stop extract/replicat.
kill extract group_name

kill replicat group_name
2) Delete extracat / replicat.
delete extract group_name

delete replicat group_name
3) Cleanup.
cleanup extract group_name

cleanup replicat group_name

PDF Oracle Goldengate Basic Architecture DL

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDF Oracle Goldengate Basic Architecture DL

Uploaded by

Copyright:

Available Formats

1. Oracle GoldenGate Basic Architecture.

Datapump - The datapump which is a goldengate process(not to be confused with oracle

Download the GoldenGate software from Oracle Edelivery.

Select a Product Pack: Oracle Fusion Middleware

Download the Oracle GoldenGate media pack.

Create the directory for GoldenGate.

Make changes in your bash profile.

Add path variable.

PATH=/u01/app/gg:$PATH; export PATH

LD library entry should look something like this.

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib:/u01/app/gg; export LD_LIBRARY_PATH

Reload bash profile

copy the tar file to the "gg" directory and untar

tar -xvof fbo_ggs_Linux_x86_ora11g_32bit.tar

Invoke the GoldenGate Software Command Interface.

[oracle@canada gg]$ ggsci

Oracle GoldenGate Command Interpreter for Oracle

GGSCI (canada) 1> create subdirs

Parameter files /u01/app/gg/dirprm: created

GGSCI (canada) 2> exit

Before going any further make sure your database is in

Prepare your database for replication.

In order to extract committed transactions from the source database

Do a logswitch to start supplemental logging.

SQL> alter system switch logfile;

SQL> select supplemental_log_data_min, supplemental_log_data_pk,

SUPPLEME SUP SUP

SUPPLEMENTAL_LOG_DATA_MIN: Ensures that logminer will have sufficient information.

Create a Tablespace and user for GoldenGate.

SQL> create tablespace golden datafile'/u01/app/oracle/oradata/orcl/golden01.dbf' size

SQL> create user ggs_admin identified by ggs_admin

SQL> grant dba to ggs_admin;

SQL> alter system set recyclebin=off scope=spfile;

SQL> shutdown immediate

1. Oracle GoldenGate Basic DML Replication.

Schema to be replicated "SCOTT".

OS - Red Hat Enterprise Linux Server release 5.4

Database - Oracle 11g Release 2.

GoldenGate Version - 11.1.1.1.2

Sample "/etc/hosts" file.

127.0.0.1 localhost.localdomain localhost

192.168.1.100 canada canada

OS - Red Hat Enterprise Linux Server release 5.4

Database - Oracle 11g Release 2

GoldenGate Version - 11.1.1.1.2

Sample "/etc/hosts" file.

127.0.0.1 localhost.localdomain localhost

192.168.1.100 canada canada

Install GoldenGate Software on both the machines.---link

Ping from both the machines to ensure network connectivity.

--Do from both machines.

Both the databases should be in archivelog mode.

[oracle@canada gg]$ export ORACLE_SID=orcl

Oracle GoldenGate Command Interpreter for Oracle

GGSCI (canada) 1> dblogin userid ggs_admin, password ggs_admin

Successfully logged into database.

--Add supplemental logging on the source database for tables

GGSCI (canada) 2> add trandata SCOTT.*

Configure manager service on both Source and Target.

ggsci > edit param mgr

purgeoldextracts dirdat/*, usecheckpoints, minkeepdays 2

-The above parameter instructs the GoldenGate software to

ggsci > start manager

* Total statistics since 2012-03-15 21:31:54 *

* Daily statistics since 2012-03-15 21:31:54 *

* Hourly statistics since 2012-03-15 21:31:54 *

* Latest statistics since 2012-03-15 21:31:54 *