Issue Details (XML | Word | Printable)

Key: ODBC-218
Type: Bug Bug
Status: Open Open
Priority: Blocker Blocker
Assignee: Alexander Potapchenko
Reporter: Pedro Innecco
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ODBC Driver

Azure Data Factory crash issues when using Firebird ODBC driver

Created: 11/Jun/20 10:26 AM   Updated: 07/Jul/20 11:21 AM
Component/s: None
Affects Version/s: 2.0.5
Fix Version/s: None

File Attachments: None
Image Attachments:

1. microsoft_firebirdODBC_bug_screenshot.jpg
(83 kB)
Environment: Windows 10 VM 1909


 Description  « Hide
We are using the ODBC driver to load data from Firebird SQL into an Azure database using Azure Data Factory.

For that, we created a Windows 10 VM on-premise, which can access the Firebird SQL, and installed the Azure Data Factory Integrated Runtime, which works as the gateway to surface data to Azure Data Factory.

We noticed that with a particular dataset, the ADF process crashes on the local VM. After long sessions with the Microsoft product team for Azure Data Factory, they managed to isolate the issue to a bug in the Firebird ODBC driver.

Here is what Microsoft has to say. I'd be happy to share more information if required, but I'm afraid I will not do so in a public forum.

~~~~

So we have figured out the root cause after several times' on-call with you (thanks for your patience!). Here are the summary:

- First, this is a crash issue of the using 3rd party driver: Firebird ODBC driver. The following gives the call stack from the crash dump. So this is a bug in the 3rd party driver.

- - BTW, this seems an obsolete driver which hasn't been updated since 2017.

- Second, as far as we know, the Firebird driver bug only happens when using C# ADO .Net ODBC with big data set. If using native version of ODBC, the issue doesn't repro. As ADF Copy activity is using ADO .Net ODBC, you would hit the driver issue.

- Based on the current situation, ADF Copy activity cannot work well on the problematic driver, and a workaround suggestion is to use SSIS or other tools that don't use ADO .Net ODBC. Sorry for the inconvenience.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Pedro Innecco added a comment - 07/Jul/20 11:21 AM
Screenshot of debugging process showing the bug raised by the Firebird ODBC driver.