5 Replicate Data Using Oracle GoldenGate Cloud

Oracle GoldenGate Cloud Service allows you to replicate data from various on-premise and cloud sources to various on-premise and cloud targets.

Topics:

  • Replication Using Oracle Database Cloud Service

  • Replication Using Oracle Exadata Cloud Service

  • Replication Using Oracle Big Data Cloud Service

  • Replication Using Oracle MySQL Cloud Service

  • Replication Using Oracle Autonomous Data Warehouse Cloud

Configure Oracle GoldenGate Cloud for Replication

In your Oracle GoldenGate Cloud Service instance VM, you configure Extracts, data pumps, and Replicats to enable data replication.

How do I Configure Replication?

Oracle GoldenGate Cloud Service replication requires connecting to and configuring database support for the replication node.

Configure a General Replication Process

  1. Connect to the node defined in the Manager parameter file mgr.prm located at /u01/app/oracle/gghome/dirprm

  2. Avoid using root user to run GoldenGate Cloud Service processes, otherwise some operations can fail to read using 'oracle' user.

In the following table, you can review the parameters and descriptions necessary to configure a replication process.

Parameter Description
Port:

Establishes the TCP/IP Port Number on Which Manager Listens For Requests

DynamicPortList: Specifies the ports that Manager can dynamically allocate
Autostart: Specifies the processes to be restarted after abnormal termination
LagReportHours: Sets the interval, in hours, at which Manager checks the lag for Extract and Replicat processing. Alternatively, this interval can be set in minutes.
LagInfoMinutes: Specifies the interval at which Extract and Replicat send an informational message to the event log. Alternatively, this interval can be set in seconds or hours.
LagCriticalMinutes: Specifies the interval at which Extract and Replicat send a critical message to the event log. Alternatively, this interval can be set in seconds or hours.
PurgeOldExtracts: Purges the GoldenGate Cloud Service trails that are no longer needed, based on option settings.

Note:

If you copy and paste text into parameter files, then beware of editors that try to turn a double-minus into em—dashes.

Managing Trail Files Use the PurgeOldExtracts parameter in the Manager parameter file to purge trail files when GoldenGate Cloud Service has finished processing them.

Note:

Trail files, if not managed properly, can consume a significant amount of disk space!

Configure Replication process, using the DMZ (Demilitarized Zone) Server

A DMZ server is a public-facing computer host placed on a separate or isolated network segment. The intention of this server is to provide an addition layer of network security between servers in the trusted network and servers in the public network.

Follow the four high-level steps to configuring a replication from a non-cloud database to cloud.

  1. Start the SSH Proxy Server on the DMZ Server.

  2. Configure and start the Online Change Capture Process (Extract) on the on-premise server.

  3. Configure and start the Data pump Extract on the on-premise Server (SOCKS PROXY pointing to DMZ Server).

  4. Configure and start the Online Change Delivery Process (Replicat) on the GGCS server.

1. Start the SSH Proxy Tunnel Setup on the DMZ Server

  • Start the SSH SOCKS Proxy Server on the DMZ Server

    Command Syntax:

    ssh –i <private_key file> -v –N –f –D <listening IP Address>:<listening IP port><GGCS Oracle User>@<GGCS IP Address>><socksproxy output file>2>&1

    Parameter Description
    –i

    Private Key file.

    -v

    Verbose Mode.

    –N

    Don’t execute remote command (used for port forwarding).

    –f

    Run SSH process in the background.

    –D

    Specifies to run as local dynamic application level forwarding; act as a SOCKS proxy server on a specified interface and port.

    2>&1

    Redirect Stdout and Stderr to the output filelistening.

    IP Address

    DMZ Server IP Address.

    listening IP port

    TCP/IP Port Number.

  • Verify that the SSH SOCKS Proxy server has started successfully.

    Check the socks proxy output file using the cat Unix command.

    Look for the:

    Local connections to <dmz-server:port> and

    Local forwarding listening on <ip_address> port <port #>.

    This information helps you to make sure you’re pointing to the right DMZ server address and port.

2. Configure and Start the Online Change Capture Process (Extract) on the On-premises Server

On the source server, create the online change capture (Extract) process, using the following commands:

GGCSI> add extract etpcadb, tranlog, begin now  
GGSCI> add exttrail ./dirdat/ea, extract etpcadb, megabytes 100  
GGSCI> start extract etpcadb  
GGSCI> info extract etpcadb detail

3. Configure and Start the Data pump Extract on the On-premise Server

On the source server, create the datapump (Extract) process, using the following commands:

GGCSI> add extract ptpcadb, exttrailsource ./dirdat/ea
GGSCI> add rmttrail ./dirdat/pa, extract ptpcadb, megabytes 100
GGSCI> start extract ptpcadb
GGSCI> info extract ptpcadb detail

4. Configure and Start the Online Change Delivery Process (Replicat) on the Cloud Server.

On the GoldenGate Cloud Service server, create the Change Delivery process (Replicat) using the following commands:

GGCSI> dblogin useridalias ggcsuser_alias
GGSCI> add replicat rtpcadb integrated, exttrail ./dirdat/pa
GGSCI> start replicat rtpcadb
GGSCI> info replicat rtpcadb detail

You can review this detailed steps by following the tutorial Replicate On-Premises Data to Cloud with Oracle GoldenGate Cloud Service.

How do I Configure Extracts and Data Pumps?

Oracle GoldenGate Cloud Service replication requires you to configure Extract and data pump process on source.

  1. To connect to the replication node, use one of the following options:

    • Local trail (ExtTrail) on the local system

    • Remote trail (RmtTrail) on the remote system

    Note:

    Oracle GoldenGate Cloud Service trails support the continuous extraction and replication of database changes storing these changes temporarily on cloud. A trail can reside on any platform that Oracle GoldenGate Cloud Service supports. (Oracle and MySQL databases are supported).

    You can configure one Replication node to process a trail for target databases. After all the data has been consumed, Replicat can then purge the data using the MinKeepDays parameter. As long as Replicat remains current, your temporary storage requirements for trails can be low.

  2. Format the Trail:

    •By default, trails are formatted in canonical format, allowing them to be exchanged rapidly and accurately among databases.

    Each trail file contains the following:

    • Record header area: Stored at the beginning of the file and contains information about the trail file itself.

      Trail File Information

      • Compatibility level

      • Character set (globalization function with version 11.2.1 and later)

      • Creation time

      • File sequence number

      • File size

      First and Last Record Information

      • Timestamp

      • Commit Sequence Number (CSN)

      Extract Information

      • Oracle GoldenGate Cloud Service version

      • Group name

      • Host name and Hardware type

      • Operating system type and version

      • DB type, version, and character set

    • Record data area: Contains a header area as well as a data area.

    • Checkpoints: Both Extract and Replicat maintain checkpoints into the trails. Checkpoints provide persistent processing whenever a failure occurs. Each process resumes where the last checkpoint was saved, guaranteeing that no data is lost. One Extract can write to one or many trails. One or many Replicat processes are involved in processing each trail.

    Note:

    Instead of the default canonical format, you can use alternative formats to output data.

    This feature is beneficial if database load utilities or other programs are used that require different input format.

    These alternative formats include:

    • Logical Change Records (LCRs)

    • FormatASCII

    • FormatSQL

    • FormatXML

  3. Set Up a View

    Objective Command

    To view the trail file header:

    Logdump 1> fileheader on

    To view the record header with the data:

    Logdump 2> ghdr on

    To add column information:

    Logdump 3> detail on

    To add hexadecimal and ASCII data values to the column list:

    Logdump 4> detail data

    To control how much record data is displayed:

    Logdump 5> reclen 280
  4. Keep a log of your session

    Objective Command

    To start and stop the logging of a logdump session, use the Log option:

    Logdump> Log to MySession.txt

    When enabled, logging remains in effect for all sessions of Logdump until it’s disabled with the Log Stopcommand:

    Logdump> Log Stop

Supported Scenarios

Oracle GoldenGate Cloud Service supports heterogeneous replication through the Classic Extract mechanism.

This table describes different scenarios considering that integrated extract and integrated delivery are not supported on any of the non-Oracle databases.

Source Target Extract Replicat

Oracle 12c

Oracle Database Cloud Service

Integrated Extract is supported

Integrated and Coordinated Delivery supported

MySQL

Oracle Database Cloud Service

Only Classic Extract is supported

Integrated and Coordinated Delivery supported

Note:

With Oracle 12c when not using multi-tenancy, you can still use Classic Extract, however it can’t be used when container/pluggable databases are used.

You can review detailed steps in the tutorial, Replicate On-Premises Data to Cloud with Oracle GoldenGate Cloud Service.

Replicate Data Using Oracle Exadata Cloud

You can capture data from and delivery data to Oracle Exadata Cloud Service using Oracle GoldenGate Cloud Service.

About Replication Using Oracle Exadata Cloud Service

Oracle GoldenGate Cloud Service supports real-time data replication, from on-premise Oracle DB, or Database Cloud Service to Exadata Service.

DBCS/Exadata Service Requirement / Oracle GoldenGate Cloud Service replication setup requirement

Database Cloud Service can setup instances for Oracle GoldenGate replications to Exadata Service. The setup includes the following steps:
  • Create ggadm database user.

    • Create GoldenGate admin user in the database using user name ggadm. The ggadm user's password is the same as the DBCS administration password. 

    • Grant necessary database privileges to ggadm to enable Oracle GoldenGate Cloud Service replication

  • Prepare the database for GoldenGate Cloud Service replication. 

    • Set database parameters (enable_goldengate_replicationstreams_pool_size)

    • Alter database to add supplemental logging and to enable force logging.

By default the ggadm user will be created, but users have option to overwrite the setup to specify a different user name.

A script file is included in DBCS instance to setup the Oracle GoldenGate replication. This setup occurs while users provision a new DBCS instance or update an existing DBCS instance for Exadata Service. 

You will be charged based on the number of OCPUs on the Exadta CS box.

Note:

Exadata Cloud Service opens the SQL*Net port for Oracle GoldenGate Cloud Service access (extract and replicat)

How do I Create an Oracle Database Exadata Cloud Service Instance?

Oracle GoldenGate Cloud Service supports capturing from, and delivering to Exadata Cloud Service. The replication is based on the remote capture and delivery architecture. Oracle GoldenGate Cloud Service captures from on-premises Oracle Databases and sends data to a GoldenGate Cloud Service instance. This instance connects to Database Cloud Service in Exadata Service through SQL*Net and performs remote delivery (integrated delivery).

You must create an Exadata Cloud Service database deployment that is properly configured for use as a GoldenGate Cloud Service replication target before you create a GoldenGate Cloud Service instance.

Before you can create a database deployment, you must have an active Exadata Cloud Service instance in place.

Note:

If you do not have an active service instance in place, then the Create Service wizard will not show the options required to create a deployment on Exadata Cloud Service.

Review Creating an Exadata Cloud Service Instance

You must complete the following fields when using the wizard.

  • Service level: Oracle Database Exadata Cloud Service.

  • Database release: This selection determines the version of Oracle Grid Infrastructure that is configured.

    Database releases Version of Oracle Grid Infrastructure

    Oracle Database 11g Release 2 or Oracle Database 12c Release 1

    Oracle Grid Infrastructure 12c Release 1 is installed and can only be used to support version 11.2 or version 12.1 database deployments. In this case, you cannot later use the Create Service wizard to create a version 12.2 database deployment.

    Oracle Database 12c Release 2

    Oracle Grid Infrastructure 12c Release 2 is installed and used to support all of your database deployments, including subsequent deployments that use an earlier Oracle Database release version.

    If you wish to deploy Oracle Database 12c Release 2 on a system that is already configured with Oracle Grid Infrastructure 12c Release 1, then you must manually upgrade to Oracle Grid Infrastructure 12c Release 2 and manually create the version 12.2 database deployment. For details see My Oracle Support note 2206224.1.

  • Database edition: The only valid option for use with Exadata Cloud Service is Enterprise Edition — Extreme Performance.

Configure the database deployment for use as a replication database by setting the Enable Oracle GoldenGate option on the Service Details page of the wizard.

The target database must be network accessible on the listener port by:

Once you have created and properly configured an Exadata Cloud Service database deployment for use as a replication target, you can create an Oracle GoldenGate Cloud Service instance that uses it.

When provisioning your Database, you can select any Oracle Database Exadata Cloud Service you already have.

  1. You first create the Oracle Database Exadata Cloud Service instance by launching the wizard. The wizard is invoked through the Open Service Console button on the Cloud My Services Dashboard related to the Exadata Cloud Service.

  2. Provide all the Instance Details:

    Instance Details fields Description

    Name

    The name for your service instance is no longer than 25 characters, starts with a letter, not contains spaces or other special characters and is unique within the identity domain.

    Data Center

    The data center that will host your Exadata Cloud Service instance.

    Plan

    A plan is associated with a set of attributes that apply to a service. For Exadata Cloud Service only one plan is available.

    Rack size

    Select the option that describes the number of compute nodes and Exadata Storage Servers that you have.

    Extra number of OCPUs (Cores)

    Optionally you can enter a number of additional CPU cores that you want to enable.

    Exadata System Name

    The Exadata Database Machine environment. This name is also used as the cluster name for the Oracle Grid Infrastructure installation.

    Database backups on Exadata Storage (Yes or No)

    Check this option to configure the storage to enable local database backups on Exadata storage.

    Administrator Details

    Provide information about the administrator of your Exadata Database Machine environment

  3. Create the Service instance by clicking in the Create Service Instance button.

  4. In the Overview you can also review additional information: (like the Service Start Date and the Version).

    Note:

    When you run the Oracle Database Cloud Service provisioning wizard, always select an Oracle Database Exadata Cloud Service option. This action is to have the Oracle Database software pre-installed on an Oracle Exadata machine. Using this option, Database Service instances are created on available Exadata infrastructure.

  5. When configuring your Oracle Database Cloud Service, you select Exadata System for your service instance.

  6. Finally, when configuring your Oracle GoldenGate Cloud Service instance, you select the Database Cloud Service that has Exadata.

Follow the steps through the tutorial Get Started with Oracle GoldenGate Cloud Service

To enable Oracle GoldenGate Cloud Service replication, you need to file an SR to whitelist the GGCS IP address so that GGGCS can communicate with the Exadata DB instance with the SQL*Net connection. The SR would typically include the following information:

  • IdentityDomain ID -xxxxxx of the GGCS VM

  • Source Compute instance - GGCS VM IP address

  • Exadata CS SQL*Net Port: 1521

You can find additional Exadata Cloud Service documentation at: Enabling Access to a Compute Node Port

Note:

  • Oracle GoldenGate Cloud Service doesn't support Oracle database 12.2 capture yet.

  • With Exadata CS X6, you can complete the whitelist operation using the UI interface.

Replicate Data to Oracle Autonomous Data Warehouse Cloud

You can replicate data to Oracle Autonomous Data Warehouse Cloud using Oracle GoldenGate Cloud Service.

About Replicating Data to Oracle Autonomous Data Warehouse Cloud

You can configure an Oracle Autonomous Data Warehouse Cloud instance as a target database for Oracle GoldenGate Cloud Service.

Autonomous Data Warehouse Cloud is a fully-managed data warehouse designed to support all standard SQL and business intelligence tools and deliver scalable analytic query performance. Autonomous Data Warehouse Cloud provides all of the performance of the market-leading Oracle Database in a fully-managed environment that is tuned and optimized for data warehouse workloads. Some data types, SQL commands, and database features are not available in Autonomous Data Warehouse Cloud.

To setup Oracle Autonomous Data Warehouse Cloud as a target database, you must use Oracle GoldenGate 12.3 in an Oracle GoldenGate Cloud Service instance that includes Oracle GoldenGate 12c (12.3.0.1.2). The source for the replication to Oracle Autonomous Data Warehouse Cloud can be:
  • Oracle GoldenGate On Premises releases 12.3.0.1.2 and later are certified with Oracle Autonomous Data Warehouse Cloud for remote delivery using the non-integrated Replicats only. However, any supported release of Oracle GoldenGate for any supported database and operating system combination that can send trail data to Oracle GoldenGate for Oracle Database release 12.3.0.1.2 and later, can be used as source systems.

  • Oracle Database Cloud Service on Oracle Cloud and Oracle Cloud at Customer

  • Oracle Exadata Cloud Service on Oracle Cloud and Oracle Cloud at Customer

Note:

You cannot setup Oracle Autonomous Data Warehouse Cloud database as a source database for Oracle GoldenGate Cloud Service.

Use Case for Replicating to Oracle Autonomous Data Warehouse Cloud with Oracle GoldenGate Cloud Service

Use Oracle GoldenGate Cloud Service to replicate data to Oracle Autonomous Data Warehouse Cloud for:
  • Real-time data warehousing: Replicate on-premises data to Oracle Autonomous Data Warehouse Cloud to set up a staging environment for downstream ETL or real-time data warehousing.

  • Operational reporting: Replicate real-time data from multiple on-premises data sources and deliver to Oracle Autonomous Data Warehouse Cloud for creating reports.

Understanding What is Supported While Replicating to Autonomous Data Warehouse Cloud

Review the supported data types and limitations before replicating data to Autonomous Data Warehouse Cloud.

Understanding Limitations

For a complete list of database initialization parameter restrictions, database features restrictions, SQL commands restrictions, and data types restrictions, see Autonomous Data Warehouse Cloud for Experienced Oracle Database Users.

The Oracle Database data types that are supported by Oracle GoldenGate can be replicated to Autonomous Data Warehouse Cloud. For a complete list of supported data types, see Details of Support for Oracle Data Types in Using Oracle GoldenGate for Oracle Database. The support limitations mentioned for replicating data to Oracle Database using Oracle GoldenGate apply to replicating data to Autonomous Data Warehouse Cloud too. There are additional limitations when replicating data into Autonomous Data Warehouse Cloud as listed in the following section.

Oracle GoldenGate Replicat Limitations for Autonomous Data Warehouse Cloud

Currently, only non-integrated Replicats are supported with Autonomous Data Warehouse Cloud. Integrated Replicats are not supported.

For the best compression ratio in your target tables in Autonomous Data Warehouse Cloud, Oracle recommends replicating changes (including updates and deletes) from your source systems as inserts into staging tables and using in-database batch operations to merge the changes into your target tables.

Data Type Limitations for DDL and DML Replications

The following data types are not supported while replicating data to Autonomous Data Warehouse Cloud:

  • LONG

  • LONG RAW

  • XMLTYPE STORE AS OBJECT RELATIONAL

  • XMLTYPE STORE AS BINARY

  • BFILE

  • MEDIA

  • SPATIAL

The following data types are supported only when the trail file is generated through an integrated Extract.

  • ABSTRACT/USER DEFINED TYPE

  • UROWID

  • ANYDATA

How Do I Replicate Data to Oracle Autonomous Data Warehouse Cloud?

You need to configure non-integrated Replicats to deliver data to Oracle Autonomous Data Warehouse Cloud.

Prerequisites:

You should have the following details available with you:
  • Oracle GoldenGate Cloud Service instance details.

  • Oracle Autonomous Data Warehouse Cloud database account details.

  • Your source database with Oracle GoldenGate Extract processes configured.

Replication Procedure Overview

To deliver data to Oracle Autonomous Data Warehouse Cloud using Oracle GoldenGate Cloud Service, perform the following tasks:

  • Configure Oracle Autonomous Data Warehouse Cloud for Replication.
    • Unlock the pre-created Oracle GoldenGate database user ggadmin in Oracle Autonomous Data Warehouse Cloud.

    • Create new application user user_target.

    • Create target database tables for replication.

  • Obtain Oracle Autonomous Data Warehouse Cloud client credentials file.

  • Configure Oracle GoldenGate Cloud Service for replication.
    • Transfer the client credentials file that you downloaded from Oracle Autonomous Data Warehouse Cloud.

    • Configure the sqlnet.ora file.

    • Configure the tnsnames.ora file.

    • Create a useridalias for the ggadmin Oracle Autonomous Data Warehouse Cloud user.

  • Configure Oracle GoldenGate Manager and non-integrated Replicats to deliver data to Oracle Autonomous Data Warehouse Cloud.

Configure Oracle Autonomous Data Warehouse Cloud for Replication

In the Oracle Autonomous Data Warehouse Cloud database, complete the following tasks:

  1. Oracle Autonomous Data Warehouse Cloud has a pre-existing database user created for Oracle GoldenGate called ggadmin. The ggadmin user has been granted the right set of privileges for Oracle GoldenGate Replicat to work. By default, this user is locked. To unlock the ggadmin user, connect to your Oracle Autonomous Data Warehouse Cloud database as the ADMIN user using any SQL client tool. See About Connecting to Autonomous Data Warehouse Cloud.

  2. Run the alter user command to unlock the ggadmin user and set the password for it. See Creating Users with Autonomous Data Warehouse Cloud.
    alter user ggadmin identified by password account unlock;
  3. Create the new application user user_target.
    create user user_target identified by password;
    grant create session, resource, create view, create table to user_target;
  4. Connect to Oracle Autonomous Data Warehouse Cloud database as the user_target user and create schema and target tables for which DDL replication is not enabled.

Obtain Oracle Autonomous Data Warehouse Cloud Client Credentials File

To establish connection to your Oracle Autonomous Data Warehouse Cloud database, you download the client credentials file from the Oracle Autonomous Data Warehouse Cloud service console.

Note:

If you do not have administrator access to Oracle Autonomous Data Warehouse Cloud, you should ask your service administrator to download and provide the client credentials file to you.
  1. Log into your Oracle Autonomous Data Warehouse Cloud account.

  2. From the Instance page, click the menu option for the Oracle Autonomous Data Warehouse Cloud instance and select Service Console.

  3. Log into the service console using the admin username and its associated password.

  4. In the service console, click the Administration tab.

  5. Click Download Client Credentials.

  6. Enter a password to secure your client credentials file and click Download.

  7. Save the client credentials file to your local system.

The client credentials file contains the following files:
  • cwallet.sso

  • ewallet.p12

  • keystore.jks

  • ojdbc.properties

  • sqlnet.ora

  • tnsnames.ora

  • truststore.jks

You refer to the sqlnet.ora and tnsnames.ora files while configuring Oracle GoldenGate Cloud Service to work with Oracle Autonomous Data Warehouse Cloud.

Configure Oracle GoldenGate Cloud Service for Replication

In the Oracle GoldenGate Cloud Service instance, complete the following tasks:

  1. Connect to your Oracle GoldenGate Cloud Service instance.

    ssh -i private_key opc@IP_address_of_your_instance
  2. Once you are connected to your Oracle GoldenGate Cloud Service instance, change user to oracle.

    sudo su - oracle
  3. Transfer the client credentials file that you downloaded from Oracle Autonomous Data Warehouse Cloud to your Oracle GoldenGate Cloud Service instance.

  4. In the Oracle GoldenGate Cloud Service instance, unzip the client credentials file into a new directory /u02/data/adwc_credentials. This will be your key directory.

  5. To configure the connection details, open your tnsnames.ora file from the oracle client location in the Oracle GoldenGate Cloud Service instance.

    Note:

    If your Oracle GoldenGate Cloud Service is associated with Oracle Database Cloud Service, the tnsnames.ora file will exist. Otherwise, you need to create the tnsnames.ora file and the network/admin directories under /u02/data/oci.
    cd /u02/data/oci/network/admin
    ls
    tnsnames.ora
  6. Edit the tnsnames.ora file in the Oracle GoldenGate Cloud Service instance to include the connection details that is available in the tnsnames.ora file in your key directory (the directory where you unzipped the client credentials file downloaded from Oracle Autonomous Data Warehouse Cloud).

    Sample Connection String
    connection_name = (description= (address=(protocol=tcps)(port=TNS Service port)(host=ADWC_IP))
    (connect_data=(service_name=ADWC_Database_Name (security=(ssl_server_cert_dn="ADWC SSL certification")))

    Note:

    The tnsnames.ora file provided with the client credentials file contains three database service names identifiable as:
    ADWC_Database_Name_low
    ADWC_Database_Name_medium
    ADWC_Database_Name_high
    For Oracle GoldenGate replication, use ADWC_Database_Name_low. See Predefined Database Service Names for Autonomous Data Warehouse Cloud
  7. To configure the wallet, create a sqlnet.ora file in the oracle client location in the Oracle GoldenGate Cloud Service instance.
    cd /u02/data/oci/network/admin
    ls
    sqlnet.ora tnsnames.ora
  8. Edit this sqlnet.ora file to include your key directory.
    WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="/u02/data/adwc_credentials"))) 
    SSL_SERVER_DN_MATCH=yes
  9. To create a useridalias, start GGSCI.
    cd $GGHOME
    ./ggsci
  10. Create the Oracle GoldenGate wallet and add the useridalias to the credential store.
    GGSCI add credentialstore
    GGSCI Alter credentialstore ADD USER ggadmin@connection_name PASSWORD password alias ggadmin_alias 
    GGSCI DBLOGIN USERIDALIAS ggadmin_alias

Configure Oracle GoldenGate Manager and Classic Replicat to deliver to Oracle Autonomous Data Warehouse Cloud

  1. If you are not already connected to your Oracle GoldenGate Cloud Service instance, connect using the ssh command.

    ssh -i private_key opc@IP_address_of_your_host
  2. Once you are connected to your Oracle GoldenGate Cloud Service instance, change user to oracle.

    sudo su - oracle
  3. From your Oracle GoldenGate Cloud Service instance, test the connection to your Oracle Autonomous Data Warehouse Cloud instance using sqlplus.

    sqlplus ggadmin/password@connection_name 
  4. After you are connected to the Oracle Autonomous Data Warehouse Cloud database in sqlplus from your Oracle GoldenGate Cloud Service instance, ensure that the target replication tables are available.

  5. Connect to GGSCI.
    cd $GGHOME
    ./ggsci
  6. To configure, Oracle GoldenGate manager, open the mgr parameter file to edit it.
    GGSCI edit param mgr
  7. Ensure that the manager parameter file has the following information:
    PORT port_number
    Dynamicportlist port_1-port_n
    ACCESSRULE, PROG COLLECTOR, IPADDR IP_Address_GGCS_host, ALLOW
    PURGEOLDEXTRACTS path_to_the_trail_file, USECHECKPOINTS, MINKEEPHOURS n hours MINKEEPFILES n files
    AUTORESTART ER *, RETRIES n, WAITMINUTES n, RESETMINUTES n
  8. Add GGSCHEMA ggadmin to your GLOBALS file.

  9. Stop and start the manager and confirm that it started.
    GGSCI stop mgr
    GGSCI start mgr
    GGSCI info mgr
  10. Configure your Replicat file. A sample Replicat file is listed here. For a complete list of Replicat file parameters, see Oracle GoldenGate Parameters in Oracle GoldenGate Reference.

    replicat rep_name 
    useridalias ggadmin_alias 
    discardfile ./dirrpt/rep_name.dsc,purge 
    REPORTCOUNT EVERY 5000 RECORDS
    map SourceSchema.SourceTable, target TargetSchema.TargetTable [filter clauses];
  11. In GGSCI, login to the database using useridalias and add the Replicat.

    add replicat rep_name,exttrail ./dirdat/trail_file_name

    Note:

    Oracle Autonomous Data Warehouse Cloud times out and disconnects Replicat if it is idle for more than 60 minutes. When Replicat tries to apply changes (when it gets new changes) after being idle, it encounters a database error and abends. You must restart the Replicat unless you have configured AUTORESTART.

You have successfully configured a classic Replicat. You can now start the replicat process and replicate data to Oracle Autonomous Data Warehouse Cloud.