The services file (located in /vardir/data subdirectory) keeps track of which processes need to remain stopped when sp_cop is launched and if the file is removed, then a new one will be created upon restart of sp_cop and the default behavior of all child processes will be that they will launch once sp_cop comes up. This can have serious implications if a process was intended to be kept in a stopped state but by renaming the services file, the process is started upon restart of Shareplex. For example, typically in a high availability replication the Export process is kept in a stopped state on secondary and if renaming the services file and then starting sp_cop on secondary, the Export process will be started once sp_cop comes up. If there are any messages in Export queue, they will be inadvertently sent to the primary.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center