| Bug-ID-Nummer |
BUG-000125195 |
| Eingereicht | September 11, 2019 |
| Zuletzt geändert | June 5, 2024 |
| Gilt für | Portal for ArcGIS |
| Gefunden in Version | 10.6.1 |
| Betriebssystem | Windows OS |
| Betriebssystemversion | 2012 R2 |
| Status | Known Limit
Nach Überprüfung durch das Entwicklungsteam wurde festgestellt, dass dieses Problem im Zusammenhang mit einer bekannten Einschränkung der Software steht, die außerhalb der Kontrolle von Esri liegt. Weitere Erläuterungen finden Sie ggf. im Abschnitt "Zusätzliche Informationen" des jeweiligen Problems.
|
Zusätzliche Informationen
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.
Schritte zur Reproduzierung