Skip to main content
To homepage To homepage

At one of my clients we are using the ODX and they set it up that for every different type of load they added the data source multiple times. So for the normal full loads there is 1 source . For the incremental loads of the same source there is a different source.

In the data source selection the include only the tables they need for the full load. and they do the same for the incremental. But from time to time task wil not execute without showing up in the execution log without an error. 

I have the feeling that because the includes je indirectly exclude the other tables and if they are running at the same time this cancels each other out. In the windows logs you can see that the package then is skipped but it's no where to be found in TX.

Does anyone have an explenation about this and/or an idea how we can fix this?

My idea was that maybe putting everything in 1 source and then create 2 different transfer task instead of 2 different sources would fix this problem. Would love to hear from other people about solutions.

Hi @Bernarddb 

They are using the same data source and the same tables. If they then execute the ODX Transfer Task at the same time there could be some blocks, but in general it mainly should just be more slow.

Can you show the exact error message?

That said I do agree, it would be smarter to have two transfer tasks on the data source, where one is running a full load and one runs incrementally. Additionally this would make it so they can’t run at the same time, which may resolve this issue.

As requested hereby the screenshot

 

Hi @Bernarddb 

OK, I see.

You would need it ordered to not be able to start running while the other one is doing so.

If you can get around this by making two transfer tasks in one data source instead of two data sources, that is the best way to do this.

Thanks. this was also my thought i will updated once we made the change if it indeed was the fix.

Hi @Bernarddb has the issue been resolved? If so please help us by marking a best answer above, or let us know if you have any follow up questions

I will check this tomorrow when i'm at the client that has this problem

It looks like updating to version 20.10.44 fixed it. Everything now shows up. They didn't combine the different task yet. So the fix for this one looks to be updating to 20.10.44.

Reply


Terms and ConditionsCookie settings