Installation steps

Gluesync SQL to NoSQL for Oracle database

Prerequisites

In the following two chapters you’ll find detailed steps to follow in order to accomplish the setup either you’re using GDC or Xstream as a source connector for Gluesync.

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

A user with grant to alter source table, create table, create sequence and create trigger statements;

To create a valid user for Gluesync on your Oracle database to run GDC you can run / adapt the following query:

CREATE USER GSUSER IDENTIFIED BY password;

ALTER USER GSUSER quota unlimited on USERS;

GRANT CREATE SESSION TO GSUSER;
GRANT CREATE TABLE TO GSUSER;
GRANT SELECT ANY TABLE TO GSUSER;
GRANT CREATE TRIGGER TO GSUSER;
GRANT CREATE ANY TRIGGER TO GSUSER;
GRANT CREATE ANY SEQUENCE TO GSUSER;

Oracle Xstream

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

Either a multi-tenant or single-tenant infrastructure consisting container and pluggable databases;
A user which has Xstream admin permissions;
A user which is Xstream’s “connect user” and which has read and write access rights to tables that Gluesync should listen to.

Preparing your Oracle database for CDC through 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 here following:

for single-tenant database setups: this link;
for multi-tenant database setups: 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",
    "connectionType": "SID | SERVICE_NAME"
  }
}

Oracle specific configurations are listed under the oracle property.

cdbName (optional): name of the container database of your scope, if running on single-tenant leave empty;
pdbName (optional): name of the pluggable database that contains the data you need to replicate, if running on single-tenant leave empty;
xstreamServerName: the name of the Xstream outbound server used by Gluesync to detect table changes;
connectionType (optional): connection type used to connect to Oracle. Available types are: SID or SERVICE_NAME. Defaults to SID.

Looking for data modelling features or other options?

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