laptop and a wrench


The Replica Schema Change process adds a new empty field when a field is renamed.

Last Published: July 27, 2017 ArcSDE/Enterprise Geodatabase
Bug ID Number BUG-000089425
SubmittedJuly 29, 2015
Last ModifiedJanuary 28, 2021
Applies toArcSDE/Enterprise Geodatabase
Version found10.2
StatusWill Not Be Addressed

Additional Information

I actually don’t think it is a bug as our system is designed to work this way. Replication matches data by field name so if you change the field name, it won’t be able to match it. The behavior described with the schema changes is also expected and I think correct. We add fields that do not exist in the target with the schema differences tools by default but we do not delete fields by default – users need to choose to delete the field and thus make a conscience decision to do so. Don’ t see that as a data loss issue.

Steps to Reproduce

Bug ID: BUG-000089425


  • ArcSDE/Enterprise Geodatabase

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Discover more on this topic