Oracle Database

Connect to your Oracle database.

Getting Started

Prerequisites to create an Oracle Database based workflow. You will need

1. A source Oracle Database connection.

2. (optional) A list of tables OR SQL queries.

3. (optional) A destination Oracle Database connection OR object storage connection.

For the source database connection, we recommend using a backup or clone with read-only permissions, instead of connecting directly to your production database.

Do not use your input database connection as an output connector. This action can result in the unintended overwriting of existing data.

Create a Connection

A oracle connection is created using the following parameters:

Connection Creation Parameters

name	Display name of your choosing used to identify your connection within Gretel.	my-oracle-connection
username	Unique identifier associated with specific account authorized to access database. The connection will be to this user's schema.	john
password	Security credential to authenticate username.	...
host	Fully qualified domain name (FQDN) used to establish connection to database server.	myserver.example.com
port	Optional Port number; If left empty, the default value - 1521- will be used.	1521
service_name	Name of database service to connect to.	my_service_name
(optional) instance_name	Optional Name of specific database instance for this connection.	instance_id
(optional) params	Optional JDBC URL parameters that can be used for advanced configuration.	key1=value1;key2=value2

Creating Connections

CLI

First, create a file on your local computer containing the connection credentials. This file should also include type, name , config, and credentials. The config and credentials fields should contain fields that are specific to the connection being created.

Below is an example Oracle Database connection:

{
    "type": "oracle",
    "name": "my-oracle-connection",
    "config": {
        "username": "john",
        "host": "myserver.example.com",
        "port": 1521,
        "service_name": "mydatabase"
    },
    "credentials": {
        "password": "..."
    }
}

Now that you've created the credentials file, use the CLI to create the connection

gretel connections create --project [project id] --from-file [credential_file.json]

Console

• Navigate to the Connections page using the menu item in the left sidebar.

• Click the New Connection button.

• Step 1, choose the Type for the Connection - Oracle Database.

• Step 2, choose the Project for your Connection.

• Step 3, fill in the credentials and select Add Connection.

Step 1, choose the Type of connection

Step 3, fill in credentials

SDK

from gretel_client import create_or_get_unique_project
from gretel_client.config import get_session_config
from gretel_client.rest_v1.api.connections_api import ConnectionsApi
from gretel_client.rest_v1.models import (
    CreateConnectionRequest,
    UpdateConnectionRequest,
)

session = get_session_config()
connection_api = session.get_v1_api(ConnectionsApi)

project = create_or_get_unique_project(name="oracle-workflow")

connection = connection_api.create_connection(
    CreateConnectionRequest(
        name="my-oracle-connection",
        project_id=project.project_guid,
        type="oracle",
        config={
            "username": "john",
            "host": "myserver.example.com",
            "service_name": "my_database",
            #"port": 1521,
            #"instance_name": "myinstance",
            #"params": "key1=value1;key2=value2",
        },
        # note: best practice is to read in credentials from a file
        # or secret instead of directly embedding sensitive values
        # in python code.
        credentials={
            "password": "...",
        },
    )
)

Permissions

In Oracle, the CREATE SCHEMA command does not create a new, standalone schema. Instead, one creates a user. When the user is created, a schema is also automatically created for that user. When the user logs in, that schema is used by default for the session. In order to prevent name clashes or data accidents, we encourage you to create separate Oracle users for the Source and Destination connections.

Source Connection Permissions

The Oracle source action requires enough access to read from tables and access schema metadata. The following SQL script will create an Oracle user suitable for a Gretel Oracle source.

-- Create the user
CREATE USER user
IDENTIFIED BY password  -- change to something more secure
DEFAULT TABLESPACE SYSTEM;

-- Required to log in
GRANT CREATE SESSION ON user;

Destination Connection Permissions

The following SQL script will create an Oracle user suitable for a Gretel Oracle destination. It will write to its own schema.

-- Create the user
CREATE USER user
IDENTIFIED BY password  -- change to something more secure
DEFAULT TABLESPACE SYSTEM  -- change if you have a separate tablespace
QUOTA UNLIMITED ON SYSTEM;  -- change to limit amount of space allocated

-- Required to log in
GRANT CREATE SESSION ON user;

-- Required for writes
GRANT CREATE TABLE ON user;

For more details please check your installation's version and see Oracle documents on CREATE USER.

Oracle Database Source Action

Type	oracle_source
Connection	oracle

The oracle_source action reads data from your Oracle database. It can be used to extract:

• an entire database, OR

• selected tables from a database, OR

• the results of SQL query/queries against a database.

Each time the workflow is run the source action will extract the most recent data from the source database.

When combined in a workflow, the data extracted from the oracle_source action is used to train models and generate data with the gretel_tabular action, and can be written to an output database with the oracle_destination action. Your generated data can also be written to object storage connections, for more information see Writing to Object Storage.

For the source database connection, we recommend using a backup or clone with read-only permissions, instead of connecting directly to your production database.

Inputs

The oracle_source action takes slightly different inputs depending on the type of data you wish to extract. Flip through the tabs below to see the input config parameters and example action YAMLs for each type of extraction.

Entire Database

Entire Database

sync.mode

full - extracts all records from tables in database (coming soon) subset - extract percentage of records from tables in database

Example Source Action YAML

actions:
  - name: extract-database
    type: oracle_source
    connection: conn_1
    config:
      sync:
          mode: full

Selected Tables

Selected Tables

sync.mode	full - extracts all records from selected tables in database (coming soon) subset - extract percentage of records from selected tables in database
tables: - name: - ...	Sequence of mappings that lists the table(s) in the database to extract. name - table name

Example Source Action YAML

actions:
  - name: extract-selected-tables
    type: oracle_source
    connection: conn_1
    config:
      tables:
        - name: client
        - name: location
      sync:
          mode: full

SQL Queries

SQL Query/Queries

queries: - name: query: ...

name - name of query; will be treated as name of resulting table query - SQL statement used to query connected database Additional name and query mappings can be provided to include multiple SQL queries

Example Source Action YAML

actions:
  - name: extract-sql-queries
    type: oracle_source
    connection: conn_1
    config:
      queries:
        - name: people
          query: select first_name, last_name from client
        - name: cities
          query: select city, state, country from location

Outputs

Whether you are extracting an entire database, selected tables, or querying against a database, the oracle_source action always provides a single output, dataset.

dataset

A reference to the data extracted from the database, including tables and relationships/schema.

The output of a oracle_source action can be used as the input to a gretel_tabular action in order to transform and/or synthesize a database.

Oracle Database Destination Action

Type	oracle_destination
Connection	oracle

The oracle_destination action can be used to write gretel_tabular action outputs to Oracle destination databases.

Inputs

Whether you are writing an entire database, selected tables, or table(s) created via SQL query, the oracle_destination action always takes the same input, dataset.

dataset	A reference to the table(s) generated by Gretel and (if applicable) the relationship schema extracted from the source database.
sync.mode	replace - overwrites any existing data in table(s) at destination append - add generated data to existing table(s); only supported for query-created tables without primary keys

Sync Modes

There are multiple strategies for writing records into the destination database. These strategies are configured from the sync.mode field on a destination config.

sync.mode may be one of truncate, replace, or append.

Sync Mode: Truncate

When sync.mode is configured with truncate, records are first truncated from the destination table using the TRUNCATE TABLE DML command.

When sync mode is configured with truncate the destination table must already exist in the database.

Sync Mode: Replace

When sync.mode is configured with replace, the destination table is first dropped and then recreated using the schema from the source table.

If the source table is from Oracle, the DDL is extracted using the GET_DDL interface from the DBMS_METADATA package. If the source table is from a non Oracle source, the destination table schema is inferred based on the column types of the source schema (if present) or data.

When sync mode is configured with replace the destination table does not need to exist in the destination.

To respect foreign key constraints and referential integrity, tables without foreign keys are inserted first, and tables with foreign key references are inserted last.

When applying table DML for truncate or replace, operations are applied in reverse insertion order. This is to ensure records aren't deleted with incoming foreign key references.

It's also important to note: all table data is first dropped from the database before inserting new records back in. These operations are not atomic, so there may be periods of time when the destination database is in an incomplete state.

Sync Mode: Append

When sync.mode is configured with append, the destination action will simply insert records into the table, leaving any existing records in place.

When using the append sync mode, referential integrity is difficult to maintain. It's only recommended to use append mode when syncing adhoc queries to a destination table.

If append mode is configured with a source that syncs an entire database, it's likely the destination will be unable to insert records while maintaining foreign key constraints or referential integrity, causing the action to fail.

Example Destination Action YAML

actions:
...
  - name: oracle-write
    type: oracle_destination
    connection: conn_2
    input: synthesize
    config:
      sync:
        mode: replace
      dataset: {outputs.synthesize.dataset}

Writing to Object Storage

You can also write your output dataset to an object storage connection like Amazon S3 or Google Cloud Storage. Whether you are writing an entire database, selected tables, or table(s) created via SQL query, the {object_storage}_destination action always takes the same inputs - filename and input, and path. Additionally, S3 and GCS take bucket and Azure Blob takes container.

filename	This is the name(s) of the file(s) to write data back to. File name(s) will be appended to the path if one is configured. This is typically a reference to the output from the previous action, e.g. {outputs.<action-name>.dataset.files.filename}
input	Data to write to the file. This should be a reference to the output from the previous action, e.g. {outputs.<action-name>.dataset.files.data}
path	Defines the path prefix to write the object(s) into.
[S3 and GCS only] bucket	The bucket to write object(s) to. Please only include the name of the bucket, eg my-gretel-bucket.
[Azure Blob only] container	The container to write object(s) to. Please only include the name of the container, eg my-gretel-container.

Example Destination Action YAML

S3 Destination

actions:
...
  - name: s3-write
    type: s3_destination
    connection: conn_2
    input: <action-name>
    config:
     bucket: my-gretel-bucket
     filename: {outputs.<action-name>.dataset.files.filename}
     input: {outputs.<action-name>.dataset.files.data}
     path: gretel

GCS Destination

actions:
...
  - name: gcs-write
    type: gcs_destination
    connection: conn_2
    input: <action-name>
    config:
     bucket: my-gretel-bucket
     filename: {outputs.<action-name>.dataset.files.filename}
     input: {outputs.<action-name>.dataset.files.data}
     path: gretel

Azure Blob Destination

actions:
...
  - name: azure-write
    type: azure_destination
    connection: conn_2
    input: <action-name>
    config:
     container: my-gretel-container
     filename: {outputs.<action-name>.dataset.files.filename}
     input: {outputs.<action-name>.dataset.files.data}
     path: gretel

Example Workflow Configs

Entire Database

Create a synthetic version of your Oracle database.

The following config will extract the entire Oracle database, train and run a synthetic model, then write the outputs of the model back to a destination Oracle database while maintaining referential integrity.

name: sample-oracle-workflow-full-db

actions:
  - name: oracle-read
    type: oracle_source
    connection: conn_1
    config:
      sync:
          mode: full

  - name: synthesize
    type: gretel_tabular
    input: oracle-read
    config:
      project_id: proj_1
      train:
        model: "synthetics/tabular-actgan"
        dataset: {outputs.oracle-read.dataset}
      run:
        num_records_multiplier: 1.0

  - name: oracle-write
    type: oracle_destination
    connection: conn_2
    input: synthesize
    config:
      sync:
        mode: replace
      dataset: {outputs.synthesize.dataset}

Selected Tables

Create a synthetic version of selected tables from your Oracle database

The following config will extract two tables from your database, train and run a synthetic model, then write the outputs of the model back to a destination Oracle database while maintaining any key relationships between the tables.

name: sample-oracle-workflow-selected-tables

actions:
  - name: oracle-read
    type: oracle_source
    connection: conn_1
    config:
      tables:
        - name: client
        - name: location
      sync:
          mode: full

  - name: synthesize
    type: gretel_tabular
    input: oracle-read
    config:
      project_id: proj_1
      train:
        model: "synthetics/tabular-actgan"
        dataset: {outputs.oracle-read.dataset}
      run:
        num_records_multiplier: 1.0

  - name: oracle-write
    type: oracle_destination
    connection: conn_2
    input: synthesize
    config:
      sync:
        mode: replace
      dataset: {outputs.synthesize.dataset}

.

SQL Queries to S3

Create a synthetic version of a dataset formed by querying your Oracle database and write to S3

The following config will execute a SQL query against your Oracle database to create a table containing data from across the database. Then, it will train and run a synthetic model to generate a synthetic table. Finally, the generated data will be written to an Amazon S3 bucket.

name: sample-oracle-sql-query-to-s3

actions:
  - name: oracle-read
    type: oracle_source
    connection: conn_1
    config:
      queries:
        - name: status_by_location
          query:
            SELECT location.city, location.state, location.zip, account.vip_status
            FROM client JOIN account ON client.client_id = account.client_id
            JOIN location ON client.client_id = location.client_id

  - name: synthesize
    type: gretel_tabular
    input: oracle-read
    config:
      project_id: proj_1
      train:
        model: "synthetics/tabular-actgan"
        dataset: {outputs.oracle-read.dataset}
      run:
        num_records_multiplier: 1.0

  - name: s3-write
    type: s3_destination
    connection: conn_2
    input: synthesize
    config:
      bucket: my-gretel-bucket
      filename: {outputs.synthesize.dataset.files.filename}
      input: {outputs.synthesize.dataset.files.data}
      path: gretel

Database to GCS

Create a synthetic version of your Oracle database and write the results to GCS.

The following config will extract the entire Oracle database, train and run a synthetic model, then write the output tables to an output Google Cloud Storage bucket while maintaining referential integrity.

name: sample-oracle-workflow-full-db

actions:
  - name: oracle-read
    type: oracle_source
    connection: conn_1
    config:
      sync:
          mode: full

  - name: synthesize
    type: gretel_tabular
    input: oracle-read
    config:
      project_id: proj_1
      train:
        model: "synthetics/tabular-actgan"
        dataset: {outputs.oracle-read.dataset}
      run:
        num_records_multiplier: 1.0

  - name: s3-write
    type: s3_destination
    connection: conn_2
    input: synthesize
    config:
      bucket: my-gretel-bucket
      filename: {outputs.synthesize.dataset.files.filename}
      input: {outputs.synthesize.dataset.files.data}
      path: gretel