| ## Forcibly Deleting a Slave Replica The procedure described in this topic explains how to forcibly delete a slave replica. Use this drastic method only when the ordinary method of deletion described in Handling Network Reconfigurations fails. To forcibly delete a slave replica, use the dcecp registry delete -force command. This command deletes the slave replica from the master's replica list. The master then propagates the delete request to the other replicas. Since this operation never communicates with the deleted replica, use the -force option only when the replica dies and cannot be restarted. If a forcibly deleted replica continues operation, use the registry destroy command to stop the server and delete its database. You can also simply stop secd (by using the dcecp registry stop command) and delete or rename its database. To forcibly delete a registry replica, issue the registry delete command with the -force option, supplying the name of the registry to delete as an argument. The following sample deletes the replica at /.../giverny.com/subsys/dce/sec/lit_server_2: dcecp> registry delete /.../giverny.com/subsys/dce/sec/lit_server_2 -force dcecp> If the default replica is not the master, dcecp automatically binds to the master. If a forcibly deleted replica continues operation, use the registry destroy command to stop the server and delete its database. When you use the registry destroy command, you must enter the name of the replica that you want to stop. The following example shows the registry destroy command used to delete the replica at /.../giverny.com/subsys/dce/sec/lit_server_2: dcecp> registry destroy /.../giverny.com/subsys/dce/sec/lit_server_2 dcecp> Alternatively, you can simply stop secd (by using the dcecp registry stop command) and destroy the replica by deleting or renaming its database. ##