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.