Skip to main content
Question

The error number from ArcObjects is: '-2147155559'.

yonasfme
Forum|alt.badge.img

I'm loading data (450k polygons) from FGDB into 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. The writing is very slow and after running for 3 hrs and 43 min the transaction failed with the following error:

An error occurred while attempting to start an edit operation. The error number from ArcObjects is: '-2147155559'. The error message from ArcObjects is: {Failure to access the DBMS server [08S01:[Microsoft][SQL Server Native Client 11.0]TCP Provider: The specified network name is no longer available. ] [sde.DEFAULT]}

Here is the log file:

Any idea why it is throwing that error?

Thanks.

1 Attachments

8 replies

redgeographics
Celebrity
Forum|alt.badge.img+49

Googling the ArcObjects error number doesn't seem to yield any useful results but the SQL Server one does come up with something useful. It all seems to indicate the network connection has been lost for whatever reason.

david_r
Celebrity
  • david_rCelebrity
  • March 16, 2018

Edit sessions are notoriously slow. What happens if you manually truncate the feature class using e.g. ArcMap before running your workspace?

See also https://knowledge.safe.com/questions/35018/table-truncating-takes-ages.html

yonasfme
Forum|alt.badge.img
  • yonasfme
  • Author
  • March 16, 2018

Thanks for your ideas guys but the loading is now completed successfully!

What did I do to make it work? Not much. I had multiple SDE writers in the workspace so I removed all except the one that writes the 450k polygons. I have also added the ArcSDEGrid Snapper transformer to simulates the ArcSDE conversion on each feature by performing ArcSDE translation, scaling, and coordinate snapping. It took 4 hrs and 14 mins!

I have created a ticket to find out why it took that long and how we can improve the speed. Will update when I hear back from Safe.

Thanks.

yonasfme
Forum|alt.badge.img
  • yonasfme
  • Author
  • March 16, 2018
david_r wrote:

Edit sessions are notoriously slow. What happens if you manually truncate the feature class using e.g. ArcMap before running your workspace?

See also https://knowledge.safe.com/questions/35018/table-truncating-takes-ages.html

We trying not to do any manual work as we have a lot of datasets to be loaded to the SDE.

 

 

yonasfme
Forum|alt.badge.img
  • yonasfme
  • Author
  • March 16, 2018
redgeographics wrote:

Googling the ArcObjects error number doesn't seem to yield any useful results but the SQL Server one does come up with something useful. It all seems to indicate the network connection has been lost for whatever reason.

That's interesting because other writers on the same workspace loaded a relatively smaller number of records successfuly to the same SDE.
yonasfme
Forum|alt.badge.img
  • yonasfme
  • Author
  • March 20, 2018

Here is an article recommend by Safe support for the possible reasons of the slowness of the workspace and its workaround:

https://knowledge.safe.com/articles/51216/editing-versioned-geodatabases-using-sql.html

 

Just want to share with the community and see what you think about it.

 

 

Thanks.

fmelizard
Safer
Forum|alt.badge.img+18
  • fmelizardSafer
  • Safer
  • March 20, 2018
yonasfme wrote:

Here is an article recommend by Safe support for the possible reasons of the slowness of the workspace and its workaround:

https://knowledge.safe.com/articles/51216/editing-versioned-geodatabases-using-sql.html

 

Just want to share with the community and see what you think about it.

 

 

Thanks.

Thanks @yonasfme

 

In particular the issue is related to the truncate.

 

"The reason we cannot do an explicit truncate is that the versioned table we are interacting with is, in fact, a view. Views are unable to be truncated. As such, we have to use a different command to perform the truncate."

 

yonasfme
Forum|alt.badge.img
  • yonasfme
  • Author
  • March 26, 2018
fmelizard wrote:
Thanks @yonasfme

 

In particular the issue is related to the truncate.

 

"The reason we cannot do an explicit truncate is that the versioned table we are interacting with is, in fact, a view. Views are unable to be truncated. As such, we have to use a different command to perform the truncate."

 

Thanks @MattAtSafe

 

Reply


Helpful Members This Week

Community Stats

31,341
Posts
118,871
Replies
38,944
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.