# Oracle (v1)

Information note

**Oracle integrations are an upgraded feature**

Oracle integrations are an upgraded feature that’s available for customers on an Advanced or Premium plan. It is not available by default during the free trial, but it can be enabled if needed.

For more info about Stitch Advanced, contact the [Stitch Sales team](https://www.stitchdata.com/contact/).

Information note **Oracle extraction is supported by Stitch**   
This integration is powered by [Singer's](https://www.singer.io/) Oracle tap and certified by Stitch. [Check out and contribute to the repo on GitHub](https://github.com/singer-io/tap-oracle).  
  
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).

## Oracle feature snapshot

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

| **STITCH** |  |  |  |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on August 1, 2018 | **Supported by**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**<br><br>the Info icon<br><br>The type of Stitch plan required to use the integration. | Advanced | **Supported versions**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | 8.0 - 18c |
| **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**<br><br>the Info icon<br><br>Indicates if the integration is available as a source in Stitch Connect. | the Success icon<br><br>This version of the integration is available via the API.<br><br><br>Available | **Singer GitHub repository** | [singer-io/tap-oracle](https://github.com/singer-io/tap-oracle) |
| **CONNECTION METHODS** |  |  |  |
| **SSH connections**<br><br>the Info icon<br><br>Indicates if SSH tunnels are supported for connecting this database to Stitch. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **SSL connections**<br><br>the Info icon<br><br>Indicates if SSL connections are supported for connecting this database to Stitch. | the Remove icon<br><br>This feature is not supported for this version of the integration.<br><br><br>Unsupported |
| **REPLICATION SETTINGS** |  |  |  |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Table-level reset**<br><br>the Info icon<br><br>Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**<br><br>the Info icon<br><br>Indicates if Replication Methods can be defined by you for tables in the integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **REPLICATION METHODS** |  |  |  |
| **[Log-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental)**<br><br>the Info icon<br><br>Log-based Incremental Replication is a replication method in which Stitch identifies modifications to records - including inserts, updates, and deletes - using a database's binary log files. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Key-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental)**<br><br>the Info icon<br><br>Key-based Incremental Replication is a replication method in which Stitch identifies new and updated data using a column called a Replication Key. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[Full Table Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table)**<br><br>the Info icon<br><br>Full Table Replication is a replication method in which all rows in a table - including new, updated, and existing - are replicated during every replication job. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |  |  |
| **DATA SELECTION** |  |  |  |
| **Table selection**<br><br>the Info icon<br><br>The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Column selection**<br><br>the Info icon<br><br>The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[View replication](https://help.qlik.com/en-US/stitch/replication/replicating-database-views)**<br><br>the Info icon<br><br>Indicates if Stitch supports replicating views from this database integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Select all**<br><br>the Info icon<br><br>Indicates if the integration supports selecting all available tables and columns. | the Warning 2 icon<br><br>Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.<br><br><br>Supported, with prerequisites |
| **TRANSPARENCY** |  |  |  |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**<br><br>the Info icon<br><br>Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**<br><br>the Info icon<br><br>Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |

## Connecting Oracle

### Oracle setup requirements

To set up Oracle in Stitch, you need:

* **A Stitch Advanced plan.**

* **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](https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1001.htm#i1398692) for more info on performance views.

  * **Create users and grant privileges.** The [`CREATE USER`](https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8003.htm#i2065278) and [`GRANT`](https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_9013.htm#sthref9170) 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](https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_9013.htm#sthref9170) for more info.

* **If using Log-based Incremental Replication, you need**:

  * **A database using Oracle 8.0 through 18c**. Versions earlier than 8.0 and later than 18c don’t include LogMiner functionality, which is required for Log-based Incremental Replication.

  * **System administrator (`SYSDBA`) privileges.** This is necessary to complete steps required to use Oracle LogMiner. Refer to [Oracle’s documentation](https://docs.oracle.com/database/121/ADMQS/GUID-2033E766-8FE6-4FBA-97E0-2607B083FA2C.htm#ADMQS12004) for more info.

  * **An existing Recovery Manager (RMAN) configuration.** 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](https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89346) or loop in a member of your technical team.

### Step 1: Configure database connection settings

In this step, you’ll configure the database server to allow traffic from Stitch to access it. There are two ways to connect your database:

* **A direct connection** will work if your database is publicly accessible.
* **An SSH tunnel** is required if your database isn’t publicly accessible. This method uses a publicly accessible instance, or an SSH server, to act as an intermediary between Stitch and your database. The SSH server will forward traffic from Stitch through an encrypted tunnel to the private database.

Click the option you’re using below and follow the instructions.

I'm using an SSH tunnel to connect.

1. Follow the steps in the [Setting up an SSH Tunnel for a database connection guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-database-connection) to set up an SSH tunnel for Oracle.
2. Complete the steps in this guide after the SSH setup is complete.

#### I'm using a direct connection.

For the connection to be successful, you’ll need to configure your firewall to allow access from our IP addresses.

The IP addresses you’ll whitelist depend on the [**Data pipeline region** your account is in](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions).

1. [Sign into your Stitch account](https://app.stitchdata.com/), if you haven’t already.

2. Click **User menu (your icon) &gt; Edit User Settings** and locate the **Data pipeline region** section to verify your account’s region.

3. Locate the list of IP addresses for your region:

   * [North America region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#north-america-ip-addresses)

   * [Europe region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#europe-ip-addresses)

4. Whitelist the appropriate IP addresses.

### Step 2: Enable Log-based Incremental Replication with LogMiner

Information note **Note**: Skip this step if you’re not planning to use Log-based Incremental Replication. [Click to skip ahead](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#db-user).

Information note

**Note: Log-based Incremental Replication requirements and limitations**

Before configuring Log-based Incremental Replication, note the following:

* **Not all database versions are supported.** Only Oracle databases using [a version from 8.0 through 18c](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#setup-requirements) support [LogMiner](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm), which is required to use Log-based Incremental Replication in Stitch.
* **Some data types may not be supported**. Refer to the [Data types section](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#data-types) for more info.

Log-based Incremental Replication is the most efficient way to replicate Oracle data. Stitch uses [Oracle’s LogMiner package](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm) to query Oracle’s archive logs and retrieve all inserts, updates, and deletes to your database.

* [Step 2.1: Verify the database’s current archiving mode](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#verify-current-archiving-mode)

* [Step 2.2: Enable ARCHIVELOG mode](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#enable-archivelog-mode)

* [Step 2.3: Configure RMAN backups](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#configure-rman-backups)

* [Step 2.4: Enable supplemental logging](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#enable-supplemental-logging)

#### Step 2.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](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#configure-rman-backups).

If the result is `NOARCHIVELOG`, then you’ll need to enable archiving. Move onto to [Step 3.2](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#enable-archivelog-mode) for instructions.

#### Step 2.2: Enable ARCHIVELOG mode

Information note

**Note: This step requires:**

1. System administrator (`SYSDBA`) privileges in Oracle
2. Restarting the database. Stitch recommends performing this step during off-peak hours to minimize disruptions.

If the result to the query in [Step 3.1](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#verify-current-archiving-mode) is `NOARCHIVELOG`, then you’ll need to enable `ARCHIVELOG` mode. **Skip to [Step 3.3](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#configure-rman-backups) if the result was `ARCHIVELOG`.**

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

   ```

   ```

   ```
   SHUTDOWN IMMEDIATE
   ```

2. **If desired, back up the database.** [Oracle recommends backing up databases before any major changes](https://docs.oracle.com/database/121/ADMIN/archredo.htm#ADMIN-GUID-C12EA833-4717-430A-8919-5AEA747087B9). Refer to [Oracle’s documentation](https://docs.oracle.com/database/121/BRADV/rcmcncpt.htm#BRADV002) 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 2.3: Configure RMAN backups

Information note

**Note: This step requires:**

1. System administrator (`SYSDBA`) privileges in Oracle
2. An existing Recovery Manager (RMAN) configuration. Setting up RMAN is outside the scope of this tutorial. If you need help setting up and using RMAN, refer to [Oracle’s documentation](https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89346) or loop in a member of your technical team.

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](https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89346) 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;
```

Information note **Important**: To ensure that archive log files don’t consume all of your available disk space, you should also set the `DB_RECOVERY_FILE_DEST_SIZE` parameter to a value that agrees with your available disk quota. Refer to [Oracle’s documentation](https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#BRADV89425) for more info about this parameter.

#### Step 2.4: Enable supplemental logging

Information note **Note**: This step requires system administrator (`SYSDBA`) privileges in Oracle.

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](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm#i1021068) 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 3: Create a Stitch Oracle database user

Information note **Note**: This step requires `CREATE USER` and `GRANT` privileges in Oracle.

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.

* Instructions
* Privileges list

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 `<stitch_username>` with the name of the database user and `<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_username>
   ```

4. Grant the Stitch user `SELECT` privileges on the following system tables:

   ```

   ```

   ```
   GRANT SELECT ON all_constraints to <stitch_username>
   GRANT SELECT ON all_cons_columns to <stitch_username>
   GRANT SELECT ON all_tab_columns to <stitch_username>
   GRANT SELECT ON all_tables to <stitch_username>
   GRANT SELECT ON all_views to <stitch_username>
   GRANT SELECT ON all_constraints to <stitch_username>
   GRANT SELECT ON SYS.V_$DATABASE TO <stitch_username>
   ```

5. Grant the Stitch user `SELECT` privileges by running this command for every table you want to replicate:

   ```

   ```

   ```
   GRANT SELECT ON <schema_name>.<table_name> to <stitch_username>
   ```

   Limiting access to only the tables you want to replicate ensures that the integration can complete discovery (a structure sync) in a timely manner. If you encounter issues in Stitch where tables aren’t displaying, try limiting the Stitch database user’s table access.

Information note

**Important:** **Using Log-based Incremental Replication**

If you want to use Log-based Incremental Replication, you’ll also need to grant additional permissions to the Stitch user:

```

```

```
GRANT EXECUTE_CATALOG_ROLE TO <stitch_username>
GRANT SELECT ANY TRANSACTION TO <stitch_username>
GRANT SELECT ANY DICTIONARY TO <stitch_username>
GRANT EXECUTE ON DBMS_LOGMNR TO <stitch_username>
GRANT EXECUTE ON DBMS_LOGMNR_D TO <stitch_username>
GRANT SELECT ON SYS.V_$DATABASE TO <stitch_username>
GRANT SELECT ON SYS.V_$ARCHIVED_LOG TO <stitch_username>
```

**If you’re using version 12 of Oracle**, you’ll also need to grant the `LOGMINING` privilege to the Stitch user:

```

```

```
GRANT LOGMINING TO <stitch_username>
```

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](https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_8003.htm#i2065278) | Required to log into the Oracle database. |
| SELECT | Required to select data from specified tables. |
| [EXECUTE_CATALOG_ROLE](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm#i1014380) | **Required to use Log-based Incremental Replication.** Required by Oracle to access objects in the `SYS` schema. |
| [EXECUTE ON DBMS_LOGMNR](https://docs.oracle.com/database/121/ARPLS/d_logmnr.htm) | **Required to use Log-based Incremental Replication.** Allows the Stitch user to execute the `DBMS_LOGMNR` package for LogMiner. |
| [EXECUTE ON DBMS_LOGMNR_D](https://docs.oracle.com/database/121/ARPLS/d_logmnr.htm) | **Required to use Log-based Incremental Replication.** Allows the Stitch user to execute the `DBMS_LOGMNR` package for LogMiner. |
| [SELECT ON SYS.V_$DATABASE](https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1073.htm#REFRN30047) | Required to validate the database’s configuration settings (archiving mode, supplemental logging, etc). |
| [SELECT ANY TRANSACTION](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm#i1014380) | **Required to use Log-based Incremental Replication.** Requied by Oracle to query the `SYS.V$LOGMNR_CONTENTS` view. |
| [SELECT ANY DICTIONARY](https://docs.oracle.com/cd/B19306_01/network.102/b14266/admusers.htm#i1007207) | Required to select from system data dictionary objects. |
| [SELECT ON SYS.V_$ARCHIVED_LOG](https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1016.htm#REFRN30011) | **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](https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1154.htm#REFRN30132) | **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](https://docs.oracle.com/database/121/ARPLS/d_logmnr.htm#ARPLS66809) | **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 4: Retrieve the database's Oracle System ID

Information note **Note**: This step requires access to the `SYS.V_$THREAD` performance view.

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 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](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#define-connection-details)

* [Step 5.2: Define the SSH connection details](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#ssh-connection-details)

* [Step 5.3: Define the default replication method](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#define-default-replication-method)

* [Step 5.4: Create a replication schedule](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#create-replication-schedule)

#### Step 5.1: Define the database connection details

1. If you aren’t signed into your Stitch account, [sign in now](https://app.stitchdata.com/).

2. On the Stitch Dashboard page, click the **Add Integration** button.

3. Locate and 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 destination.

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

   * **Host (Endpoint)**: Enter the host address (endpoint) used by the Oracle instance. For example: This could be a network address such as `192.68.0.1`, or a server endpoint like `dbname.hosting-provider.com`.

   * **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 Oracle database user.

   * **Oracle System ID (SID)**: Enter the Oracle System ID (SID) of the database you retrieved in [Step 5](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#retrieve-oracle-system-id).

#### Step 5.2: Define the SSH connection details

Information note **Note**: Skip this step if you’re not using SSH to connect to Stitch.

If you’re using an SSH tunnel to connect your Oracle database to Stitch, you’ll also need to define the SSH settings. Refer to the [Setting up an SSH Tunnel for a database connection guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-database-connection) for assistance with completing these fields.

1. Click the **SSH Tunnel** checkbox.

2. Fill in the fields as follows:

   * **SSH Host**: Enter the public IP address or hostname of the server Stitch will SSH into.

   * **SSH Port**: Enter the SSH port on your server. (`22` by default)

   * **SSH User**: Enter the Stitch Linux (SSH) user’s username.

#### Step 5.3: Define the 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](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) 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](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#enable-logminer).

* **Full Table Replication** - Stitch will use Full Table Replication. Refer to the [Full Table documentation](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table) for more info, examples, and limitations for this method.

**Note**: [Key-based Incremental documentation](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental) is also available for this integration, but it must be set manually. This is due to Stitch requiring a Replication Key to be selected for every table set to replicate.

#### Step 5.4: Create a replication schedule

Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.

In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Oracle integrations support the following replication scheduling methods:

* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)

* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)

* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.

### Step 6: Select data to replicate

Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).

The last step is to select the tables and columns you want to replicate. [](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#schema)

**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.

* Selection options
* Individual tables and columns
* All tables and columns
* Database views

For Oracle integrations, you can select:

1. **Individual tables and columns**

2. **All tables and columns** (except views)

3. **Database views**

Click the tabs to view instructions for each selection method.

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 table’s name. A blue checkmark means the table is set to replicate.

4. After you set a table to replicate, a page with the table’s columns will display. De-select columns if needed.

5. Next, you’ll define the table’s Replication Method. Click the **Table Settings** button.

6. In the **Table Settings** page:

   1. Define the table’s **Replication Method**, or skip this step if you want to use the [integration’s default method](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#define-log-based-replication-setting).

   2. If using [Key-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental), select a [Replication Key](https://help.qlik.com/en-US/stitch/replication/replication-keys).

   3. When finished, click **Update Settings**.

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

8. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Information note

**Important:** Before using this feature, note that:

1. Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections.

2. Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.

Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.

1. Click into the integration from the Stitch Dashboard page.

2. Click the **Tables to Replicate** tab.

3. Navigate to the table level, selecting any databases and/or schemas that contain tables you want to replicate.

4. In the list of tables, click the box next to the **Table Names** column.

5. In the menu that displays, click **Track AllTables and Fields (Except Views)**:

   ![The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab](https://help.qlik.com/en-US/stitch/images/replication/select-all-tables-menu.png)The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tabThe Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab

6. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Setting a database view to replicate is similar to selecting a table, with a few differences. Refer to the [Replicating Database Views guide](https://help.qlik.com/en-US/stitch/replication/replicating-database-views) for detailed instructions.

At a high level, you’ll need to complete the following to select a database view:

1. [Verify the database user’s permissions](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--verify-database-user-permissions)
2. [Select the view](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--select-view-in-stitch)
3. **Optional**: [Define the view’s Primary Key](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-primary-key)
4. [Define the view’s Replication Method](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-replication-method)
5. [Save the view’s settings](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--save-view-settings)

### 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.**

Information note

**Initial replication jobs with Anchor Scheduling**

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.

#### 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.

Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.

## Oracle replication

* [Overview of Log-based Incremental Replication using LogMiner](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#logminer-replication-integration)

* [Data types](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#data-types)

### Overview of Log-based Incremental Replication using LogMiner

Stitch uses Oracle’s [LogMiner package](https://docs.oracle.com/cd/B19306_01/server.102/b14215/logminer.htm) 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](https://docs.oracle.com/en/database/oracle/oracle-database/18/strms/strms_glossary.html#GUID-6DC095AD-BC34-466D-9981-450178C04CA8), or SCNs, as [Replication Keys](https://help.qlik.com/en-US/stitch/replication/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](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) for a more detailed explanation, examples, and the limitations associated with this replication method.

### Data types

In the table below are the data types Oracle integrations support and the Stitch data type it will map to, depending on the version of the integration being used:

* the Success icon

  This data type is supported for this version of the integration.

  indicates that the data type is supported. Following the icon is the Stitch data type it will map to.
* the Info icon

  This data type is supported for this version of the integration, but there's additional info you should know.

  indicates that the data type is supported, but there is additional information you should know. Hover over the icon to view a tooltip with the information.
* the Info icon

  This data type isn't applicable to the integration.

  indicates that the data type isn't applicable to the integration. This is usually because the integration doesn't use that particular data type.
* the Remove icon

  This data type is unsupported for this version of the integration.

  indicates that the data type isn't supported. In Stitch, columns with unsupported data types will have **Unavailable** in the **Type** column of the **Tables to Replicate** tab.

Refer to the [Data typing guide](https://help.qlik.com/en-US/stitch/replication/supported-data-types) for more info about how Stitch identifies and types data when it's loaded into your destination.

**Note**: This table doesn't display info for versions that have been sunset.

| **Data type** | **Stored as** |
| --- | --- |
| **ADT** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| **BIGINT** | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>INTEGER |
| [FLOAT](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1834) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>FLOAT |
| [FLOAT](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1834) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>FLOAT |
| **BIT** | the Info icon<br><br>This data type isn't applicable to Oracle. |
| **BLOB** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1821) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>STRING |
| **CLOB** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| **COLLECTION** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT413) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>STRING<br><br><br>, formatted as DATE-TIME |
| [NUMBER](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>NUMBER |
| [NUMBER](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>NUMBER |
| [FLOAT](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>FLOAT |
| [INTEGER](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>INTEGER |
| **LONG** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| **LONG RAW** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| **LONGNVARCHAR** | the Info icon<br><br>This data type isn't applicable to Oracle. |
| **LONGVARCHAR** | the Info icon<br><br>This data type isn't applicable to Oracle. |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1828) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>STRING |
| **NCLOB** | the Remove icon<br><br>This data type is unsupported for this version of the integration. |
| **NUMERIC** | the Info icon<br><br>In Oracle, this is &lt;strong&gt;number&lt;/strong&gt;: &lt;strong&gt;(\*,0)&lt;/strong&gt; is stored as &lt;strong&gt;integer&lt;/strong&gt; and &lt;strong&gt;(\*,\*)&lt;/strong&gt; is stored as &lt;strong&gt;decimal&lt;/strong&gt;.<br><br><br>INTEGER OR DECIMAL |
| **NVARCHAR** | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>STRING |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1825) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>STRING |
| [NUMBER](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>NUMBER |
| [INTEGER](https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/datatypes.htm#CJAEAEJG) | the Success icon<br><br>This data type is supported for this version of the integration.<br><br><br>INTEGER |
| **TIME** | the Info icon<br><br>This data type isn't applicable to Oracle. |
| **TIMESTAMP** | the Info icon<br><br>Applicable to &lt;strong&gt;timestamps with time zone&lt;/strong&gt; and &lt;strong&gt;timestamps with local time zone&lt;/strong&gt;.<br><br><br>STRING<br><br>, formatted as DATE-TIME |
| **TINYINT** | the Info icon<br><br>This data type isn't applicable to Oracle. |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1822) | the Info icon<br><br>This data type is synonymous with &lt;strong&gt;varchar2&lt;/strong&gt;.<br><br><br>STRING |
| [STRING](https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1822) | the Info icon<br><br>This data type is synonymous with &lt;strong&gt;varchar&lt;/strong&gt;.<br><br><br>STRING |