Skip to main content
Solved

error number from ArcObjects is: '-2147154945'

F
Forum|alt.badge.img

Hi all,

I am using FeatureWriter to update an existing Feature Class that lives in my SDE.

Versioning is enabled. The Transaction Type is a Versioned Edit Session and my Writer Mode is Insert. I have Drop Table as No and Truncate Table as Yes. Essentially I want to replace the old FC with the new one I am creating.

I noticed the writing was taking a while, and it seems like it eventually times out. Maybe this is the case, I want to double check with the community.

The full error message is:

"An error occurred while attempting to store a row into the table 'SDE.XXXX'. The error number from ArcObjects is: '-2147154945'. The error message from ArcObjects is: {Table schema changes after cursor declared [42000:[Microsoft][SQL Server Native Client 11.0][SQL Server]Could not complete cursor operation because the table schema changed after the cursor was declared.] [DB.SDE.XXXX]}"

To note: I am not touching anything while this process is running.

Thanks!

Best answer by trentatsafe

Hello @francism,

The performance hit you are seeing(the 46mins to write 15000 features) is likely as a result of writing to a versioned table. Versioned tables take a significant performance hit because each feature has to be verified before it is inserted. It should also be noted that Truncating is quite slow compared to a Drop table for example.

 

 

In terms of speeding the process up, you may be able to speed up the process by bypassing the ArcSDE writer and using SQL to update the back-end database. This is not recommended, as you are bypassing all the safeguards that ArcGIS generally takes care of.

If dropping the table is not possible, unregistering the table as versioned, writing your updates and then re-registering your table as versioned could speed up the process of updates.

 

 

The SQL method I described above, we will have an article outlining the process of how to do this shortly. It is currently being written.

 

 

A few other things I noticed on your workspace, you have 3 File Geodatabase readers, but you are only using one of them. You have 4 File Geodatabase writers, and you don't have any feature types for them.
View original
Did this help you find an answer to your question?

6 replies

trentatsafe
Safer
Forum|alt.badge.img+6
  • trentatsafeSafer
  • Safer
  • August 23, 2017
Hello @francism

 

Would you mind supplying the full log file and workspace.

 

This seems to be more of an underlying database issue from what I've been able to find. A few of the remedies seem to be either bug fixes or incorrect usage of SQL code. In your case, I don't imagine it is the latter.

 

If you are able to attach the log and workspaces that will help me troubleshoot the issue.

 

mygis
Supporter
Forum|alt.badge.img+13
  • mygisSupporter
  • Supporter
  • August 24, 2017

Hi @francism

FME is using dll's from ArcGIS as I know. Please make sure that your version of FME and ArcGIS are compatible. Also could you please try to use the SDE Writer to test if it works?

F
Forum|alt.badge.img
  • francism
  • Author
  • August 24, 2017
Hi @trentatsafe

 

You'll notice the runtime is 46 minutes, seems like a long time to write that many features (approx 15000) to an SDE.

 

 

featurewriter-tosde.fmw

 

featurewriter-tosdelog.txt

 

 

F
Forum|alt.badge.img
  • francism
  • Author
  • August 24, 2017
mygis wrote:

Hi @francism

FME is using dll's from ArcGIS as I know. Please make sure that your version of FME and ArcGIS are compatible. Also could you please try to use the SDE Writer to test if it works?

Hi @gisinnovationsb,

 

 

thanks for your response! I've been writing to FileGDB. I had not tried simply writing to SDE, it seems to be giving me the Error message.

 

 

Would this mean that my versions are not compatible?

 

 

I'm using FME Workbench 2017.0 with Esri License

 

ArcGIS 10.4

 

trentatsafe
Safer
Forum|alt.badge.img+6
  • trentatsafeSafer
  • Safer
  • Best Answer
  • August 24, 2017

Hello @francism,

The performance hit you are seeing(the 46mins to write 15000 features) is likely as a result of writing to a versioned table. Versioned tables take a significant performance hit because each feature has to be verified before it is inserted. It should also be noted that Truncating is quite slow compared to a Drop table for example.

 

 

In terms of speeding the process up, you may be able to speed up the process by bypassing the ArcSDE writer and using SQL to update the back-end database. This is not recommended, as you are bypassing all the safeguards that ArcGIS generally takes care of.

If dropping the table is not possible, unregistering the table as versioned, writing your updates and then re-registering your table as versioned could speed up the process of updates.

 

 

The SQL method I described above, we will have an article outlining the process of how to do this shortly. It is currently being written.

 

 

A few other things I noticed on your workspace, you have 3 File Geodatabase readers, but you are only using one of them. You have 4 File Geodatabase writers, and you don't have any feature types for them.
F
Forum|alt.badge.img
  • francism
  • Author
  • August 24, 2017
trentatsafe wrote:

Hello @francism,

The performance hit you are seeing(the 46mins to write 15000 features) is likely as a result of writing to a versioned table. Versioned tables take a significant performance hit because each feature has to be verified before it is inserted. It should also be noted that Truncating is quite slow compared to a Drop table for example.

 

 

In terms of speeding the process up, you may be able to speed up the process by bypassing the ArcSDE writer and using SQL to update the back-end database. This is not recommended, as you are bypassing all the safeguards that ArcGIS generally takes care of.

If dropping the table is not possible, unregistering the table as versioned, writing your updates and then re-registering your table as versioned could speed up the process of updates.

 

 

The SQL method I described above, we will have an article outlining the process of how to do this shortly. It is currently being written.

 

 

A few other things I noticed on your workspace, you have 3 File Geodatabase readers, but you are only using one of them. You have 4 File Geodatabase writers, and you don't have any feature types for them.
Thanks, this solution worked out.

 

 

I adjusted the from Truncating Table to Drop Table as well as ensuring that the Feature Class I'm writing to is Unregistered. I also adjusted my Transaction Type as a non-versioned Edit Session.

 

 

This worked for my problem and my Feature Writer is now working to the SDE.

 

 

Cheers!

Reply


Helpful Members This Week

Community Stats

31,206
Posts
118,311
Replies
38,811
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.