NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
D-76
Considerations—DUP
duplicated to the same volumes and subvolumes as the original table, but with
different names.
DUP $VOL1.TESTSUBV.PARTS,
MAP NAMES (
\REMOTE.*.*.* TO \REMOTE.*.*.OLDPARTS,
*.*.* TO *.*.OLDPARTS )
CATALOGS (
\REMOTE.$VOL1.CAT FOR \REMOTE.*.*.*,
$VOL1.CAT FOR *.*.* );
The following command does not work as expected because DUP changes the
\LOCAL.*.*.* part of the MAP NAMES specification to *.*.*. Then, because
the local specification is given first, both local and remote partition names map
to \LOCAL.*.*.OLDPARTS.
DUP $VOL1.TESTSUBV.PARTS,
MAP NAMES (
\LOCAL.*.*.* TO \LOCAL.*.*.OLDPARTS,
\REMOTE1.*.*.* TO \REMOTE1.*.*.OLDPARTS
)
CATALOGS (
\LOCAL.$VOL1.CAT FOR \LOCAL.*.*.*,
\REMOTE1.$VOL1.CAT FOR \REMOTE1.*.*.*
);
•
Transactions, breaks, and failures
You cannot execute the DUP command within a user-defined TMF transaction.
Because it is not possible to duplicate data to an audited table, DUP creates
nonaudited tables. If the original table is audited, DUP sets the new table's AUDIT
attribute to ON after the DUP operation finishes.
If you want to be able to perform a TMF file recovery operation, make online dumps
of new audited objects and files after the DUP. See the NonStop TM/MP Operations
and Recovery Guide for information about performing dumps.
You can press the Break key to interrupt a DUP operation. If you press the Break
key, the operation stops. Items already duplicated remain, but the item being
duplicated when you pressed Break can be left in an invalid state.
If DUP fails or if you press the Break key, the corrupt flag is set for the last object
operated on before the failure. Run FILEINFO on all the target objects to find the
corrupt objects, then delete the objects before restarting DUP.