Installation Steps

GlueSync SQL to NoSQL for Oracle database

Prerequisites

Oracle Xstream | Golden Gate Middleware installations

In order to have GlueSync working on your Oracle instance you will need to have:

  • A multi tenant infrastructure consisting container and pluggable databases;

  • A paid Golden Gate license for using Xstream as data streaming mean if you are looking to use GlueSync withing Xstream APIs, otherwise it will use GDC;

  • Golden Gate replication and archive logs enabled;

  • A container level user which has Xstream admin permissions;

  • A container level user which is Xstream’s “connect user” and which has read and write access rights to tables that GlueSync should listen to.

Non-Oracle Xstream installations | GlueSync data capture (GDC)

  • No special requirements needed in order to install our trigger environment.

Preparing your Oracle database for CDC trought Xstream

If you’re Oracle database has not yet been prepared for tracking transaction logs using the Xstream APIs there are we steps to be followed in order to prepare your database before launching GlueSync.

Our Professional Services team built a tool that speeds up and streamlines the whole process, you can ask them for support using our support channels in order to gain access to the toolset and perform all the steps smoothly and safe.

Setting up Xstream

We wrote an entire chapter dedicated to those who would like to know which steps should be accomplished in order to enable Xstream in the Oracle database, you can find the documentation at this link.

Basic configuration example

This video tutorial will guide you through the basic configurations steps on setting up GlueSync for Oracle database and Couchbase, using the Xstream APIs

The SQL to NoSQL module can be customized by using a configuration file, in JSON format. The file name to use must be specified as parameter when launching the app, with the -f or --file tokens. The file should be composed by union of common configuration file (see here Installation Steps) and source/destination specific configuration:

{
  ...
  "oracle": {
    "cdbName": "oracle-contaner-db-name",
    "pdbName": "oracle-pluggable-db-name",
    "xstreamServerName": "xstream-outbound-server-name"
  }
}

Oracle specific configurations are listed under the oracle property.

  • cdbName: name of the container database of your scope;

  • pdbName: name of the pluggable database that contains the data you need to replicate;

  • xstreamServerName: the name of the Xstream outbound server used by GlueSync to detect table changes.

Looking for data modeling features or other options?

For more detailed configurations options, including the ability to perform data modeling, please have a look at the dedicated Data modeling section when sourcing from a RDBMS.