We have some queries presented to our Oracle database coming from the Fme Server - They run approx 40000 time an hour and cannot figure out how are they being run- the query are in this format:
Select owner, table_name from all_tables where ownner in 'PUBLIC, XXXXX' AND TABLE_NAME = 'XXXXXXXXXXXXXXXXXX'.
We found that there are 3-4 queries of this nature. The question is how to find them and then stop as it is not producing any output. Any suggestion will be appreciated.
Best answer by fmelizard
Hi,
This is a known bug which we have fixed recently and will be available in FME 2013 SP2. We were making multiple calls to the ALL_TABLES and ALL_OBJECT_TABLES tables when attempting to determine if the requested feature class was a table or a view. It is particularly bad when making use of the FeatureReader or Joiner transformers
The fix is in FME 2013 build 13453 which is available now as a beta download from our website at http://www.safe.com/beta.
Unfortunately we won't be backporting this fix into FME 2012.
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
So you already know which workspace is doing the queries? It sounds like a workspace is in a "looping" condition doing the same query all over again. Might be worth to inspect some log-files on the FMEServer
1) Check your job queue. Are there lots of jobs sitting waiting to be processed? Perhaps someone sent a huge batch for processing during a test and they aren't getting cleared because you don't have enough engines to cope with the volume. If they are there, which workspace is being run?
2) If a workspace was run it may contain an FMEServerJobSubmitter or a WorkspaceRunner that is spawning other jobs. Do you have any workspaces like this?
3) Have you got any workspaces that run on a schedule and someone chose to run every second instead of say every week?
4) Have a look at the Job History tab in the Admin console. Does this show which workspace is being run?
5) Go to <fmeserverinstall>\\logs and have a look for the most recent log files by date. See what information they can shed on the issue.
6) Check the task manager on the machine. Does it look like the fmeengine.exe processes are thrashing. Try restarting the FME Server service and see if they return to the same state. Are you sure its definately FME Server and someone isn't calling FME Desktop in batch? If it's the latter it may be harder to hunt out the culpret.
This is a known bug which we have fixed recently and will be available in FME 2013 SP2. We were making multiple calls to the ALL_TABLES and ALL_OBJECT_TABLES tables when attempting to determine if the requested feature class was a table or a view. It is particularly bad when making use of the FeatureReader or Joiner transformers
The fix is in FME 2013 build 13453 which is available now as a beta download from our website at http://www.safe.com/beta.
Unfortunately we won't be backporting this fix into FME 2012.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.