Skip to main content
Solved

An error occurred while trying to truncate geodatabase table/feature class

  • January 4, 2021
  • 2 replies
  • 200 views
0xbox0
Contributor
Forum|alt.badge.img+5

Hi all,

 

I have an FME process that I run nightly to refresh a polygon feature class in my SQL Server geodatabase. What I'm trying to do is truncate the feature class first and then insert new features into the feature class.

 

It has worked successfully in the past, but it's not working properly at the moment. The truncate call fails and features get inserted into the feature class. Since the truncate is failing, now I have duplicates in the table. Please see the logs below..

 

2021-01-04 10:59:26| 248.2| 0.0|INFORM|Geodatabase Writer: Truncating table/feature class `GISO.Cadastral_FME'

2021-01-04 11:21:04| 303.4| 55.1|WARN |Geodatabase Writer: An error occurred while trying to truncate table/feature class `GISO.Cadastral_FME'. The error number from ArcObjects is: '-2147154945'. The error message from ArcObjects is: {Table schema changed after cursor declared [42000:[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Could not complete cursor operation because the table schema changed after the cursor was declared.] [geoDBweb.GISO.Cadastral_FME]}. The error will be ignored

2021-01-04 11:21:04| 303.4| 0.0|INFORM|Geodatabase Writer: The field 'OBJECTID' in table 'GISO.Cadastral_FME' will not be updated since it is not editable

2021-01-04 11:21:04| 303.4| 0.0|INFORM|Geodatabase Writer: The field 'SHAPE.STArea()' in table 'GISO.Cadastral_FME' will not be updated since it is not editable

2021-01-04 11:21:04| 303.4| 0.0|INFORM|Geodatabase Writer: The field 'SHAPE.STLength()' in table 'GISO.Cadastral_FME' will not be updated since it is not editable

 

My writer is GEODATABASE_SDE and I have set the transaction type to Non-Versioned Edit Session. Currently using FME Desktop 2019.1 . Any help would be much appreciated.

 

Thanks in advance!

 

 

Best answer by jlbaker2779

Looks like this is a known issue that pops up randomly. There are some patches listed in the ESRI article that may not be applied to your server(S).

 

https://support.esri.com/en/technical-article/000012156

 

Be a good idea to open a SAFE support ticket for this regardless.

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

J
Forum|alt.badge.img+2
  • jlbaker2779
  • 194 replies
  • Best Answer
  • January 4, 2021

Looks like this is a known issue that pops up randomly. There are some patches listed in the ESRI article that may not be applied to your server(S).

 

https://support.esri.com/en/technical-article/000012156

 

Be a good idea to open a SAFE support ticket for this regardless.

0xbox0
Contributor
Forum|alt.badge.img+5
  • 0xbox0Contributor
  • Author
  • Contributor
  • 6 replies
  • January 5, 2021

Thanks for the quick reply. I'm going to give this a try.

Community Stats

32,070
Posts
121,778
Replies
39,698
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.