When I understand correctly, the query executed is the select-part of:
create or replace table jhn_boote@sql2019
as
select *
from marina.ma_boote@mm_naarden
limit 10
The select raises an itgensql160 error which is an integrated check of the data retrieved by Invantive SQL from the backing platform (here probably Oracle) against the metadata retrieved earlier from the data source.
Sofar, I have only seen it occur when the metadata has changed between logging on and retrieving or uploading data. For instance, when you drop the table on Oracle and re-create it with columns different in type, name or number of, the itgensql160 error should occur.
Invantive SQL assumes that the metadata is stable for the duration of a session. On some platforms, like Teamleader or AFAS Profit, the metadata will be cached aggressively so it can take even hours for new custom fields or GetConnectors to show up.
In these scenarios it is a quick fix to just log on to the virtual database again. The metadata will be reloaded then.
Did logging on again help in your case?
If yes or not, please add it to the topic.
In the future the behaviour of the SQL engine might be adapted to avoid an itgensql160 error, such as reloading the metadata and re-running the query when it would otherwise have been triggered. But as of today, no decision yet has been made regarding that scenario; we are still collecting experiences.
PS. It is best to create a separate question/thread for each issue. That makes it easier to handle them.