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?
