To ensure Oracle Rdb database security and integrity, a Unique
    Identifier has been added to the database root file and the
    database storage area file and storage area snapshot file
    headers. The Unique Identifier in the root file must match the
    Unique Identifier in the storage area file headers or a storage
    area cannot be accessed from the database root.

    The Unique Identifier values are displayed both in VMS date
    format surrounded by quotes and as a hexadecimal number
    surrounded by parentheses. The values displayed are the Unique
    Identifier values for the current RMU/ALTER session. The Unique
    Identifier values will not be written to the root or storage area
    files until the user ends the current session with the RMU/ALTER
    "COMMIT" command. If the user ends the current session with the
    RMU/ALTER "ROLLBACK" command, the Unique Identifier values will
    not be written to the root or storage area files and the Unique
    Identifier values in effect at the start of the session just
    ended will be restored for the new session. Any Unique Identifier
    values that have been changed during the current session will be
    displayed as "(marked)" before they are committed or rolled back.

    To execute the DISPLAY or DEPOSIT ROOT command, the user must
    be attached to the database which the root and areas belong to,
    either by specifying the database name when issuing the RMU/ALTER
    command or by executing the "ATTACH" command from the "RdbALTER>"
    prompt.