Skip to main content
Question

Best option for catching DB related errors when writing to Oracle spatial tables

  • October 4, 2020
  • 2 replies
  • 19 views
dms2
Contributor
Forum|alt.badge.img+11

My translation writes features to spatial and non spatial Oracle tables in a given order.

The problem is that any eventual DB related error should be reported to a web service and also logged to an xls file.

I'm using Featurewriters to control the writing order ​but the Featurewriter transformer has no Rejected port. How do I catch DB errors then?

SQLExecutor is fine for non spatial tables but not for spatial tables with complex geometries (due to the character number limitation for sql statements).​

Should I keep the Featurewriter approach and use a shutdown python script to catch DB errors and do the Excel and web service part​? Is there any other option?

Thanks for the help.​

​

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.

2 replies

david_r
Celebrity
  • david_rCelebrity
  • October 5, 2020

Unfortunately this is a known weakness with the FeatureWriter, please consider adding your vote here: https://community.safe.com/s/idea/0874Q000000TkwiQAC

I would've used FeatureWriter + Python for this. You could also consider wrapping your workspace into a second (master) workspace, in which you could e.g. analyze the logs messages output from the FeatureWriter.

dms2
Contributor
Forum|alt.badge.img+11
  • dms2Contributor
  • Author
  • Contributor
  • October 5, 2020

Unfortunately this is a known weakness with the FeatureWriter, please consider adding your vote here: https://community.safe.com/s/idea/0874Q000000TkwiQAC

I would've used FeatureWriter + Python for this. You could also consider wrapping your workspace into a second (master) workspace, in which you could e.g. analyze the logs messages output from the FeatureWriter.

I'm voting right away.​

Thanks!​

Community Stats

32,207
Posts
122,305
Replies
39,891
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.