Skip to main content
To homepage To homepage
Solved

ODX transfer task results in command timeout

R
Participant
Forum|alt.badge.img

Hi community,

I have this strange thing I cannot explain. I have a data connection that has been working properly for months. Since the beginning of May the transfer task results in a time out error, where after 1 hour the command time out is reached. I have tried everything to resolve this error; nothing is working. I tried with one really small table and 1 thread (of course setting the time out to a few minutes 😉); same error. 

The strange thing is; I have cloned this exact data connection and tested the transfer task running this exact similar table over 1 thread. This works without any problems. I have also added several other tables, also without any problems I fetch the rows of all tables within a few seconds. 

Does anybody have ANY idea what might cause this extremely weird behaviour? 

Best answer by Christian Hauggaard

Hi @Remy Kamphuis | Victa I have created a support ticket for this

View original
Did this topic help you find an answer to your question?

6 replies

R
Contributor
  • RLB
  • Contributor
  • 75 replies
  • June 13, 2024

Is the failing table loaded incrementally?

What type of storage are you using? If ADLS Gen2: does deleting the parquet files solve the issue?

R
1 person likes this
  • R
    Remy Kamphuis | Victa
R
Participant
Forum|alt.badge.img

In this transfer task we only fully load the tables. The really small table I tested with contains 8 rows of data and only a few fields. We use ordinary on premise SQL server for data storage.

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Remy Kamphuis | Victa which version of TimeXtender are you using?

R
Participant
Forum|alt.badge.img
Christian Hauggaard wrote:

Hi @Remy Kamphuis | Victa which version of TimeXtender are you using?

Hi @Christian Hauggaard we are using TimeXtender 6284.1 and same ODX version.

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Remy Kamphuis | Victa I have created a support ticket for this

wouter.goslinga
TimeXtender Xpert
Forum|alt.badge.img+2

@Remy Kamphuis | Victa can you please try to sync the datatypes for the target table with the ODX datatypes (you can do this by right-clicking the top node of the target data area, choose Advanced → Synchronize data types). Make sure the datatypes are exactly the same between the source ODX table and the target data area table.

I have seen this problem multiple times with multiple customers and it always turned out to be a problem with an implicit type cast that does not throw an error but just times out.

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings