SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

NOTE: NonStop SQL/MX additionally restricts system-generated names by excluding vowels to
prevent names containing actual words that could be unexpected or misleading.
SQL/MX Subvolume Naming Guidelines
• The subvolume name must begin with the letters ZSD, followed by a letter, not a digit (for
example, ZSDa, not ZSD2).
• The subvolume name must be exactly eight characters long.
• All Guardian files representing data in a particular schema must have the same subvolume
name regardless of the volume on which they reside. This subvolume name must match the
subvolume name indicated in the SCHEMA_SUBVOLUME column of the system schema table
NONSTOP_SQLMX_system-name.SYSTEM_SCHEMA.SCHEMATA.
• For RDF database creation, if you explicitly specify the subvolume that is already in use by
the primary database, use the REPEAT USE ALLOWED clause to avoid receiving an error
when executing the CREATE SCHEMA statement.
Examples of valid SQL/MX subvolume names are:
• ZSDBMM3K
• ZSDADMM8
The REPEAT USE ALLOWED clause of CREATE SCHEMA specifies that NonStop SQL/MX allow
subvolume names to be reused. If the subvolume name is in already in use, the schema is created
anyway and a warning is issued. If you omit this clause, the subvolume name you enter must not
be in use by any other schema. If the subvolume name has been used for another schema, an error
is generated. For more information, see the “Using the Subvolume Option in the CREATE SCHEMA
Statement” (page 75).
For more information, see the SQL/MX Reference Manual.
SQL/MX Data File Naming Guidelines
• The file name must end with the digits “00” (zero zero).
• The file name must be exactly eight characters long.
• The file name must match the designated schema subvolume name for the schema in which
the object is being created. Otherwise, an error is generated.
Examples of valid names for SQL/MX files are:
• WDE6TI00
• HEPQTI00
• SS8BSI00
For more information, see the SQL/MX Reference Manual.
Resource Forks
NonStop SQL/MX maintains substantial information about data files in companion files known as
resource forks. Resource forks are located in the same volume and subvolume as data files and
have the same name as their corresponding data file, with the final “0” (zero) changed to “1”
(one).
74 Creating an SQL/MX Database