Transaction-Level Read Consistency in On-premises gateway against Oracle (12.x)

[Eric7]

Hi, does the on-premises gateway ensure Transaction-Level Read Consistency when refreshing a dataflow from an Oracle database?

One of our dataflows contains two tables with referential integrity between them, a parent table A with about 1000 rows and a child table B with 50 million rows. There is about an hour difference in time between a full refresh of table A and B, which means that table B may well contain values referencing rows in A that do not exist in A in the dataflow after refresh.

Oracle supports an isolation level called SERIALIZABLE, which ensures Transaction-Level Read Consistency within one database transaction. Does the gateway utilize this?

Eirik

[v-janeyg-msft]

Hi, @Eric7 

Have you resolved the issue? If yes, kindly mark the helpful answer as a solution if you feel that makes sense. If not, let me know and I'll try to help you further. Thanks.

Best Regards

Janey Guo

[v-janeyg-msft]

Hi, @Eric7 

It should be implemented. But the timeout period needs to be set enough.

Like this:

If the data is large or changes quickly, it is recommended to use the DQ mode connection.

Best Regards

Janey Guo

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Eric7 · Accepted solution]

Hi, I assume then that the on-premises gateway does not ensure data consistency between each table in a dataflow against the same datasource. It would be better if it did, but we can handle this to some extent by  adding consistency checks in the transformations.