Troubleshoot the Oracle Eloqua connector
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.
Resolve connection, sign-in, authentication, access, and rate-limit errors from the managed Oracle Eloqua connector in Lakeflow Connect.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
API Base URL is not valid
Error message:
API Base URL must be an https host with no path, e.g. https://secure.p03.eloqua.com; received '<value>'.
Cause: The API Base URL in the connection isn't an https URL that contains only a host. For example, the value includes a path such as /API/REST/2.0.
Solution:
Enter only the scheme and host of your instance's base URL, for example https://secure.p03.eloqua.com. To find the base URL, see Step 2: Find your API base URL.
Sign-in fails because of too many authorization attempts
Error message:
This user has already authorized this app within the allowed time frame of 60 seconds.
Cause: Oracle Eloqua accepts one OAuth authorization initiation per minute for each user of an app, and returns an HTTP 429 response for additional attempts. See Authenticate using OAuth 2.0.
Solution:
Wait at least 60 seconds, then click Sign in with Oracle Eloqua again.
Connection creation fails after you sign in
Cause: Oracle Eloqua authorization codes expire 60 seconds after Oracle Eloqua issues them. If the code isn't exchanged for tokens within that time, Oracle Eloqua rejects it and the connection isn't created. See Authenticate using OAuth 2.0.
Solution:
Click Sign in with Oracle Eloqua again and complete the sign-in without delay. If Oracle Eloqua reports too many authorization attempts, see Sign-in fails because of too many authorization attempts.
Sign-in fails with a redirect URI error
Cause: Oracle Eloqua returned an invalid_redirect_uri error (error code 2509). The OAuth Callback URL of your Oracle Eloqua app doesn't match the redirect URI that Databricks sends.
Solution:
In Settings > AppCloud Developer, open your app and set the OAuth Callback URL to https://<workspace-url>/login/oauth/http.html. See Step 1: Register an Oracle Eloqua app.
Pipeline fails to authenticate
Cause: Oracle Eloqua returned an HTTP 401 response. This usually means one of the following: the Oracle Eloqua user revoked the app's access, the refresh token expired, or your instance moved to a different pod. Oracle Eloqua refresh tokens expire after one year if they aren't used.
Solution:
- Confirm that the API Base URL in the connection matches the current base URL of your instance. See Step 2: Find your API base URL.
- Recreate the connection authorization. See Create an Oracle Eloqua connection.
Pipeline fails with an access error
Cause: Oracle Eloqua returned an HTTP 403 response. The Oracle Eloqua user who authorized the connection doesn't have permission to read the requested data.
Solution:
Ask your Oracle Eloqua administrator to grant the user access to the data, or recreate the connection authorization as a user who has access. See Create an Oracle Eloqua connection.
Oracle Eloqua API rate limit exceeded
Cause: Oracle Eloqua returned an HTTP 429 response because the connector sent too many requests in a short period.
Solution:
The connector waits and retries automatically. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Oracle Eloqua instance.