Question

Hi when I am connecting from Postgresql db to FME getting below error Fetching Feature types error failed to retrieve feature types Please ensure that the dataset is accessible and has feature types available to read

  • 23 June 2022
  • 1 reply
  • 33 views

Log details :

 

FME Configuration: Using connection values from 'J10_170' for R_3

Creating reader for format: PostgreSQL

Trying to find a DYNAMIC plugin for reader named `POSTGRES'

FME API version of module 'POSTGRES' matches current internal version (3.8 20180604)

FME Configuration: Using connection values from 'J10_170' for R_3

Creating reader for format: PostgreSQL

Trying to find a DYNAMIC plugin for reader named `POSTGRES'

FME API version of module 'POSTGRES' matches current internal version (3.8 20180604)

Opening POSTGRES reader for dataset 'postgres'

PostGIS client encoding: 'UTF8'

PostgreSQL 9.5.25 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit

Successfully closed POSTGRES database reader

Successfully closed POSTGRES database reader

Merged 0 schema features read from 1 datasets into 0 resulting feature types

UniversalReader -- readSchema resulted in 0 schema features being returned

Reader Parameter(0) = >J10_170<

Reader Parameter(1) = >SCHEMAS_FOR_TABLE_LISTING<

Reader Parameter(2) = ><

Reader Parameter(3) = >FME_DELIM<

Reader Parameter(4) = >.<

Reader Parameter(5) = >FME_EXPAND<

Reader Parameter(6) = >postgres<

Reader Parameter(7) = >_MERGE_SCHEMAS<

Reader Parameter(8) = >YES<

Reader Parameter(9) = >RETRIEVE_ALL_TABLE_NAMES<

Reader Parameter(10) = >YES<

Reader Directive(0) = >RUNTIME_MACROS<

Reader Directive(1) = >SCHEMAS_FOR_TABLE_LISTING,,FME_DELIM,.,FME_EXPAND,postgres,_MERGE_SCHEMAS,YES,RETRIEVE_ALL_TABLE_NAMES,YES<

Configuration object contents:

FME Temporary Folder: D:\\TEMP

mapping file Line 0: `APPLICATION' `FME_WORKBENCH'

mapping file Line 1: `AUTOREG' `YES'

mapping file Line 2: `LOG_ENCODING' `UTF-8'

mapping file Line 3: `LOG_MAX_FEATURES' `-1'

mapping file Line 4: `LOG_APPEND' `NO'

mapping file Line 5: `FME_HOME' `C:\\Program Files\\FME\\'

mapping file Line 6: `FME_SESSION_USED' `TRUE'

mapping file Line 7: `R_3_METAFILE' `POSTGRES'

mapping file Line 8: `R_3_SCHEMAS_FOR_TABLE_LISTING' `'

mapping file Line 9: `R_3_FME_DELIM' `.'

mapping file Line 10: `R_3_FME_EXPAND' `postgres'

mapping file Line 11: `R_3__MERGE_SCHEMAS' `YES'

mapping file Line 12: `R_3_RETRIEVE_ALL_TABLE_NAMES' `YES'

mapping file Line 13: `R_3_SCHEMAS_FOR_TABLE_LISTING' `'

mapping file Line 14: `R_3_FME_DELIM' `.'

mapping file Line 15: `R_3_FME_EXPAND' `postgres'

mapping file Line 16: `R_3__MERGE_SCHEMAS' `YES'

mapping file Line 17: `R_3_MERGE_SCHEMAS' `YES'

mapping file Line 18: `R_3_RETRIEVE_ALL_TABLE_NAMES' `YES'

mapping file Line 19: `R_3_KNOWN_TO_BE_USING_NAMED_CONNECTION' `YES'

mapping file Line 20: `SCHEMA_TIME' `YES'

mapping file Line 21: `R_3_DATASET' `postgres'

mapping file Line 22: `R_3_HOST' `10.8.69.170'

mapping file Line 23: `R_3_PORT' `5432'

mapping file Line 24: `R_3_USER_NAME' `postgres'

mapping file Keyword: `R_3_METAFILE' occurs 1 time(s)

mapping file Keyword: `LOG_MAX_FEATURES' occurs 1 time(s)

mapping file Keyword: `R_3_SCHEMAS_FOR_TABLE_LISTING' occurs 2 time(s)

mapping file Keyword: `LOG_APPEND' occurs 1 time(s)

mapping file Keyword: `R_3_RETRIEVE_ALL_TABLE_NAMES' occurs 2 time(s)

mapping file Keyword: `R_3_PORT' occurs 1 time(s)

mapping file Keyword: `R_3_FME_DELIM' occurs 2 time(s)

mapping file Keyword: `R_3_HOST' occurs 1 time(s)

mapping file Keyword: `AUTOREG' occurs 1 time(s)

mapping file Keyword: `R_3_USER_NAME' occurs 1 time(s)

mapping file Keyword: `R_3__MERGE_SCHEMAS' occurs 2 time(s)

mapping file Keyword: `FME_HOME' occurs 1 time(s)

mapping file Keyword: `LOG_ENCODING' occurs 1 time(s)

mapping file Keyword: `APPLICATION' occurs 1 time(s)

mapping file Keyword: `R_3_PASSWORD' occurs 1 time(s)

mapping file Keyword: `R_3_KNOWN_TO_BE_USING_NAMED_CONNECTION' occurs 1 time(s)

mapping file Keyword: `R_3_FME_EXPAND' occurs 2 time(s)

mapping file Keyword: `R_3_MERGE_SCHEMAS' occurs 1 time(s)

mapping file Keyword: `SCHEMA_TIME' occurs 1 time(s)

mapping file Keyword: `R_3_DATASET' occurs 1 time(s)

mapping file Keyword: `FME_SESSION_USED' occurs 1 time(s)

UniversalReader -- readSchema resulted in 0 schema features being returned

Successfully closed POSTGRES database reader


1 reply

Badge +6

Hi @srinivas9my​, it would be worth checking if your POSTGRES database is configured properly to be read/edited. Here is a tutorial to help you get started https://community.safe.com/s/article/getting-started-with-postgis 

Reply