ORACLE GOLDEN GATE

1. DATABASE REPLICATION SO
ORACLE GOLDEN GAT
No. Category
1 HETEROGENEITY
2 RECOVERABILITY AND RESTARTABILITY
3 PERFORMANCE AND OVERHEAD
4 SINGLE PRODUCT VS. MULTIPLE
PRODUCTS
5 EASE OF TROUBLESHOOTING

2. DATABASE REPLICATION SOFTWARE
ORACLE GOLDEN GATE
Oracle Goldengate key differenciator
GoldenGate’s database and platform support is very extensive,
already proven, with real customer reference
Example of supported DB:
- Oracle
- DB2 OS/390
- DB2 UDB
- Microsoft SQL Server
- Sybase
- Ingres
- Enscribe
- SQL/MP
- SQL/MX
- Teradata
- My SQL
Example of supported OS:
- Windows 2000, 2003, XP
- Linux
- Sun Solaris
- HP-UX
- IBM AIX
- HP NonStop
- TRU64
- IBM z/OS, LUW
GoldenGate persists change data into Trail files and has check-
pointing system that allows to “trace” a transaction through our
replication flow, thus OGG persisted Trail files allow you to replay
transactions. When the target system or the network is down for any
reason, GoldenGate continues to capture new transactions to be
delivered when the target system or the network is again available
GoldenGate can handle higher load volumes and is less intrusive on the source database than similar products. For examp
customer site, we found out that other product need to have 6-7 processes running on the source database server, while O
processes
GoldenGate is only one product, which make it easier to install and
configure (take less than 1 day, compared to other similar product that
is complex to install and it takes usually several days)
GoldenGate allows users to access/search Trail files and allows fast
troubleshooting.

3. SOFTWARE
GATE
Compared to other products
With some product, although they claimed to support multiple DB, but it
use some customization to do that, for example some product need to
use triggers to capture from Sybase, and some product don’t have
capture from Teradata.
Also even though some product sometimes claim to support Oracle DB,
they don’t have any real references for real time capturing from Oracle
DB and they don’t usually fully support Oracle ASM.
Some products has problems with restarting processes because of their
queue approach for managing change data (versus our persisted Trail
files where you can replay transactions). Most of the time they need to
re-instantiate every table after a server shuts down or process is killed
due to network hiccups, disk corruption, etc.
Also most similar product doesn’t handle network environments that are
not stable and can lose transactions after a network error.
ntrusive on the source database than similar products. For example, in one of
ve 6-7 processes running on the source database server, while OGG only need 2
Some product need multiple products for data integration and replication
for HA purposes, thus requires the purchase of multiple products
Similar product usually doesn't allow following transactions during the
data movement, so it need longer time to do troubleshooting on Prod
environment