SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
D-71
DUP Command
An asterisk (*) in the fileset specification indicates that the portion of the name
in which the asterisk appears should be the same as the corresponding portion
of the name of the object or file being duplicated. For example,
MAP NAMES $WHS2.INVENT.PARTLOC TO $TEST.*.*
specifies that the new table that duplicates $WHS2.INVENT.PARTLOC is to be
$TEST.INVENT.PARTLOC.
(The meaning of the asterisk differs from the usual meaning of an asterisk in a
fileset specification. The ? normally allowed in a fileset specification is not
allowed.)
If you specify a list of map-specs and one conflicts with another, DUP uses the
first in the list.
For information about using MAP NAME, see the target-fileset specification
Considerations item on page D-76.
CATALOG[S] { catalog-spec }
{ ( catalog-spec> [, catalog-spec ]...) }
specifies existing catalogs in which the target objects are to be described;
catalog-spec is
catalog-name [ FOR simple-fileset-list ]
catalog-name identifies a catalog on the same node as the objects to hold
the descriptions of the objects.
FOR simple-fileset-list specifies the names and location of the target
objects to be described in the catalog. A fileset within simple-fileset-
list that does not specify a node matches any node. Specifying the local
node for a fileset is equivalent to not specifying any node for the fileset. For
example, if \LOCAL is the local node name, both the node specifications *.*.*
and \LOCAL.*.*.* match all files on all nodes, both local and remote.
If you omit the FOR clause, SQL uses catalog-name as the catalog for all
duplicated objects.
If you omit the CATALOGS option, SQL uses the current default catalog.
COLLATION[S] ( collation-spec [, collation-spec ] ... )
specifies collations to be used by new objects: