For how many years have you been working
with physical servers? Software Defined Servers can improve performance and
security while lowering complexity and cost. With Software Defined Servers
you define servers with an optimum configuration to your environment rather
than being memory starved and cpu over-provisioned. Find out how you can
improve your computing environment with
TidalScale. your friends.
The concept behind this page is to combine documentation for GoldenGate installations for Oracle 126.96.36.199
through 188.8.131.52 databases with information about command syntax and examples.
GoldenGate configuration is primarily a matter of putting the correct parameters into .prm files in the correct order and the number of parameters is far too voluminous to cover here at this time.
In the future this will stabilize on just Oracle Database 18c and GoldenGate 12.3 or above.
Pre-Installation Environment Prep
GG software owner's environment
Unzipped install files
Post installation GGHOME directory files
Installation Step 1 of 6
Installation Step 2 of 6
Even when the GGHOME environment variable is set the software location ignores it and must be fixed
Installation Step 3 of 6
Review to make sure things are configured properly. Then save the response file to document your installation choices.
Installation Step 4 of 6
A good practice is to save the response files into the directory /home/oracle and then to place a copy into your change control
Installation Step 5 of 6
Installation Step 6 of 6
Unzipped install files
SQL> conn / as sysdba
ALTER DATABASE FORCE LOGGING;
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
ALTER SYSTEM SET enable_goldengate_replication=TRUE
COMMENT='Enabled GG Replication 15-MAR-2014 DAM'
GGSCI> info PONLINE4, showch
GGSCI (dc2sfdb02) 2> info all
Program Status Group Lag at Chkpt Time Since Chkpt
Create a new pump process where the extract process already exists
ADD EXTRACT <pump_process_name>, exttrailsource <path>, begin now
GGSCI> add extract uwpumpdb, exttrailsource /u01/app/oracle/product/gg/dirdat/a1, begin now
-- edit the parameter file for the pump process to have the following contents:
userid gg, password gg
rmthost ggtargethost, mgrport 7809
-- execute the following ggsci commands on the source server:
GGSCI> add rmttrail /u01/app/oracle/product/gg/dirdat/a1, extract uwpumpdb
GGSCI> start uwpumpdb
/* After executing the above, start the manager process on the target server (ggtargethost) and the pump process will started
propagating data to the rmttrail files */