Install and Configure the Software

Install and configure Oracle Client and Oracle GoldenGate software on premise and in a compute instance in the cloud.

About Installing and Configuring the Software

Determine where to install the Oracle GoldenGate software, the Oracle GoldenGate version, and the capture mode.

Consider the following before installing Oracle GoldenGate:

  • Where to install the software?

    When installing the software on-premise, you can install Oracle GoldenGate software on the database server or on a separate machine (Oracle GoldenGate server). If you don't want to install the software on the source production system, you can install the software on a separate machine and perform remote capture of transactions from source database. The remote capture process uses SQL*NET to make a connection to the database and capture transactions remotely. The remotely captured transactions are written into local trail files on the server where the Oracle GoldenGate software is installed.

    An Oracle GoldenGate user must be on source database to capture transactions and Oracle Client software must be on the Oracle GoldenGate server to enable Oracle Client libraries to connect to the database.

  • What software version to install?

    Use the latest supported version of Oracle GoldenGate for the source database version, according to the certification matrix on My Oracle Support. Oracle GoldenGate version 12.3 is the latest supported version of the software for the source database version 11.2.0.3.

  • Which capture mode to use, integrated or classic capture mode?

    The method that you use determines how you configure the Oracle GoldenGate processes. To capture Oracle Database version 11.2.0.3, the integrated capture mode requires specific patches on the database. If the patches are not on the database, then either apply the patches or use the classic capture mode.

In this case, we're installing Oracle GoldenGate version 12.3 and Oracle Client software on a Oracle GoldenGate server and using the classic capture mode because the source database is a production database running Oracle Database version 11.2.0.3 and is not patched to the level needed to use the integrated capture mode.

Install and Configure the Software On-Premise

Identify the Oracle Client and Oracle GoldenGate software that is compatible with your source database version and install the software on your Oracle GoldenGate server.

Obtain the IP address of your Oracle GoldenGate instance in the cloud. You'll need the IP address to configure the data pump. The data pump reads the trail files generated by the extract process and transfers the changes to your Oracle GoldenGate instance in the cloud.
  1. Install the Oracle Client for the database version.

    In this case, the on premise database is Oracle Database version 11.2.0.3.

    Create the client_install.rsp file by updating the following parameters in the sample client install response file that is available with the client software:

    • UNIX_GROUP_NAME=oinstall
    • INVENTORY_LOCATION=/u01/app/oraInventory
    • ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/client_1
    • ORACLE_BASE=/u01/app/oracle
    • oracle.install.client.installType=Administrator
    • oracle.installer.autoupdates.option=SKIP_UPDATES
    $ ./runInstaller -silent -responsefile /tmp/client_install.rsp
  2. Install the Oracle GoldenGate software.
    Version 12.3.0.1.4 is the latest compatible version with Oracle Database version 11.2.0.3.

    Create the oggcore.rsp file by updating the following parameters in the sample client install response file that is available with the client software

    • INSTALL_OPTION=ORA11g
    • SOFTWARE_LOCATION=/u01/app/oracle/product/12.3.0.1/gg_2
    • START_MANAGER=true
    • MANAGER_PORT=7809
    • DATABASE_LOCATION=/u01/app/oracle/product/11.2.0.3/client_1
    • INVENTORY_LOCATION=/u01/app/oraInventory
    • UNIX_GROUP_NAME=oinstall
    ./runInstaller -silent -responsefile /tmp/oggcore.rsp
  3. Configure the parameter file for the extract command.

    Start the extract command with the begin now option, unless you have long running transactions on database. The parameter file for the extract command captures transactions for two schemas - SCH_B01 and SCH_C01, along with sequences.

    GGSCI (mlib-gghub) 3> add extract ext11g, tranlog, begin now
    GGSCI (mlib-gghub) 3> add exttrail ./dirdat/et, extract ext11g
    GGSCI (mlib-gghub) 3> view params ext11g
    EXTRACT ext11g
    EXTTRAIL ./dirdat/et 
    USERIDALIAS oci_migra 
    TRANLOGOPTIONS DBLOGREADER
    DISCARDFILE ./dirrpt/ext11g.dsc,
    APPEND MEGABYTES 50
    
    WARNLONGTRANS 2h CHECKINTERVAL 5m 
    GETUPDATEBEFORES 
    NOCOMPRESSDELETES
    NOCOMPRESSUPDATES
    
    DISCARDROLLOVER AT 01:00 ON SUNDAY 
    STATOPTIONS REPORTFETCH 
    REPORTCOUNT every 10 minutes, RATE
    REPORTROLLOVER AT 01:00 ON SUNDAY
    
    TABLE SCH_B01.* ;
    TABLE SCH_C01.* ;
    
    SEQUENCE SCH_B01.*; 
    SEQUENCE SCH_C01.* ;
  4. Configure the data pump and enter the IP address for the RMTHOST.
    The IP address for RMTHOST is the address of Oracle GoldenGate running on a compute instance in the cloud.
    GGSCI (mlib-gghub) 3> add extract pmp11g, EXTTRAILSOURCE ./dirdat/et
    
    GGSCI (mlib-gghub) 3> add rmttrail ./dirdat/rt ,extract pmp11g
    
    GGSCI (mlib-gghub) 3> view params pmp11g
    
    EXTRACT pmp11g
    RMTHOST 192.0.2.1 MGRPORT 7809
    PASSTHRU
    RMTTRAIL ./dirdat/rt
    
    TABLE SCH_B01.* ;
    TABLE SCH_C01.* ;
    
    SEQUENCE SCH_B01.* ;
    SEQUENCE SCH_C01.* ;
    
    The data pump transfers all captured changes to the target Oracle GoldenGate instance in the cloud without any filtering.
  5. Start the extract process on the source database to start capturing the transactions for change synchronization.

    Start the extract and data pump at the same time to transfer captured changes to the target Oracle GoldenGate instance in the cloud.

    GGSCI (mlib-gghub) 2> start extract EXT11G
    
    GGSCI (mlib-gghub) 2> start extract PMP11G

Install and Configure Oracle GoldenGate in the Cloud

Install the Oracle Client software version that is compatible with the database version you're upgrading to in the cloud and provision Oracle GoldenGate on the same compute instance in the cloud.

The Oracle Client and Oracle GoldenGate must be on the same compute instance to enable a connection to the database. For example, Oracle Database version 18c and Oracle GoldenGate 18c.

  1. Install the Oracle Client software for the upgrade database version on a compute instance in the cloud. For example, install Oracle Database 18c Client software.

    Create the client_install.rsp file by updating the following parameters in the sample client install response file that is available with the client software

    • UNIX_GROUP_NAME=oinstall
    • INVENTORY_LOCATION=/u01/app/oraInventory
    • ORACLE_HOME=/u01/app/oracle/product/18.3.0/client_1
    • ORACLE_BASE=/u01/app/oracle
    • oracle.install.client.installType=Administrator
    $ ./runInstaller -silent -responsefile /tmp/client_install.rsp
    
  2. Provision Oracle GoldenGate on the compute instance.
    This example uses manager port 7809.
    Create the oggcore.rsp file by updating the following parameters in the sample client install response file that is available with the client software:
    • SOFTWARE_LOCATION=/u01/app/oracle/product/18.1.0.0/gg_1
    • START_MANAGER=true
    • MANAGER_PORT=7809
    • DATABASE_LOCATION=/u01/app/oracle/product/18.3.0/client_1
    • INVENTORY_LOCATION=/u01/app/oracle
    • UNIX_GROUP_NAME=oinstall
    $ ./runInstaller -silent -reponsefile /tmp/oggcore.rsp
    
  3. Configure the manager port with the standard set of parameters.
    GGSCI (mlib-gghub) 3> view params mgr
    
    PORT 7809
    DYNAMICPORTLIST 7740-7760
    
    AUTOSTART EXTRACT *
    AUTOSTART REPLICAT *
    
    AUTORESTART ER *, RETRIES 3, 
    WAITMINUTES 10, RESETMINUTES 60
    DOWNREPORTMINUTES 15
    LAGCRITICALSECONDS 10
    LAGINFOMINUTES 0
    LAGREPORTMINUTES 15
    
    GGSCI (mlib-gghub) 4>
  4. Configure replicat.

    The replicat created is a parallel extract.

    GGSCI (mlib-gghubtgt) 2> add replica rep18c parallel, exttrail ./dirdat/rt, checkpointtable oci_migra.ggchkpt
    
    GGSCI (mlib-gghubtgt) 2> view params rep18c
    
    REPLICAT rep18c
    
    useridalias oci_migra_cld
    
    DISCARDFILE ./dirrpt/rep18c.dsc, append
    
    MAP_PARALLELISM 12
    
    APPLY_PARALLELISM 12
    
    REPORTCOUNT EVERY 30 SECONDS, RATE
    
    REPORTROLLOVER AT 01:00 ON SUNDAY
    
    DISCARDROLLOVER AT 01:00 ON SUNDAY
    
    MAP SCH_B01.*, TARGET BILDB.SCH_B01.*;
    
    MAP SCH_C01.*, TARGET BILDB.SCH_C01.*;