Flashback Issue When Upgrading from SQL Server 2017 to 2019

Posted Sun, 26 Apr 2020 06:12:00 GMT by Jon Westcott

Upgrading from SQL Server 2017 to 2019 due to an issue of 2017 runtime in our server. With SQL Server 2019 we encountered an issue to load Oracle tables with the flashback activated to our datalake (SQL 2019).

Without the flashback we can load them successfully in SQL Server 2019. Before we were able to load them with the flashback to SQL Server 2017.

Posted Sun, 26 Apr 2020 14:10:58 GMT by BimlFlex Support

What error code are you running into?

Posted Mon, 27 Apr 2020 19:22:00 GMT by Jon Westcott

"An OLE DB error has occurred. Error Code: 0x80004005."

Posted Tue, 28 Apr 2020 16:20:10 GMT by BimlFlex Support

If some tables work and not others, then most likely there are data type issues, memory issues, or other table-level differences that affect the loads.

It could be the parameter value data type or some other implicit cast that leads to this error.