Users should not run queries on the Central Base using "Tools after module generation". Refer to official documentation for details about the tool editor CMS - Tool editor
If the SQL error is related to a non-existing table or non-existing column (example : "Relation xxxx does not exist" ot "Column xxx does not exist"), the root cause is likely to be a known vulnerability in Cast-MS that will be fixed in Service Pack 8.2.9
If user defines a Tool after module generation and sets the search path to the Central Base instead of the Local Base, then all the SQL queries and procedures in the further steps may be affected.
To remedy the situation,
- Remove any "set search_path = xxx" in the scripts registered as "Tools after module generation"
- Prefer prefixing all involved tables, views and procedures with the name of the local base.
- Relaunch snapshot
