Warning message: Resetting a database that is still referenced.

Hi, ​@ebygomm.

Thanks for posting to the Community! Looks like you might of forgotten to provide your log file. Also, could we kindly ask which build of FME you’re running, an explanation of where the warnings are coming from in your workflow, and possibly the OS you have it installed on?

Thanks!

Build 24612, Windows Server 2019

It doesn’t cause any issues, it’s just ‘noise’ in the log file and on the web interface. The database mentioned in the log is one that is used within an SQL executor

Hello, ​@ebygomm.

I do appreciate your patience thus far. If possible, may we ask for a sample workspace and the log file to determine if we can reproduce the warning message on our end? If not, all good! We may ask you to submit a Support Ticket so we can take a look from there.

Thank you!

Not an answer, just wanted to note that I’ve been seeing this message on almost all of the workspaces I run. We used to see this message on some workspaces but it seems to be much more frequent since upgrading from 2021 to 2024.

As with ​@ebygomm , it doesn’t seem to cause any issues, and is always reported at the end of the translation (successful or not) but it feels like FME is not shutting down connections cleanly and it would be nice to know if there’s anything that can be done to improve on workspace design to avoid this.

This one is also annoying, the SQL is a single statement, I don’t need a warning about it. Just needless noise

No query delimiter specified; SQL will be treated as a single statement. To specify the delimiter token, write FME_SQL_DELIMITER <token> as the first line of SQL text

I see the same ”Resetting .. “ message for all FME Flow jobs that have a database connection to Oracle.

Would also like ot get rid of those as my customer does not understand why these warnings are shown.

Thanks.

Hi all.

Sorry for the delayed response. This issue is listed in the Known Issues for FME [FMEENGINE-85247].

Thanks

Today’s useless warning, I’ve set a filter on purpose, I’m not sure why that warrants a warning

Hello ​@ebygomm,

Thanks for sharing those warning messages. We’ll look into these. If you don’t mind - if you do find anymore you may think are not useful in the logs, we encourage you to list them down and submit a support ticket - we can investigate from there.

Thanks!