| Bug ID Number |
BUG-000125195 |
| Submitted | September 11, 2019 |
| Last Modified | June 5, 2024 |
| Applies to | Portal for ArcGIS |
| Version found | 10.6.1 |
| Operating System | Windows OS |
| Operating System Version | 2012 R2 |
| Status | Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
|
Additional Information
When a collaboration workspace sync does not include any non-hosted feature service, edits entries are written to the sde_versions table.
Assume a guest (G) organization is the replication to a collaboration host (H). Both have a replica for the feature service. Metadata for the replica on each participant stores the Replica Sync Generation number (RSG) and the Replica Server Sync Generation number (RSSG).
When H asks G for edits, the RSG is incremented but G does not have any edits to send back so H and the RSSG is never incremented. Incrementing the RSG triggers a version entry.
This behavior is not harmful. The next time an edit occurs, the sde_versions table edits are updated and the redundant entries removed.
If the shared data is not being edited, pause the sync on the guests collaboration workspace. This avoids replica sync calls being made and sde_versions entries building up. Sync can be enabled on the workspace at any time.
Workaround
Delete the replica from the GDB_ITEMS table and the replica versions from the SDE_versions table to remove the orphaned replica manually. However, this is an unsupported workaround because ESRI does not recommend directly editing system tables such as GDB_ITEMS and SDE_versions tables.
Steps to Reproduce