o  To use the RMU Move_Area command for a database, you must have
       the RMU$MOVE privilege in the root file access control list
       (ACL) for the database or have the OpenVMS SYSPRV or BYPASS
       privilege.

    o  You cannot disable extensions of snapshot (.snp) files.

    o  The parameter (file and area) qualifiers for the RMU Move_Area
       command have positional semantics. See the Command_Qualifiers
       help entry for more information on parameter qualifiers.

    o  The RMU Move_Area command provides four qualifiers, Directory,
       Root, File, and Snapshots, that allow you to specify the
       target for the moved files. The target can be just a
       directory, just a file name, or a directory and file name.

       If you use all or some of these four qualifiers, apply them as
       follows:

       -  If you want to move the database root, use the Root
          qualifier to indicate the target for the moved database
          root file.

       -  Use local application of the File qualifier to specify the
          target for the moved storage area or areas.

       -  Use local application of the Snapshots qualifier to specify
          the target for the moved snapshot file or files.

       -  Use the Directory qualifier to specify a default target
          directory. The default target directory is the directory to
          which all storage area and snapshot files not qualified
          with the File or Snapshot qualifier are moved. It is
          also the default directory for files qualified with the
          Root, File, or Snapshot qualifier if the target for these
          qualifiers does not include a directory specification.

       Note the following when using these qualifiers:

       -  Global application of the File qualifier when the target
          specification includes a file name causes Oracle RMU
          to move all of the specified storage areas to different
          versions of the same file name. This creates a database
          that is difficult to manage.

       -  Global application of the Snapshot qualifier when the
          target specification includes a file name causes Oracle RMU
          to move all of the specified snapshot files to different
          versions of the same file name. This creates a database
          that is difficult to manage.

       -  Specifying a file name or extension with the Directory
          qualifier is permitted, but causes Oracle RMU to move all
          of the specified files (except those specified with the
          File or Root qualifier) to different versions of the same
          file name. Again, this creates a database that is difficult
          to manage.

       See Example 6.

    o  You must specify the Root qualifier when you use the RMU Move_
       Area command on a single-file database. If you omit the Root
       qualifier, you receive an error message. If you want to place
       the snapshot file for a single-file database on a different
       device or directory from the root file, Oracle Corporation
       recommends that you create a multifile database. However,
       you can work around this restriction by defining a search
       list for a concealed logical name. (However, do not use a
       nonconcealed rooted logical name to define database files; a
       database created with a non-concealed rooted logical name can
       be backed up, but may not restore correctly when you attempt
       to restore the files to a new directory.)

       To create a single-file database with a snapshot file on a
       different device or directory from the root file, define a
       search list by using a concealed logical name. Specify the
       location of the root file as the first item in the search
       list. When you create the database, use the logical name for
       the directory specification. Then, copy the snapshot file
       to the second device. The following example demonstrates the
       workaround:

       $ ! Define a concealed logical name.
       $ DEFINE /TRANS=CONCEALED/SYSTEM TESTDB USER$DISK1:[DATABASE], -
       _$ USER$DISK2:[SNAPSHOT]
       $
       $ SQL
       SQL> ! Create the database.
       SQL> !
       SQL> CREATE DATABASE FILENAME  TESTDB:TEST;
       SQL> EXIT
       $ !
       $ ! Copy the snapshot file to the second disk.
       $ COPY USER$DISK1:[DATABASE]TEST.SNP USER$DISK2:[SNAPSHOT]TEST.SNP
       $ !
       $ ! Delete the snapshot file from the original disk.
       $ DELETE USER$DISK1:[DATABASE]TEST.SNP;

    o  There are no restrictions on the use of the Nospams qualifier
       option with mixed page format storage areas, but the use of
       the Nospams qualifier typically causes severe performance
       degradation. The Nospams qualifier is useful only where
       updates are rare and batched, and access is primarily by
       database key (dbkey).