When you synchronize data between different DB flavours, eg. Oracle and PostgreSQL, you sometimes have to use double quotes as delimiters for table and column names. Eg. if you have created a table in PostgreSQL using double quotes (as Toad Data Model invariably does when it creates DDL scripts), you will ALWAYS need to use the quotes also in subsequent DML statements. However, the sync script never has those quotes, rendering your DMLs syntactically incorrect (resulting in "entity not found"). It would be nice to have the option to tell TDP to delimit table and column names with double quotes if necessary.
A small correction: You will need the quotes in DMLs, if you created the table with quotes AND in upper or mixed case. In Oracle, table and column names are created per default in upper case, in PostgreSQL in lower case. If you convert an Oracle model into PostgreSQL using Toad Data Modeler, you will have upper case names that always require the quotes in DMLs.
Yes, Eero, I think I've run into similar caveats with other platforms too. Wondering if this option gives some relief in your case?
Hi Gary,
thanks for your reply! I, too, had hoped that this setting would help. Unfortunately, the Synchronization Wizard ignores the option when generating the sync script... 
Cheers,
Eero
Hi,
why don't you rename tables at both plateforms with same unquoted fields ?
Oracle fields created with uppercase unquoted and PG fields with lowercase unquoted...
It works for a daily dms from oracle to PG.
I hope this help
Hi mercier,
thank for your reply! Renaming is an option, of course, and you can easily create a script for doing it even for large schemas with lots of objects. Still, since the schema creation is done with a tool (of ours, i.e. Quest), I'd love to have the option to do things right directly, without having to do cosmetics afterwards... 
Besides, in some cases, (3rd party) applications may actually break if you rename objects.
Cheers
Eero