Shareplex does not allow editing of an active config file. When trying to edit one within sp_ctrl, it gives an error "Edit config file is not allowed for an active config file". The question arises as to how Shareplex would behave if someone attempted to edit an active config file outside of sp_ctrl, say using vi editor.
Implications of trying to get around the restrictions of not able to edit an active config file.
If an attempt is made to edit an active config file outside of sp_ctrl, thereby bypassing the restriction imposed by Shareplex, it may result in loss of current activation. This is how it works. If a user attempted to add or remove tables in an active config file this way, then upon the completion of the editing session (when changes to the config file are saved), any new objects added to the config file will need to be locked by Shareplex and if for any reason it is not able to do so, then the currently active config will be deactivated. By the same token any object is removed from the currently active config file, then upon exiting the editing session, Shareplex will attempt to lock that object and failure to do so would result in loss of activation. If the routing information for an object is changed, then the object would still need to be locked, albeit very briefly. Any failure in locking would prove disastrous to the currently active config.
It may be noted that in the above situations if the locking was successful, then there will be no damage done. But the fact that such unintended consequences can occur should be sufficient to deter one from trying this approach. All said it is better to do all editing using sp_ctrl interface so that the best practices are adhered to and all precautions are observed. If wishing to edit an active config file, the only way to do so in sp_ctrl is to make its copy and edit it.