# Set this flag entry to true/false if you want to enable synchronization and queue jobs if they are using same target or using same datapool
We set this value to false. Today is the first day we're getting a load from testers using the tool and we're seeing these two errors come up on any of the datapools at the testmatch step.
ORA-00942: table or view does not exist
ORA-00955: name is already used by an existing object
Sometimes it's the first, sometimes the second. But these are referencing the FNV view that is connected to the TestMatch and we've gone and checked and those views are there and available.
In addition, when we run it (or another user) it works. So we aren't sure what is causing this intermittent failure, but we would like to resolve it as it is happening more frequently than we'd like. (About 1/3 of the time.)
Release : 4.8
Component : CA Test Data Manager
Engineering reviewed the logs and preformed a deep dive analysis on the Testmatch code. The problem caused by enabling concurrency, is that Testmatching was not designed with concurrency enabled in mind. This will be converted to an Enhancement request as a placeholder for future work on Testmatch.