Skip to main content
To homepage To homepage

Hi

In an effort to resolve intermittent ODX errors whilst retrieving data back from Oracle JDE tables I am trying to understand whether reducing the ‘concurrent execution threads’ setting in the Oracle data source connections could be a potential solution.

I have multiple Oracle connections set up in TX, with each connection pulling a subset of tables (e.g. all the JDE master file tables in one connection, all the transaction-related GL tables in another etc). All these connection transfer tasks are then wrapped up in a TX job scheduled to run each evening.

The ‘concurrent execution threads’ default value across all the Oracle data connections I had set up for this was ‘8’.

My thinking was that if TimeXtender is running multiple data pulls simultaneously then this could be causing resource contention issues on the source Oracle server, and thereby intermittently triggering data pull failures with generic error messages that don’t precisely indicate root cause.

I have since changed the ‘concurrent execution threads’ value to ‘1’ across all my Oracle connections in TX, so was expecting this to increase the job run time as the tables would now be pulled sequentially. However, this seems not to have been the case as the job run times are exactly the same as before the change of this value.

Is my understanding about the ‘concurrent execution threads’ incorrect inasmuch that this does not change whether tables pulls are run in parallel or not? And is it possible to tell if the table pulls associated with a job are actually running in parallel?

 

 

 

Hi ​@Paul Bridge 

Can you please confirm which version of TimeXtender you are using, as well as the particular Oracle provider you are using?

Thanks

Hi ​@Paul Bridge 

If you have multiple Oracle data sources pointing at the same source running at the same time, then yes that might be why it behaves like so. 

Is it all one database or multiple running on the same server? If you connect to the same database with multiple data sources they can run at the same time.

A way to test this would not be to limit the concurrent execution but to make sure only one Transfer task transferring data from oracle is running at the same time.

Hi Christian

TDI v7026.1

TimeXtender Oracle Data Source 23.1.4.0

Regards

Paul

 

Hi ​@Paul Bridge 

Thanks for the info. I don’t know anything has changed so that it would behave differently if you used the newest versions.

Are you sharing the same Oracle server and database across the data sources?

Hi Thomas

Yes, I have multiple cloned connections all pointing at the same data source, with each data connection pulling a subset of different JDE tables. In the ODX job in TDI there is a job which contains these individual table transfer and storage management tasks and I am wondering whether having these all in the same job means that they potentially run concurrently and are overloading the source Oracle server.

 

 

Hi ​@Paul Bridge 

Thanks for the image.

If your tasks are all the same data source it will do each task in steps, but otherwise it will run them at once.

So yes that it will run a lot of tables at once and potentially affect the oracle server.

You can see this behavior once a task is started where multiple tasks will show as running at the same time. The limit being that it can’t run two tasks at once in a data source.

Hi ​@Paul Bridge does the above comment help answer your question / resolve your issue? If so please help us by choosing a best answer above. If you have any follow up questions then please let us know

Terms and ConditionsCookie settings