The Replica Schema Change process adds a new empty field when a field is renamed.
Last Published: July 27, 2017ArcSDE/Enterprise Geodatabase
Bug ID Number
July 29, 2015
January 28, 2021
Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
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.