HP NonStop G-Series - Manual (Page 89)

File Relocation Facility
HP NonStop Storage Management Foundation User's Guide—523562-008
5-3
Aborting Relocation Operations
issued while one is in progress is rejected with an FESMSRELOCINPROGRESS
error.

File information reports. SMF supports file information requests against files being
relocated at both the source and target destinations.
When relocating files on a virtual disk, you can use the FUP SOURCEDATE option to
retain the original timestamp. For more information, see the File Utility Program (FUP)
Reference Manual.
Aborting Relocation Operations
A relocation operation can be canceled by stopping the requesting process (FUP or the
user application) that initiated the operation. When this is done, the file relocation
operation is aborted.
If the requesting process that initiated the relocation operation is stopped after the file
relocation has finished, but before the requesting process has been notified of the
completion, the file relocation is not aborted. In this case, an EMS event is emitted
indicating the relocation operation finished.
A relocation operation is also aborted if the requesting process is running in a
processor that goes down.
Special Considerations for SQL Files
The information in this subsection pertains to the relocation of SQL files: that is, base
tables, indexes, views, collations, programs, and catalogs.
User Interfaces
The user interface for relocating a SQL file is either FUP or the user application
program. There is no separate interface for executing relocation operations from the
SQL conversational interface (SQLCI). However, FUP can be executed from within
SQLCI by typing the desired FUP command followed by a semicolon at the SQLCI
prompt. Alternatively, you can enter an interactive FUP session by typing FUP followed
by a semicolon (that is, FUP;) at the SQLCI command line.
Protection Views
SQL protection views must reside on the same physical disk volume as the SQL base
table on which they are defined. As such, protection views cannot be relocated
independently: they are implicitly relocated whenever a base table is moved.
A file relocation operation does not finish until a base table and all protection views
defined on it are on the same volume. If an error condition occurs before the entire set
has been relocated, the relocate operation is backed out and no files are moved.