Skip to main content
Question

SQLCreator when used as a single transformer in a workbench file is unable to execute queries when run from FME Flow as a scheduled job


kirti2810kr
Contributor
Forum|alt.badge.img+1

There is one workbench file that only has a SQLCreator within it that executes some update queries in the database tables for Oracle DB.

This workbench was previously scheduled to run from FME server but  we recently migrated our FME environment from FME Server (on-prem) to FME Flow 2023 (azure environment). We are seeing issues when this process is run from FME Flow , the SQL queries defined to be executed within the SQLCreator are not getting executed. However, when run from FME Form (2023) it is working fine.

Can you please confirm if there is a known issue with SQLCreator from FME Flow.

We have observed that when SQLCreator is replaced with Creator+SQLExecutor , the process seems to be working fine from both FME Form and FME Flow.

Hence need confirmation to proceed with the change

2 replies

david_r
Evangelist
  • March 3, 2025

I’m not aware of any such issues. When you write “not getting executed”, what does that mean? Does the SQLCreator execute at all? Does the job log mention the SQLCreator at all?

Any error messages or warnings in the logs?


kirti2810kr
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • March 6, 2025
From FME Flow logs

Job log mentions that SQLCreater is being referenced but not about the query being executed.

 

From Form, below is the screenshot , Creating bulk features **** statement should be logged if query execution is working

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings