OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
40.7 Restoring a Duplicate Master
This section describes how to recover from a very unusual problem. Do not use the
methods described here to resolve the problem unless it is absolutely necessary.
Occasionally the replica that you want to be the master will have a master sequence
number that is lower than (or equal to) another master sequence number in the system.
When the master detects that its master sequence number is lower than another one in the
system, it marks itself as a duplicate master and its process exits. Each time you start the
master replica, it will notice that it has been deemed a duplicate master, and its process
will again exit.
To force this ‘‘duplicate’’ master to become the master and not exit, restart its secd
process with the -master_seqno option in the following format:
secd -master_seqno new_master_seqno
where new_master_seqno is a new master sequence number to assign to the replica.
Make this number one digit higher than the highest master sequence number in the
system.
Use the dcecp registry show -replica command for each replica to find the highest
master sequence number.
40.8 Adopting Registry Orphans
Although dcecp displays object names and you identify registry objects by name, the
DCE Security Service uses UUIDs to identify objects internally. When you create a
registry object, the DCE Security Service automatically sets up an association between
the object name and a UUID that it uses to identify the object. When you delete registry
objects, you delete the association between the registry object and the UUID that
identifies the object.
Orphans are objects owned by UUIDs that are not associated with a principal or group
because the principal or group has been deleted. For example, if you delete a principal
from the registry, you also delete the association between the name used to identify the
principal externally and the UUID used to identify the principal internally. Any objects
(files, programs) owned by the deleted principal are now owned internally by a UUID no
longer associated with a principal. If no other principal, group, or organization has
access rights to the object, the object cannot be accessed at all and is now an orphan.
To solve this problem, you can use the dcecp principal create, group create, and org
create commands with the -uuid option to create a principal, group, or organization with
the same UUID as the UUID that owns the orphaned object and thus ‘‘adopt’’ the
orphaned object.
Note: When you create a new registry object, you have no way of specifying the
UUID associated with the object; therefore, you cannot simply add a new
40 − 8 Tandem Computers Incorporated 124243