SQL/MX 3.1 Reference Manual (H06.23+, J06.12+)

SQL/MX Utilities
HP NonStop SQL/MX Release 3.1 Reference Manual—663850-001
5-87
Renaming Guardian location of partitions of tables or
indexes
primary extent and that of secondary extents separately. If you do not specify
EXTENT, MODIFY uses the extent size values of the largest partition.
See EXTENT on page 8-6 and MAXEXTENTS on page 8-7.
Renaming Guardian location of partitions of tables or indexes
You can use MODIFY to rename the Guardian filename part at one or more locations
of an existing table or index. However, you cannot rename the system, volume, or
subvolume part of the Guardian location.
[[catalog.]schema.]object
is the ANSI name of the object. The object can either be a table or an index,
depending on the keyword TABLE or INDEX. If you do not specify the schema and
the catalog name, the default catalog and schema names are used.
rename-spec
specifies how source files will be renamed to the corresponding target files. The
operation uses rename-spec to rename one or more source files to the
corresponding target file names.
The MODIFY form to rename Guardian location of partitions of a table or an
index:
MODIFY { TABLE | INDEX } [[catalog.]schema.]object
RENAME [ WHERE ] LOCATION
{ rename-spec | ( rename-spec [, rename-spec ] ... ) }
[OUTFILE oss-file [CLEAR]]
rename-spec is:
{ simple-rename-spec
| pattern-map-spec }
simple-rename-spec is: location TO file-name-part
pattern-map-spec is: pattern MAP NAMES TO target-map }
location is:
The Guardian file name of a source location to rename.
file-name-part is:
The Guardian file name part to rename the source location
to.
pattern is:
Standard Guardian file name pattern.
target-map is:
an 8-character specification of how matching source file
names will be renamed. It consists of letters, digits, and
(?) characters.