Oracle as a source

The Oracle source supports both cloud and on-premises endpoints. To connect to an on-premises database, your environment must have a self-managed Groundplex configured in the Classic Manager shared folder. Refer to Connect to on-premises endpoints for more information.

To use the Incremental load type, you'll need to select a column that contains the last updated timestamp for each table.

A timestamp column must be one of the following types:

  • TIMESTAMP
  • TIMESTAMP WITH TIME ZONE
  • TIMESTAMP WITH LOCAL TIME ZONE

Supported Snap account types

Designer and Classic Manager provide multiple Snap account types for most endpoints and not all types are compatible with AutoSync. When you create or edit a data pipeline, the existing credentials list includes only compatible accounts.

Many Snap accounts support references to JAR files. If you create an account that references a JAR file for use in AutoSync, you must use an absolute path to the JAR file.

For Oracle, Autosync supports:

  • Oracle Thin Account

Connection configuration

When you configure credentials in AutoSync, the Oracle properties include the following:

  • Credential label: A unique, meaningful name such as Oracle-Sales-Admin. If a configuration with the same name exists, AutoSync displays an Asset conflict error message.
  • Hostname: The name of the machine hosting the database.
  • Port number: The port number to connect to the database. Default value: 1521
  • Database name: The name of the database. For example, MyDB.
  • Username: A username for an account with the correct permissions for AutoSync to retrieve and synchronize data.
  • Password: The password for the account. Multiple retries with an invalid password can cause your account to be locked.
  • Database specifier type: The format of the JDBC URL. AutoSync formats the connection parameters into one of the following options. Default value: Service name
    • Service name: Uses the jdbc:oracle:thin@//HOST:PORT/DBNAME format.
    • SID: Uses the jdbc:oracle:thin@HOST:PORT:DBNAME format.
  • Share: (Optional) Select a user group to share this configuration with. Org admins create user groups to share credentials. If you are a member of a user group, you can select it from the dropdown. You can also select the global shared folder, which shares the credentials with everyone in your Org.
  • Validate and save: After saving, AutoSync adds the configuration to the list of saved credentials.
  • Select schema: AutoSync populates this list from the account. Choose the schema that contains the tables to load as a source.
  • Select tables to synchronize: After configuring a destination, choose tables to synchronize. AutoSync populates the list from your Oracle account.
  • Select the column that tracks the last modified time: To use Incremental or SCD2 load, select a column that tracks modifications. To use Full load, leave this field empty. Refer to Incremental load for more information.
  • Click Select another table to add another table to synchronize.