SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual523352-013
D-78
Examples—DUP
*.*.* TO *.*.OLDPARTS )
CATALOGS (
\REMOTE.$VOL1.CAT FOR \REMOTE.*.*.*,
$VOL1.CAT FOR *.*.* );
This 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.*.*.*
);
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. For information about
performing dumps, see the TMF Operations and Recovery Guide.
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.
If a DUP operation fails after correctly duplicating some objects and files, restarting
the operation from the beginning causes errors unless the original operation used
the TARGET PURGE option. Determine the objects and files that were duplicated
and consider the appropriate setting for the TARGET option before you restart a
partially successful DUP operation.
If an unusual situation occurs while a collation is being duplicated, two temporary
files (ZZCLnnnn and ZZCSnnnn, where nnnn is a number) might be left in the
same subvolume as the source collation. You can purge both of these files with the
PURGE command.
Examples—DUP
This example copies table $VOL1.PERSNL.JOB to subvolume
$NEWVOL.PERSNL and gives it the same name as the original table. The new