Skip to main content
Question

Error while flushing the cursor for feature class 'test1'. Error number frm ArcObjects is: '-2147216072'. Error message from ArcObjects is: {Underlying DBMS error [ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

  • October 24, 2017
  • 2 replies
  • 259 views

Forum|alt.badge.img

I am creating feature class using geoprocessing tool, in that i have some columns with VARCHAR(2000), while writing features i am getting An error occurred while flushing the cursor for the table/feature class 'featureclass1'. The error number from ArcObjects is: '-2147216072'. The error message from ArcObjects is: {Underlying DBMS error [ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column. But once i change VARCHAR(2000) to NCLOB its writing without any issues. i am not understanding why this happening. I have to use VARCHAR(2000) at any cost. Is any solution for this? I am using FME 2016 32 bit and ArcGIS 10.2.

Thank you.

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

trentatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • October 24, 2017

Hello @r8,

While the data that is returned does appear to be an Oracle error, the original source error appears to be the ArcObjects error '-2147216072', This suggests a basic I/O database error. If the writer seems to fail on a specific feature, ensure the feature is not larger than the 2000 character limit.

 

 

There are a few more suggestions found here:

 

https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/Tips_for_Using_the_Geoda.htm

Forum|alt.badge.img
  • Author
  • October 27, 2017

Hello @r8,

While the data that is returned does appear to be an Oracle error, the original source error appears to be the ArcObjects error '-2147216072', This suggests a basic I/O database error. If the writer seems to fail on a specific feature, ensure the feature is not larger than the 2000 character limit.

 

 

There are a few more suggestions found here:

 

https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/Tips_for_Using_the_Geoda.htm
Hi @trentatsafe,

 

Thank you for your quick reply. I checked all the VARCHAR2(2000) columns and it has less than 2000 characters only. The writer was not even writing a single feature in target feature class.