Applying supported DDL on replicating tables in an active-active replication environment does not need any special considerations and this solution delves on the reason behind this.
General information.
When applying supported DDL on one node in a master-master replication environment, the Capture process on the secondary nodes will not pick up the DDLs to send them back to the first node. The reason behind this is that Capture process ignores the DDL or DML done by Shareplex user (Post process). The only exception is the setting of the parameter SP_OCT_REPLICATE_POSTER to 1. But this is only done in cascading replication and is, therefore, not applicable in our situation. So there is no loop back of the DDL back to the primary node.
The only thing that needs to be taken care of is to apply the supported DDL on one node and let Shareplex carry that change and apply it to the remaining nodes in a peer-to-peer environment. It is not advisable to try applying that DDL on other nodes separately.
