HP Integrity NonStop H-Series - Manual (Page 49)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-021
3-9
SQL Collations
input list, because the view did not change. On the destination, the view is dropped
when RESTORE drops and replaces the referenced table, but the view is not
recreated. The view is eventually replaced at the next synchronization.
When a shorthand view is synchronized, it is marked as corrupted if a table it
references is not present on the destination system. This can create a problem if the
view name alphabetically precedes the name(s) of the base tables.
SQL Collations
SQL collations are backed up as a combination of a collation file label and an
immediately-following temporary edit file. AutoSYNC treats this pair of items as a
single unit for recovery, OPENUPDATE and trigger processing.
Partitioned Files and Tables
AutoSYNC synchronizes entire partitioned files and tables when the primary partition is
specified in the source file set.
PARTONLY synchronization of single partitions is not supported. An error message is
generated if a secondary partition is specifically selected to be synchronized.
When selecting a partitioned file for synchronization, AutoSYNC retrieves the
aggregate modification time to compare source and destination modification times. If
any partition of the source file is newer than the equivalent partition of the destination
file, the entire partitioned file is synchronized.
If source partitions are synchronized to identical volume names on the destination,
specify the synchronization as:
Identical name mapping is implied and no MAPNAMES file is required.
If some of the source partition volume names are different on the destination, use the
MAPNAMES option to describe the mapping of the secondary partition names.
Changing Primary Partition Mapping
AutoSYNC does not use MAPNAMES directly. The entries are only used by the
RESTORE MAP NAMES option. As a consequence, you cannot change the mapping
of the primary partition (or any other) file name using an entry in the mapnames-file.
For example, if you want to synchronize the primary partition $DATA01 of a partition file
to $BACK01 on the destination, the mapping of the volume names must appear in the
SYNC $DATA.DB.PARTFILE TO \.*.*.*;
Note. To avoid errors, it is recommended that the mapnames file contain an entry for
every secondary partition volume, even for the secondary partitions with names that
are identical on the source and destination.