Skip to main content
  • Home
  • Forums
  • FME Form
  • Data
  • Writing to Oracle Spatial with apparently valid geometries - but are rejected by Oracle DB
Solved

Writing to Oracle Spatial with apparently valid geometries - but are rejected by Oracle DB

  • November 5, 2013
  • 3 replies
  • 24 views
B
Hello all

 

 

I have had it  several times, that i cannot write to Oracle Spatial DB apparently correct (at least by GeometryValidator Transformer) geometries. I can write these geometries with other writers (i tested ESRI shapes and ESRI geodatabase). I know that oracle has his own strict geometry validation rules.

 

 

Strange enough, the ORA-Error echoed back (ORA 20263) is not a common error found here for example:  http://docs.oracle.com/cd/B14117_01/server.101/b10744/toc.htm

 

 

Is there a way to check before the insert, if a geometry is valid (in strict Oracle DB terms). Or is there a parameter within the writer that can catch the Ora-Error, skip the geometry, and continue the process of writing with the other pending geometries?

 

 

I'm working with FME Desktop 2013 (20130124), DB is Oracle Spatial 10.2.0.4.0

 

 

Yes, you guessed right, english is not my native language.

 

 

I appreciate your help. 

 

 

Bernard

 

 

 

 

 

Best answer by fmelizard

Hi Bernard,

 

 

Yes, disabling/enabling triggers and constraints can also be a way to avoid these errors.

 

Itay
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • November 5, 2013
Hi Bernard,

 

 

I cannot think of a way to do it 'on the fly' as you require (maybe sombody else can ?)

 

A possible workaround (didnt try it myself and not very elegant I admit) would be to insert the data to oracle (where no geom validation takes place), preform oracle validation on it (sdo_geom.validate_geometry_with_context) and select only the features that pass the validation to write.

 

 

Itay

 

 

 

B
  • bernard
  • Author
  • November 5, 2013
Hi Itay

 

 

Thanks for your reply.

 

I think I have to go that way. I found out in the meantime, that it is a BEFORE INSERT Trigger, that causes the mentioned ORA-Error. I will disable this trigger.

 

 

 

 

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • Best Answer
  • November 5, 2013
Hi Bernard,

 

 

Yes, disabling/enabling triggers and constraints can also be a way to avoid these errors.

 

Itay

Helpful Members This Week

Community Stats

30,929
Posts
117,225
Replies
38,734
Members

Latest FME

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.