Hello,
The TLDR is, we have a distributed collaboration that makes copies from out EGDB to our AGO and we're having issues with the database not fully compressing after doing bulk edits.
Environment:
- ArcGIS Enterprise: 11.2
- Enterprise Geodatabase: 10.9.1(SQL Server), with a dedicated feature data set that contain feature classes that we bulk reload (delete features and append) data. It's Traditional versioned without move edits to base) and has GlobalIDs. Just simple features: points, lines, and polygons.
- We're publishing the services to Portal with Feature Access turned on and Editing turned off. And the only operations allowed are Query and Sync.
- We have also set up a headless DB user account for publishing/sharing the data.
The problem:
We're testing out sharing data through the Distributed Collaboration to our ArcGIS Online and we've been running this for a week or two now. And I'm noticing that after we do a bulk reload of the feature classes we use for the distributed collaboration, then run a reconcile and compress script, the SDE_States aren't zero stating, and now we have 6 states and 3 of them were somehow produced (based on the time stamp) after we ran reconcile and compress. The SDE_versions table, I noticed, also has a growing list of Sync_Send and Sync_Receive, which share the same state_id as the states that aren't zeroing.
A few things I've tried but with no success.
- Manually kicked off the reconcile and compress. Which blocks/disconnects all users, reconciles and compresses, then allows connections again.
- Turned off the published services and re-ran.
- Unshared from the Distributed collab group, deleted the services from ArcGIS Server, and removed the feature service replicas (using Pro) and we have no geodatabase replicas. Then re-ran reconcile and compress.
- Latest attempt, tried unversioning the feature data set, which actually popup a message saying 4 of the feature classes were uncompressed and if I wanted to compress them before unversioning (I did).
I'm not a DBA by any stretch of the imagination, just knowledgeable enough to poke and prod and ask questions. So I'm not sure what to do at this point. We'd like to move this into production, but I'm hesitant to move forward if this is going to be an issue.
Thank you!
