Forum Discussion
Oracle source- Import Mode - schedule refresh timeout
Hi,
I have 8 tables in my model and i am using Import mode. My datasource is oracle and i gave timeout as 3600 minutes. My datset size is 16 MB. Below are the tables and the count.
Schedule refresh will run for 2 hrs and after that it fails. I am a Pro user.
i tried this schedule refresh during daytime as well as night time but it is failing.
Note:My desktop refresh is sucessful whenever i refresh.
I have enabled even additional logging but i dont get any precise message.
| table | count |
| A | 2268 |
| B | 174942 |
| C | 1051241 |
| D | 4100086 |
| E | 1940135 |
| F | 36 |
| G | 133994 |
Below is the error message
Timeout expired. The timeout period elapsed prior to completion of the operation
9 Replies
- AnonymousNot applicable
Hi Anonymous ,
Have you configured a gateway for it? Can you provide more detailed error messages?
Hope it helps!
Best regards,
Community Support Team_ Scott ChangIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
Yes I have installed standard Gateway and using the gateway to refresh it.
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Timeout expired. The timeout period elapsed prior to completion of the operation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}}
- AnonymousNot applicable
I have installed standard gateway and using that gateway refresh schedule is configured.
- AnonymousNot applicable
Hi Anonymous ,
If you are using the ODBC connector, there is currently a problem. Please try using the Oralce connector, or use the Personal Edition Gateway.
Hope it helps!
Best regards,
Community Support Team_ Scott ChangIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
The report is working fine with the scheduled refresh in my local machine. But when i use another machine which is a kindof server where we have installed the standard gateway we are getting the timeout issue. Still the scheduled refresh is not working in the server and i have enabled all the ports and domain name settings in the server but i am not sure why it does not work. it cannot connect to db i guess something is blocking and we are not sure what it is . Any ideas? Thanks in advance