AnsweredAssumed Answered

Conflicts detected for deleted features on reconcile

Question asked by fannonj on Dec 3, 2015
Latest reply on Dec 4, 2015 by vangelo-esristaff



We have a customer who is increasingly reporting (since upgrading from 9.3.1 to 10.2.1 a year ago) that they are getting conflicts when reconciling versions. The conflicts reported are always related to deleted features in the edit version (see below example). 


The customer has a relatively small team and there are only approx 6 versions open at any time. Edit versions are created from SDE.default and this particular case, no other users/versions have modified the objects in question since the the version was created, so the deletes should not be causing conflicts. Also, other similar deletes in the same version have reconciled without conflicts and I have tried to reproduce the same issue by performing similar edits in a new version, but do not get the same issues.


I have tried looking at the sde_states and sde_state_lineages tables, as well as the _A and _D tables for the feature classes and can't see any obvious issues or differences between the conflicting objects and those that reconcile ok. However, I'm certainly not an expert in this area.


Does anyone have an idea what might be causing the conflicts? Is there another scenario, other than a change to the objects in the default version since the edit version was created, that would cause a conflict?


The feature classes involved are all part of a geometric network, could this be part of the problem?


Does anyone have some useful SQL queries that I can run to investigate the state tree for this version or reproduce the queries that the reconcile tool is performing to detect the conflicts?


Any thoughts or assistance would be much appreciated.


Note the customer is using:

ArcGIS Desktop 10.2.1 (with the utilities and telecoms update 3 patch)

SQL Server 2012 / SDE 10.2.1 (with the utilities and telecoms update 3 patch)