Forum Discussion
Timeout while fetching data from oracle table using dataflow ( Premium capacity P1)
Hi Team,
We are using P1 capacity and gateway to fetch oracle tables ( each table has appr >50 million records with atleast 30 columns) . When we create the dataflow and start the process we get a timeout error ( after 10 min). We have researched and tried solutions to disable "enhanced compute engine" and increased timeout( >12 hours) in advanced editor however it still fails.
Please find attached screenshot. Any help is deeply greatly appriciated.
Also we would like to know how such large & wide tables are handled in such scenarios?
Hi Anonymous
Try setting the following two options. Reference: Oracle.Database - PowerQuery M | Microsoft Docs
- CommandTimeout : A duration which controls how long the server-side query is allowed to run before it is canceled. The default value is ten minutes.
- ConnectionTimeout : A duration which controls how long to wait before abandoning an attempt to make a connection to the server. The default value is driver-dependent.
Example:
Oracle.Database("servername", [ConnectionTimeout=#duration(0,0,5,0), CommandTimeout=#duration(0,0,5,0)])
Regards,
Community Support Team _ Jing Zhang
If this post helps, please consider Accept it as the solution to help other members find it.
2 Replies
Hi Anonymous
Try setting the following two options. Reference: Oracle.Database - PowerQuery M | Microsoft Docs
- CommandTimeout : A duration which controls how long the server-side query is allowed to run before it is canceled. The default value is ten minutes.
- ConnectionTimeout : A duration which controls how long to wait before abandoning an attempt to make a connection to the server. The default value is driver-dependent.
Example:
Oracle.Database("servername", [ConnectionTimeout=#duration(0,0,5,0), CommandTimeout=#duration(0,0,5,0)])
Regards,
Community Support Team _ Jing Zhang
If this post helps, please consider Accept it as the solution to help other members find it.Isn't that 600 seconds timeout something you set on the Oracle side? How are you connecting, via SQLNet or via ODBC? Keep in mind that there is a connection timeout and a command timeout setting.
Also make sure that your gateway is not slowing you down - check its utilization when the refresh runs.
