Oracle snapshot

A high-level look at Stitch's Oracle integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release Status

Released

Supported By

Stitch

Stitch Plan

Enterprise

Supported Versions

n/a

Singer GitHub Repository

Oracle Repository

CONNECTION METHODS
SSH Connections

Supported

SSL Connections

Supported

REPLICATION SETTINGS
Anchor Scheduling

Supported

Table-level Reset

Supported

Configurable Replication Methods

Supported

REPLICATION METHODS
Log-based Replication

Supported

Key-based Replication

Unsupported

Full Table Replication

Supported

DATA SELECTION
Table Selection

Supported

Column Selection

Supported

View Replication

Unsupported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Oracle

Oracle setup requirements

To set up Oracle in Stitch, you need:

  • An Enterprise Stitch plan. Oracle integrations can be added on as part of an Enterprise plan. Reach out to Stitch support for more info.
  • Privileges in the Oracle database that allow you to:

    • Access the V$DATABASE and V_$THREAD performance views. These are required to verify setting configuration while setting up your Oracle database and to retrieve the database’s Oracle System ID. Refer to Oracle’s documentation for more info on performance views.

    • Create users and grant privileges. The CREATE USER and GRANT privileges are required to create a database user for Stitch and grant the necessary privileges to the user.

    • GRANT access to the objects you want to replicate. This is necessary to grant the privileges necessary for selecting data to the Stitch database user. Refer to Oracle’s documentation for more info.

    • Use System administrator (SYSDBA) privileges, if replicating data incrementally. This is necessary to complete steps required to use Oracle LogMiner, which enables the use of Log-based Incremental Replication. Refer to Oracle’s documentation for more info.

  • An existing Recovery Manager (RMAN) configuration, if replicating data incrementally. RMAN is used to manage database backups and archive logs and is required to use Log-based Incremental Replication. Setting up RMAN is outside the scope of this tutorial. If you need help setting up and using RMAN, refer to Oracle’s documentation or loop in a member of your technical team.


Step 1: Whitelist Stitch's IP addresses

For the connection to be successful, you’ll need to configure your firewall to allow access from our IP addresses. Whitelist the following IPs before continuing onto the next step:

  • 52.23.137.21/32

  • 52.204.223.208/32

  • 52.204.228.32/32

  • 52.204.230.227/32


Step 2: Retrieve the database's Oracle System ID

An Oracle System ID (SID) is used to uniquely identify a specific database in your system. When you connect an Oracle database to Stitch, you’ll enter the SID of the database you want Stitch to extract data from into the Integration Settings page.

To retrieve your database’s SID, log into your database as a user with access to the SYS.V_$THREAD performance view and run the following:

SELECT INSTANCE FROM SYS.V_$THREAD

The value returned by the query will be the database’s SID. Keep this handy - you’ll need it to complete the setup.


Step 3: Enable Log-based Incremental Replication with LogMiner

Log-based Incremental Replication is the most efficient way to replicate Oracle data. Stitch uses Oracle’s LogMiner package to query Oracle’s archive logs and retrieve all inserts, updates, and deletes to your database.

Step 3.1: Verify the database's current archiving mode

To check the database’s current mode, run:

SELECT LOG_MODE FROM V$DATABASE

If the result is ARCHIVELOG, archiving is enabled and no further action is required. Skip to Step 3.3 to configure RMAN backups.

If the result is NOARCHIVELOG, then you’ll need to enable archiving. Move onto to Step 3.2 for instructions.

Step 3.2: Enable ARCHIVELOG mode

If the result to the query in Step 3.1 is NOARCHIVELOG, then you’ll need to enable ARCHIVELOG mode. Skip to Step 3.3 if the result was ARCHIVELOG.

  1. Shut down the database instance. The database and any associated instances must be shut down before the datbase’s archiving mode can be changed.

    SHUTDOWN IMMEDIATE
    
  2. If desired, back up the database. Oracle recommends backing up databases before any major changes. Refer to Oracle’s documentation for more info.

  3. Start a new instance and mount (but not open) the database:

    STARTUP MOUNT
    
  4. Change the database’s archiving mode and re-open it:

    ALTER DATABASE ARCHIVELOG
    ALTER DATABASE OPEN
    

Step 3.3: Configure RMAN backups

Next, you’ll configure Recovery Manager (RMAN) backups. This setting defines how long the database will retain backups and archive logs, which is what Stitch will read from to perform Log-based Incremental Replication. Refer to Oracle’s documentation for more info about RMAN.

Stitch recommends a retention period of at least 3 days, but strongly recommends 7. To specify the RMAN retention policy, run the following:

RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

Step 3.4: Enable supplemental logging

In this step, you’ll enable supplemental logging for the database. This ensures that columns are logged in redo log files, which is required by Oracle to use LogMiner. Refer to Oracle’s documentation for more info about supplemental logging.

Stitch supports supplemental logging at the database and table level. Note: You do not need to enable both. Select the level you want to use for supplemental logging (database or table) and follow the steps below:

  • At the database level, this means that any time a change is made to a table in the database, it will be logged in the redo log files.

    To enable supplemental logging at the database level, run:

    ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS
    
  • At the table level, this means that only changes made to the specified table will be logged in the redo log files. By only applying logging to the tables you want to replicate through Stitch, this may reduce the overall disk space used by redo log files.

    To enable supplemental logging at the table level, run the following for every table you want to replicate through Stitch:

    ALTER TABLE <SCHEMA_NAME>.<TABLE_NAME> ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS
    

Next, verify that supplemental logging was successfully enabled by running the following query:

SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE

If the returned value is YES or IMPLICIT, supplemental logging is enabled.


Step 4: Create a Stitch Oracle database user

Next, you’ll create a dedicated database user for Stitch. This will ensure Stitch is visible in any logs or audits and allow you to maintain your privilege hierarchy.

  1. If you aren’t already, log into your database as a user with CREATE USER and GRANT privileges.
  2. Run the following command to create the Stitch database user, replacing <password> with a secure password:

    CREATE USER STITCH IDENTIFIED BY <password>
    
  3. Grant the Stitch user the CREATE SESSION privilege, which will allow Stitch to connect to the database:

    GRANT CREATE SESSION TO STITCH
    
  4. Grant the Stitch user SELECT privileges. This can be done one of two ways: Granting access to all tables, or only granting access to specific tables you want to replicate.

    • To grant Stitch access to all tables, run:

       GRANT SELECT ANY TABLE TO STITCH
      
    • To grant Stitch access to specific tables, run the following command for each table you want to replicate. Replace <SCHEMA> and <TABLE> with the name of the schema and table, respectively:

       GRANT SELECT ON <SCHEMA>.<TABLE> to STITCH
      

See the Privileges list tab for an explanation of why these permissions are required by Stitch.

In the table below are the database user privileges Stitch requires to connect to and replicate data from a Oracle database.

Privilege name Reason for requirement
CREATE SESSION

Required to log into the Oracle database.

SELECT

Required to select data from the tables and columns you want to replicate.

  • SELECT ANY TABLE grants SELECT privileges to any table in the connected database.
  • SELECT ON <SCHEMA.TABLE> grants SELECT privileges only to the specified table.
EXECUTE_CATALOG_ROLE

Required to use Log-based Incremental Replication. Required by Oracle to access objects in the SYS schema.

EXECUTE ON DBMS_LOGMNR

Required to use Log-based Incremental Replication. Allows the Stitch user to execute the DBMS_LOGMNR package for LogMiner.

EXECUTE ON DBMS_LOGMNR_D

Required to use Log-based Incremental Replication. Allows the Stitch user to execute the DBMS_LOGMNR package for LogMiner.

SELECT ON SYS.V_$DATABASE

Required to validate the database’s configuration settings (archiving mode, supplemental logging, etc).

SELECT ANY TRANSACTION

Required to use Log-based Incremental Replication. Requied by Oracle to query the SYS.V$LOGMNR_CONTENTS view.

SELECT ANY DICTIONARY

Required to select from system data dictionary objects.

SELECT ON SYS.V_$ARCHIVED_LOG

Required to use Log-based Incremental Replication. Required to locate the start and end of extracted dictionaries in archived redo log files via the SYS.V_$ARCHIVED_LOG view.

SELECT ON SYS.V_$LOGMNR_CONTENTS

Required to use Log-based Incremental Replication. Required to identify the redo log files to mine (read) via the SYS.V_$LOGMNR_CONTENTS view.

LOGMINING

Required to use Log-based Incremental Replication if using Oracle version 12. In version 12 of Oracle, this privilege is required to use the START_LOGMNR procedure in LogMiner.


Step 5: Connect Stitch

In this step, you’ll complete the setup by entering the database’s connection details and defining replication settings in Stitch.

Step 5.1: Define the database connection details

  1. Sign into your Stitch account, if you haven’t already.
  2. On the Stitch Dashboard page, click the Add Integration button.
  3. Click the Oracle icon.
  4. Fill in the fields as follows:

    • Integration Name: Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your data warehouse.

      For example, the name “Stitch Oracle” would create a schema called stitch_oracle in the data warehouse. Note: The schema name cannot be changed after the integration is saved.

    • Host (Endpoint): Enter the host address (endpoint) used by the Oracle instance.

      In general, this will be 127.0.0.1 (localhost), but could also be some other network address (ex: 192.68.0.1) or your server’s public IP address. Note: This must be the actual address - entering localhost into this field will cause connection issues.

    • Port: Enter the port used by the Oracle instance. The default is 1521.

    • Username: Enter the Stitch Oracle database user’s username.

    • Password: Enter the password for the Stitch database user.

    • Oracle System ID (SID): Enter the Oracle System ID (SID) of the database you retrieved in Step 2.

Step 5.2: Define the SSL connection details

Click the Connect using SSL checkbox if you’re using an SSL connection. Note: The database must support and allow SSL connections for this setting to work correctly.

Step 5.3: Define default replication method

In the Default Replication Method section, you’ll select a default Replication Method for the integration.

The method you select will be the default Replication Method for any table you set to replicate. You can change the Replication Method for individual tables in the Table Settings page for that table.

Select a default Replication Method:

  • Log-based Incremental Replication - Stitch will use Log-based Incremental Replication. Refer to the Log-based Incremental documentation for more info, examples, and limitations for this method. Note: This method can only be used if you completed the steps for setting up LogMiner.

  • Full Table Replication - Stitch will use Full Table Replication. Refer to the Full Table documentation for more info, examples, and limitations for this method.

Step 5.4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.


Step 6: Select data to replicate

The last step is to select select the tables and columns you want to replicate.

When you track a table, Stitch will use the default Replication Method selected in the Integration Settings page. You can choose a different Replication Method for individual tables during this process.

You can select tables and columns by:

  1. In the Integration Details page, click the Tables to Replicate tab.
  2. Locate a table you want to replicate.
  3. Click the checkbox next to the object’s name. A green checkmark means the object is set to replicate.
  4. If there are child objects, they’ll automatically display and you’ll be prompted to select some.
  5. After you set a table to replicate, the Settings page will display. Note: When you track a table, by default all columns will also be tracked.

  6. In the Settings page, define the table’s Replication Method or skip this step if you want to use the integration’s default method.

  7. Repeat this process for every table you want to replicate.

  8. Click the Finalize Your Selections button to save your data selections.

Initial and historical replication jobs

After you finish setting up Oracle, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Oracle Replication

Overview of Log-based Incremental Replication using LogMiner

Stitch uses Oracle’s LogMiner package to replicate data incrementally. This means that when Log-based Incremental is selected as the Replication Method for a table, Stitch will only replicate new or updated data for the table during each replication job.

To identify new and updated data, Stitch uses Oracle’s Approximate Commit System Change Numbers, or SCNs, as Replication Keys. When reading from the database’s logs, records with an SCN value greater than the maximum SCN from the previous job will be replicated.

Refer to the Log-based Incremental Replication documentation for a more detailed explanation, examples, and the limitations associated with this replication method.

Note: Stitch currently supports Log-based Incremental and Full Table Replication for Oracle integrations. Other replication methods are not currently supported.

Data typing and LogMiner (Log-based Incremental Replication)

Oracle’s LogMiner packages supports the data types listed in the table below. Refer to Oracle’s documentation for more info.

Only columns with the data types listed below are able to be selected and replicated through Stitch. Columns with data types not in this list will show as UNSUPPORTED in Stitch. For reference, you can view the code for data typing in Stitch’s Oracle integrations in the Singer Oracle GitHub repository.

Oracle data type Stitch data type mapping
BINARY_FLOAT FLOAT
BINARY_DOUBLE FLOAT
CHAR STRING
NCHAR STRING
NVARCHAR2 STRING
VARCHAR STRING
VARCHAR2 STRING
DATE DATE-TIME
TIMESTAMP DATE-TIME
TIMESTAMP WITH TIME ZONE DATE-TIME
TIMESTAMP WITH LOCAL TIME ZONE DATE-TIME
INTEGER INTEGER
SMALLINT INTEGER
NUMBER (*,0) INTEGER
NUMBER (*,*) DECIMAL


Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.