These are the settings I have on the writer
FME can create your tables for you, but the target schema will have to be created manually first.
You can e.g. use pgAdmin to create a schema in your database.
Hi @alex_chris, try setting "fme_feature_type" to the Schema Definition Name in the dynamic writer feature type explicitly.
Hi @alex_chris, try setting "fme_feature_type" to the Schema Definition Name in the dynamic writer feature type explicitly.
Yes, that did it. Thank you
Hi @alex_chris, try setting "fme_feature_type" to the Schema Definition Name in the dynamic writer feature type explicitly.
Elaboration. FME identifies a schema definition with it's name (Schema Definition Name) which is unique in a workpace, and usually the schema definition name is equal to the name of the source feature type, from which the schema definition has been derived.
By default, the Schema Definition Name in a dynamic writer feature type is set to use the destination feature type name you have set. If you would create a new table with the same name as the source table, it's not necessary to change the default behavior.
However, in the question case, you have set the destination table name which is different from the source table. It's the reason why you have to set the Schema Definition Name explicitly.
Hi,
i have nearly the same Problem.
Copying a postgis table with FME-Desktop works fine. But copying with FME-Server fails.
I use the same Version (2017.3) dwith FME-Desktop and FME-Server
do you have any ideas?
287INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT f_table_name, f_geography_column, coord_dimension, srid, type FROM geography_columns WHERE f_table_schema = 'ausbildung' AND f_table_name = 'beispiel'' 288INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT f_table_name, f_geometry_column, coord_dimension, srid, type FROM geometry_columns WHERE f_table_schema = 'ausbildung' AND f_table_name = 'beispiel'' 289INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT r_table_name, r_raster_column, '2', srid, 'RASTER' FROM raster_columns WHERE r_table_schema = 'ausbildung' AND r_table_name = 'beispiel'' 290ERROR0.00.2Today at 13:28:43Error executing SQL command ('select * from "ausbildung"."beispiel" where false limit 0'): 'ERROR: relation "ausbildung.beispiel" does not existLINE 1: select * from "ausbildung"."beispiel" where false limit 0 294WARN0.00.2Today at 13:28:43No spatial column was found for 'ausbildung.beispiel'. This is most likely a PostgreSQL table with no spatial data. No geometry will be read. If spatial data is not present, please try using the PostgreSQL reader instead 295WARN0.00.2Today at 13:28:43PostGIS geometry type unknown or empty (). Setting PostGIS geometry to 'postgis_none' 296ERROR0.00.2Today at 13:28:43Error executing SQL command ('select * from "ausbildung"."beispiel" where false limit 0'): 'ERROR: relation "ausbildung.beispiel" does not existLINE 1: select * from "ausbildung"."beispiel" where false limit 0,
Hi,
i have the same Problem. Reading and writing a postgistable dynamically works fine with fme-desktop, but if i run this workspace with FME-Server (2017) it fails.
fme-Server and FME-Desktop : same Version
Same postgis-db, same data
part of the fme-server log:
287INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT f_table_name, f_geography_column, coord_dimension, srid, type FROM geography_columns WHERE f_table_schema = 'ausbildung' AND f_table_name = 'beispiel'' 288INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT f_table_name, f_geometry_column, coord_dimension, srid, type FROM geometry_columns WHERE f_table_schema = 'ausbildung' AND f_table_name = 'beispiel'' 289INFORM0.00.2Today at 13:28:43Executing metadata query: 'SELECT r_table_name, r_raster_column, '2', srid, 'RASTER' FROM raster_columns WHERE r_table_schema = 'ausbildung' AND r_table_name = 'beispiel'' 290ERROR0.00.2Today at 13:28:43Error executing SQL command ('select * from "ausbildung"."beispiel" where false limit 0'): 'ERROR: relation "ausbildung.beispiel" does not existLINE 1: select * from "ausbildung"."beispiel" where false limit 0 294WARN0.00.2Today at 13:28:43No spatial column was found for 'ausbildung.beispiel'. This is most likely a PostgreSQL table with no spatial data. No geometry will be read. If spatial data is not present, please try using the PostgreSQL reader instead 295WARN0.00.2Today at 13:28:43PostGIS geometry type unknown or empty (). Setting PostGIS geometry to 'postgis_none' 296ERROR0.00.2Today at 13:28:43Error executing SQL command ('select * from "ausbildung"."beispiel" where false limit 0'): 'ERROR: relation "ausbildung.beispiel" does not existLINE 1: select * from "ausbildung"."beispiel" where false limit 0
do you have any idea?