NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
D-74
Considerations—DUP
Rules for Enscribe files
•
If an Enscribe file references its alternate-key files, DUP modifies such
references in the new file based on the MAP NAME option you specify. If you
omit the MAP NAME option, DUP does not modify the references.
•
To duplicate an alternate-key file, you must specify it explicitly or implicitly
(through wild-card characters) in source-fileset-list.
•
DUP does not duplicate the DDL record definition of an Enscribe file.
•
Target specification
With some minor exceptions, a target-fileset specification is equivalent to
the following MAP NAME option:
MAP NAME *.*.* TO target-fileset
The following are some guidelines for specifying target-fileset or MAP
NAME options:
°
If you want new objects to have the same unqualified object names as the
original objects, specify target-fileset with an asterisk for the object part
of the Guardian name, using specific names only for the parts of the name that
are to be different, for example:
DUP $VOL1.*.*, $NWVOL.*.*; <--To new volume
DUP $VOL1.SUBV1.*, *.NWSUBV.*; <--To new subvolume
DUP $VOL1.SUBV1.*, $NWVOL.NWSUBV.*; <--To new volume and
new subvolume
°
If you want to give new unqualified names to the new objects or to map more
than one name at the same level (node, volume, or subvolume) to a different
name, you must use MAP NAME. For example, the following command
duplicates the PERSNL and SALES subvolumes to the same volume, but
different subvolumes:
DUP ($VOL1.PERSNL.* FROM CATALOG $VOL1.PERSNL,
$VOL1.SALES.* FROM CATALOG $VOL1.SALES),
MAP NAME ($VOL1.PERSNL.* TO $VOL1.NWPERS.*,
$VOL1.SALES.* TO $VOL1.NWSALES.*);
°
Do not map a table to a specific table name if you want its dependent objects
(protection views and indexes) duplicated, for example:
DUP PERSNL.EMPLOYEE, TESTSUBV.* <---Use this
DUP PERSNL.EMPLOYEE, TESTSUBV.EMPLOYEE <---Not this
°
Be careful that you define the MAP NAMES and CATALOGS parameters
correctly for dependent tables, indexes, views, and programs. An incorrect
mapping scheme can leave the objects invalid or cause the RESTORE process to
fail.