How we can extract Oracle eloqua bulk api objects using Oracle Eloqua Connector in adf

Shaikh Juned Shaikh Jamil 0 Reputation points
2024-11-08T19:50:57.7+00:00

We want to ingest activities data from eloqua to snowflake using Oracle Eloqua Connector but we can't see activities table. But we are able to ingest activities data from eloqua bulk api. What is the reason?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,859 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Amira Bedhiafi 26,491 Reputation points
    2024-11-10T13:16:00.7833333+00:00

    The reason you can't see the activities table in the Oracle Eloqua Connector could be due to the connector’s limitations in accessing certain types of objects or tables directly. The Oracle Eloqua Connector in Azure Data Factory may have restricted visibility into specific system tables like "activities," or its available API endpoints might not support direct access to certain resources.

    Using the Eloqua Bulk API is a good alternative, as it’s designed for exporting large datasets efficiently, including complex data like activities. You could use a custom approach with a Web Activity in ADF to authenticate with the Bulk API and a Copy Activity to load the data into Snowflake, bypassing the need for direct connector access to the activities table. This setup would involve creating a Bulk API job for data extraction, polling the job status until it’s complete, and then copying the resulting data files.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.