Skip to main content
Solved

Postgres Dynamic Writer Not Working As Expected

  • July 1, 2022
  • 3 replies
  • 275 views
raaaju1990
Contributor
Forum|alt.badge.img+9

I have simple workbench, which pulls data from Oracle Spatial and writes the data into Postgres Dynamic Writer. The workbench when ran, throws the following error,

"Esri Geodatabase Writer: Feature Type Definition 'd_y_n' was requested, but not defined. Please visit https://www.safe.com/support

GEODATABASE_SDE writer: A fatal error has occurred. Check the logfile above for details

FeatureReader (QueryFactory): A fatal error has occurred. Check the logfile above for details"

WorkbenchThe attribute manager is used to match the name of the fme_feature_type_name and the dynamic writer featureclass name ,

Attribute ManagerThe dynamic writer has the following parameters as shown in the image,

Dynamic Writer 

I couldn't figure out what mistake am I making here. Could any one please help ?

 

Thanks in advance.

 

 

Best answer by nielsgerrits

Hi @nielsgerrits​  Thanks for the reply. May I please know what does it mean to update both streams ? could you please explain ?

I think you need to replicate what you did in the schema feature, replacing fme_feature_type_name to $(TARGET_TABLE), in the data features coming from the Generic outputport. AttributeExposer, expose fme_feature_type, AttributeManager, replace fme_feature_type with $(TARGET_TABLE).

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+60
  • nielsgerritsVIP
  • 2937 replies
  • July 1, 2022

Not sure if this will fix your issue, but I believe fme_feature_type_name  in the schema corresponds with fme_feature_type in the features so you should update both streams?

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
raaaju1990
Contributor
Forum|alt.badge.img+9
  • raaaju1990Contributor
  • Author
  • Contributor
  • 12 replies
  • July 1, 2022

Not sure if this will fix your issue, but I believe fme_feature_type_name  in the schema corresponds with fme_feature_type in the features so you should update both streams?

Hi @nielsgerrits​  Thanks for the reply. May I please know what does it mean to update both streams ? could you please explain ?

nielsgerrits
VIP
Forum|alt.badge.img+60
  • nielsgerritsVIP
  • 2937 replies
  • Best Answer
  • July 1, 2022

Hi @nielsgerrits​  Thanks for the reply. May I please know what does it mean to update both streams ? could you please explain ?

I think you need to replicate what you did in the schema feature, replacing fme_feature_type_name to $(TARGET_TABLE), in the data features coming from the Generic outputport. AttributeExposer, expose fme_feature_type, AttributeManager, replace fme_feature_type with $(TARGET_TABLE).

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...

Community Stats

32,062
Posts
121,727
Replies
39,689
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.