Skip to main content
Solved

PostGIS writer set to create if needed, still i get "table does not exist"

so_much_more
Supporter
Forum|alt.badge.img+6

I have a a workflow of moving several tables from one database to another one. I needed to make a change and wanted to test the workflow writing to my localhost instead of production database. So i changed the postgis writer from “Truncate existing” to “Create if needed” targeting my local test environemnt.

 

Still i get an error complaining that the tables does not exist?.. 
It does not matter if I hardcode the Table Qualifier or not. Or if i remove it all together. 
I have tried to not running the wb in cached mode etc..
Tried running the WB in both 2023 version which it was created in and in 2024 version.

 

“POSTGIS Writer: Table 'rplan.PblMidlByggAnleggOmråde' does not exist. Please check the Table Name specified, or modify the Table Handling value under Format Parameters”

And yes the schema “rplan” does exisit in my localhost database.

I have no explanation to why FME would struggle with this?

Best answer by nielsgerrits

Just to be sure, you changed the table handling for all featuretypes, correct? Because the error is from the second table.

View original
Did this help you find an answer to your question?

6 replies

nielsgerrits
VIP
Forum|alt.badge.img+52

Does FME connects with an account which has proper rights? Can you create a table using this connection?

so_much_more
Supporter
Forum|alt.badge.img+6
  • so_much_moreSupporter
  • Author
  • Supporter
  • March 7, 2025
nielsgerrits wrote:

Does FME connects with an account which has proper rights? Can you create a table using this connection?

Yes i can. I tried writing tables dynamically from a bunch of shapefiles into a newly created schema in the same database. -Your standard postgres default database with the postgres superuser. 

nielsgerrits
1 person upvoted this
  • nielsgerrits
    nielsgerrits
so_much_more
Supporter
Forum|alt.badge.img+6
  • so_much_moreSupporter
  • Author
  • Supporter
  • March 7, 2025

I did a test just setting up one reader and one writer to the same databse i am trying to write to above.
No issues…
 


With this one table created I ran the full workbench above and then it complained about the next table not already in the database. The workbench does not seem to pick up that the table handling parameter is changed. 

nielsgerrits
VIP
Forum|alt.badge.img+52
  • nielsgerritsVIP
  • VIP
  • Best Answer
  • March 7, 2025

Just to be sure, you changed the table handling for all featuretypes, correct? Because the error is from the second table.

so_much_more
Supporter
Forum|alt.badge.img+6
  • so_much_moreSupporter
  • Author
  • Supporter
  • March 7, 2025
nielsgerrits wrote:

Just to be sure, you changed the table handling for all featuretypes, correct? Because the error is from the second table.

Ooooohhh, ding ding ding! I completely overlooked that. My mindset was in the dynamic writer mode. You are completely right. It was set to truncate for the ones that was failing! Feel silly i overlooked that now! Thank you for spotting it, i was completely confused

nielsgerrits
VIP
Forum|alt.badge.img+52

Cheers :) I know the feeling.

Reply


Most helpful members this week

Community Stats

30,847
Posts
116,941
Replies
38,670
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.