The following restrictions apply to administrative VOB hierarchies:
- A VOB can have at most one AdminVOB hyperlink pointing to an administrative
VOB. The mkhlink command prevents the creation of a second AdminVOB hyperlink
from a VOB.
- Local types may not eclipse (have the same type and name as) global types.
An attempt to add a VOB to an administrative VOB hierarchy will fail if the
VOB defines a local type that would eclipse one already defined as global
in the hierarchy. Use the –acquire option to mkhlink to
force the local type to become an instance of the global type. See the mkhlink reference
page for more information.
- All VOBs in a hierarchy should be backed up and restored as a group. If
they are not, VOBs in one part of the hierarchy may hold instances of types
that are not defined in their administrative VOB (because the administrative
VOB was restored from a backup taken before the type was created). For more
information, see Restoring one or more members of a set of related databases.
- If the administrative VOBs from which an ordinary VOB derives a type object
definition is not accessible, instances of that type cannot be created or
manipulated in the ordinary VOB. For more information, see If an administrative VOB becomes unavailable.