HP NonStop G-Series - Manual (Page 54)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-019
3-16
Changing File Ownership
Changing File Ownership
By default, the ownership of each synchronized file is preserved. You may specify the
OWNER option to give the files to any user ID, including your own user ID.
Note that for OSS files, only SUPER.SUPER can change the ownership of a file on the
destination. Moreover, using the OWNER option does not change the group id of the
file. To change the group id, the user must also specify the OWNERGROUP option.
Synchronizing Based on Ownership
By default, source files owned by all user can be candidates for synchronization,
provided the security settings allow it.
You can restrict the source file set to files owned by a specific user ID, by using the
FROMOWNER option. Files owned by other users are skipped.
Note that for OSS, if a directory that is not owned by the FROMOWNER user ID is not
synchronized, even if it contains files or subdirectories that are owned by the
FROMOWNER user ID.
Synchronizing based on REDEFINITION timestamp
By default, AutoSYNC compares source and destination MODIFICATION timestamps
to decide if the destination table needs to be replaced.
Users might want to synchronize tables after performing certain types of DDL
operations on SQL tables, such as adding a column or a partition or creating an index.
However these operations leave the MODIFICATION timestamp unchanged and
update only the REDEFINITION timestamp, causing AutoSYNC to overlook the
change that occurred on the table.
To synchronize tables based on differences in the REDEFINITION timestamp, use the
SQLREDEF option. AutoSYNC then compares the source and destination
REDEFINITION timestamps of the table, in addition to the MODIFICATION
timestamps, to decide if a table requires synchronization.
Note that a SQL index is synchronized automatically with the primary partition of the
base table. If the redefinition date of an index in the source subvolume is newer than in
the destination subvolume, but the primary source partition is older than the primary
destination partition, the index will not be synchronized.
Synchronizing based on Binder or Linker timestamp
Certain operations performed on an object file cause the MODIFICATION timestamp of
the file to change but do not alter the file in ways that require synchronization. For
example, SQL compiling a program on the source system changes the modification
timestamp of the object file but does not require the replacement of the file on the
destination. This is reflected by the fact that the binder or linker timestamp of the object
file is unchanged by the SQLCOMP utility.