Skip to main content
Question

Oracle (non spatial) writer behaviour if values are too long ?

  • July 18, 2018
  • 3 replies
  • 39 views
mhab
Contributor
Forum|alt.badge.img+10

Hello

I use a ORACLE non spatial writer (shortname ORACLE8I_DB), non-dynamic i.e. fixed definition of attributes. One of the attributes is defined as: HSN varchar2(10)

If I use this in my environment and if the attribute HSN is longer than 10 it gets written without any error or warning and is cut to length 10.

Problem:

If a customer in a different Oracle environment uses the same workspace with the same data the writer stops with ERROR complaining that the value is too long.

One time it cuts the data without any message, the other time it stops with ERROR.

Does anyone have an idea what maybe the reason for the different behaviour in the Oracle environments ?

Our Oracle expert says there is no option in Oracle to control this. Google didn't help either ...

Thanks for any hint

Michael

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

M
Forum|alt.badge.img+2

The Oracle writer has an Advanced Parameter: Enforce Strict Attribute Conversion = Yes|No This can change how FME handles attributes that are to long and need truncation.

mhab
Contributor
Forum|alt.badge.img+10
  • mhabContributor
  • Author
  • Contributor
  • July 19, 2018

The Oracle writer has an Advanced Parameter: Enforce Strict Attribute Conversion = Yes|No This can change how FME handles attributes that are to long and need truncation.

Good to know.

 

BUT: It is the same workspace running in both enviroments. So I think the FME workspace should have the same behaviour in all places ?!

 

 

M
Forum|alt.badge.img+2
Good to know.

 

BUT: It is the same workspace running in both enviroments. So I think the FME workspace should have the same behaviour in all places ?!

 

 

Yes it should have the same behaviour. Perhaps check that you are running the same version of FME on both machines. Also, open the workspace on the problem machine and check that the Enforce Strict Attribute Conversion = No , as it should be on your machine.

 

 

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.