Ingest data from Oracle Eloqua

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Oracle Eloqua from the Previews page. See Manage Databricks previews.

Create a managed Lakeflow Connect pipeline that ingests Oracle Eloqua data into Unity Catalog tables. Use the Databricks UI, Declarative Automation Bundles, or a Databricks notebook.

Requirements

• To create an ingestion pipeline, first meet the following requirements:

  • Your workspace must be enabled for Unity Catalog.

  • Serverless compute must be enabled for your workspace. See Serverless compute requirements.

  • To create a new connection, you must have CREATE CONNECTION privileges on the metastore. See Manage privileges in Unity Catalog.

    If the connector supports UI-based pipeline authoring, an admin can create the connection and the pipeline at the same time by completing the steps on this page. However, if the users who create pipelines use API-based pipeline authoring or are non-admin users, an admin must first create the connection in Catalog Explorer. See Connect to managed ingestion sources.

  • To use an existing connection, you must have USE CONNECTION privileges or ALL PRIVILEGES on the connection object.

  • You must have USE CATALOG privileges on the target catalog.

  • You must have USE SCHEMA and CREATE TABLE privileges on an existing schema or CREATE SCHEMA privileges on the target catalog.

• To ingest from Oracle Eloqua, first configure authentication from Databricks and create a connection. See Configure authentication to Oracle Eloqua and Create an Oracle Eloqua connection.

Connector options

For the options the Oracle Eloqua connector accepts, their scope, and the tables they apply to, see Connector options. Set pipeline-scoped options in source_configurations. See Examples for usage.

Create an ingestion pipeline

For the list of supported source tables, see Supported source tables.

Databricks UI

1. In the sidebar of the Databricks workspace, click Data Ingestion.
2. On the Add data page, under Databricks connectors, click Oracle Eloqua.
3. On the Connection page of the ingestion wizard, select the connection that stores your Oracle Eloqua credentials. If you have the CREATE CONNECTION privilege on the metastore, click Create connection to create a connection with the credentials from Configure authentication to Oracle Eloqua.
4. Click Next.
5. On the Ingestion setup page, enter a name for the pipeline.
6. Select a catalog and a schema to write event logs to. If you have USE CATALOG and CREATE SCHEMA privileges on the catalog, click Create schema in the drop-down menu to create a schema.
7. Click Create pipeline and continue.
8. On the Source page, select the tables to ingest.
9. Click Save and continue.
10. On the Destination page, select a catalog and a schema to load data into. If you have USE CATALOG and CREATE SCHEMA privileges on the catalog, click Create schema in the drop-down menu to create a schema.
11. Click Save and continue.
12. (Optional) On the Schedules and notifications page, click Create schedule. Set the frequency to refresh the destination tables.
13. (Optional) Click Add notification to set email notifications for pipeline operation success or failure, then click Save and run pipeline.

Declarative Automation Bundles

Use Declarative Automation Bundles to manage Oracle Eloqua pipelines as code. Bundles can contain YAML definitions of jobs and tasks, are managed using the Databricks CLI, and can be shared and run in different target workspaces (such as development, staging, and production). For more information, see What are Declarative Automation Bundles?.

1. Create a bundle using the Databricks CLI:

   Bash

   databricks bundle init

2. Add two new resource files to the bundle:

   • A pipeline definition file (for example, resources/oracle_eloqua_pipeline.yml). See pipeline.ingestion_definition and Examples.
   • A job definition file that controls the frequency of data ingestion (for example, resources/oracle_eloqua_job.yml).

3. Deploy the pipeline using the Databricks CLI:

   Bash

   databricks bundle deploy

Databricks notebook

1. Import the following notebook into your Databricks workspace:

   Open notebook in new tabOpen in Databricks

2. Leave cells one, two, and three as they are.

3. Modify cell four with your pipeline configuration details. See pipeline.ingestion_definition and Examples.

4. Optionally configure advanced pipeline settings. See Common patterns for managed ingestion pipelines.

5. Click Run all.

Examples

The Oracle Eloqua connector makes its source tables available in the default source schema. For the list of tables, see Supported source tables. Ingest individual tables or the entire schema.

Ingest specific tables

Use this option to ingest a specific subset of tables, or to customize destination naming per table.

Declarative Automation Bundles

The following pipeline definition file ingests individual Oracle Eloqua tables:

YAML

resources:
  pipelines:
    oracle_eloqua_pipeline:
      name: oracle_eloqua_pipeline
      catalog: 'main'
      target: 'oracle_eloqua_data'
      ingestion_definition:
        connection_name: oracle_eloqua_connection
        objects:
          - table:
              source_schema: 'default'
              source_table: 'contact'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'
              destination_table: 'contact'
          - table:
              source_schema: 'default'
              source_table: 'campaign'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'
              destination_table: 'campaign'
          - table:
              source_schema: 'default'
              source_table: 'form_submission'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'
              destination_table: 'form_submission'

Databricks notebook

The following pipeline specification ingests individual Oracle Eloqua tables:

Python

pipeline_name = "oracle_eloqua_pipeline"
connection_name = "<oracle-eloqua-connection>"
pipeline_spec = {
  "name": pipeline_name,
  "ingestion_definition": {
    "connection_name": connection_name,
    "objects": [
      {
        "table": {
          "source_schema": "default",
          "source_table": "contact",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data",
          "destination_table": "contact"
        }
      },
      {
        "table": {
          "source_schema": "default",
          "source_table": "campaign",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data",
          "destination_table": "campaign"
        }
      },
      {
        "table": {
          "source_schema": "default",
          "source_table": "form_submission",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data",
          "destination_table": "form_submission"
        }
      }
    ]
  }
}
json_payload = json.dumps(pipeline_spec, indent=2)
create_pipeline(json_payload)

Ingest from a specific start date

Use the start_datetime option to control how far back the incremental tables read on their first sync.

Declarative Automation Bundles

The following pipeline definition file ingests Oracle Eloqua tables from a specific start date:

YAML

resources:
  pipelines:
    oracle_eloqua_pipeline:
      name: oracle_eloqua_pipeline
      catalog: 'main'
      target: 'oracle_eloqua_data'
      ingestion_definition:
        connection_name: oracle_eloqua_connection
        source_configurations:
          - api_source_connector_config:
              configs:
                start_datetime: '<start-datetime>'
        objects:
          - table:
              source_schema: 'default'
              source_table: 'contact'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'
              destination_table: 'contact'
          - table:
              source_schema: 'default'
              source_table: 'form_submission'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'
              destination_table: 'form_submission'

Databricks notebook

The following pipeline specification ingests Oracle Eloqua tables from a specific start date:

Python

pipeline_name = "oracle_eloqua_pipeline"
connection_name = "<oracle-eloqua-connection>"
pipeline_spec = {
  "name": pipeline_name,
  "ingestion_definition": {
    "connection_name": connection_name,
    "source_configurations": [
      {
        "api_source_connector_config": {
          "configs": {
            "start_datetime": "<start-datetime>"
          }
        }
      }
    ],
    "objects": [
      {
        "table": {
          "source_schema": "default",
          "source_table": "contact",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data",
          "destination_table": "contact"
        }
      },
      {
        "table": {
          "source_schema": "default",
          "source_table": "form_submission",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data",
          "destination_table": "form_submission"
        }
      }
    ]
  }
}
json_payload = json.dumps(pipeline_spec, indent=2)
create_pipeline(json_payload)

Ingest the entire schema

Use this option to ingest all Oracle Eloqua source tables into a single destination schema with one declaration.

Declarative Automation Bundles

The following pipeline definition file ingests all supported Oracle Eloqua tables into a destination schema:

YAML

resources:
  pipelines:
    oracle_eloqua_pipeline:
      name: oracle_eloqua_pipeline
      catalog: 'main'
      target: 'oracle_eloqua_data'
      ingestion_definition:
        connection_name: oracle_eloqua_connection
        objects:
          - schema:
              source_schema: 'default'
              destination_catalog: 'main'
              destination_schema: 'oracle_eloqua_data'

Databricks notebook

The following pipeline specification ingests all supported Oracle Eloqua tables into a destination schema:

Python

pipeline_name = "oracle_eloqua_pipeline"
connection_name = "<oracle-eloqua-connection>"
pipeline_spec = {
  "name": pipeline_name,
  "ingestion_definition": {
    "connection_name": connection_name,
    "objects": [
      {
        "schema": {
          "source_schema": "default",
          "destination_catalog": "main",
          "destination_schema": "oracle_eloqua_data"
        }
      }
    ]
  }
}
json_payload = json.dumps(pipeline_spec, indent=2)
create_pipeline(json_payload)

Declarative Automation Bundles job definition file

The following is an example job definition file for use with Declarative Automation Bundles. The job runs daily.

Declarative Automation Bundles

YAML

resources:
  jobs:
    oracle_eloqua_job:
      name: oracle_eloqua_job
      schedule:
        quartz_cron_expression: '0 0 0 * * ?'
        timezone_id: 'UTC'
      tasks:
        - task_key: oracle_eloqua_ingestion
          pipeline_task:
            pipeline_id: ${resources.pipelines.oracle_eloqua_pipeline.id}

Common patterns

For advanced pipeline configurations, see Common patterns for managed ingestion pipelines.

Next steps

Start, schedule, and set alerts on your pipeline. See Common pipeline maintenance tasks.

Additional resources

• Oracle Eloqua connector FAQ
• Oracle Eloqua connector limitations
• Oracle Eloqua connector reference
• Troubleshoot the Oracle Eloqua connector