I am using ODX version 6143.1. When loading a table from a source system, incremental load on a datetime column (with an offset of 7 days) works fine. But when I set up the incremental load rule with Detect deletes and Detect updates selected, the first incremental load (which is the initial load) runs successful, but a second load (which should be the increment) gives me a 404 HTTP error:
Response status code does not indicate success: 404 (The specified path does not exist.).
Edit: problem only arises when setting the Delete detection option. When I remove this checkbox, the 404 error disappears (so the Detect primary key updates option does work correct).
What is the specific Oracle provider you use? It may relate to what provider type it is.
Hi Thomas, I'm using the OracleClient Data Provider; ODX storage is ADLS gen2
Can you use an Oracle SQL Profiler tool to review what query statements were sent to the source for HTTP 404 error ?
Also, there is a new option for the ADO and OLEDB data sources called "Date and time syntax'
Options are: Default, ANSI, and ODBC.
For Oracle, you will need to set it to ANSI to get the date-time formatting to work.
Given the fact that the error is an HTTP error I think the problem lies more on the ODX storage side, because HTTP is of course not used to connect to Oracle, but it is used to connect to the adls gen2 storage container.
You may use an Oracle query Profiler tool to review what query statements were sent to the source which led to HTTP 404 error in ODX processing. Also examine the folders in ADLS storage.
For additional troubleshooting, you may open a ticket with our support team.
@wouter.goslinga did you manage to resolve the error? Would you like to setup a screenshare to investigate further?
@Christian Hauggaard , no it is not solved yet, setting up a screenshare would be a good idea, i'll send you a DM.
@wouter.goslinga thanks for the call. What was the outcome of the test with the TimeXtender Oracle data source? Did you experience the same issue there, or was it only for the OracleClient Data Provider data source?