Snapshot=(Allocation=n,File=file-spec)

    If you specify the Allocation parameter, specifies the snapshot
    file allocation size in n pages for a restored area. If you
    specify the File parameter, specifies a new snapshot file
    location for the restored storage area to which it is applied.
    You can specify the Allocation parameter only, the File parameter
    only, or both parameters; however, if you specify the Snapshots
    qualifier, you must specify at least one parameter.

    This is one of the commands used to alter the parameters of the
    restored database from those defined at the time of the database
    backup. Others are /DIRECTORY, /ROOT and /FILE.

    See the Usage Notes for information on how this qualifier
    interacts with the Root, File, and Directory qualifiers.

    The Shapshot qualifier is a positional qualifier. It can be used
    locally or globally, depending on where the qualifier is placed
    on the command line. See Examples 22 and 23.

    To save read/write disk space, you can specify that less space be
    allocated for the storage area's .snp file when it remains as a
    read/write file on a read/write disk. If the keyword Allocation
    is omitted, the original allocation is used. This qualifier is
    not valid for single-file databases.

    You cannot specify an .snp file name for a single-file database.
    When you create an .snp file for a single-file database, Oracle
    Rdb does not store the file specification of the .snp file.
    Instead, it uses the file specification of the database root
    (.rdb) file to determine the file specification of the .snp file.

    If you want to place the .snp file on a different device or
    directory, Oracle Corporation recommends that you create a
    multifile database. However, you can work around the 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 database with an .snp file on a different device
    or directory, 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 .snp 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 (.snp) file to the second disk.
    $ COPY USER$DISK1:[DATABASE]TEST.SNP -
    _$ USER$DISK2:[SNAPSHOT]TEST.SNP
    $ !
    $ ! Delete the snapshot (.snp) file from the original disk.
    $ DELETE USER$DISK1:[DATABASE]TEST.SNP;