SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Installing NonStop SQL/MX
HP NonStop SQL/MX Installation and Management Guide—523723-004
3-24
The Phases of InstallSqlmx
Table 3-2. The Phases of InstallSqlmx
Phase Phase Activities
1 InstallSqlmx verifies that the SQL/MX objects were laid down correctly from
the SUT installation. If any required SQL/MX objects are missing from their
default locations, InstallSqlmx notifies the user about the missing objects and
aborts the installation. For file name and default location information, see
Overview of Automatic File Installations
on page 3-6. Also see Locating System
Schema Tables on page 8-15.
2 InstallSqlmx creates an anchor file that contains the location of the SQL/MX
system metadata tables. The anchor file is a simple text file with ASCII tokens
that identifies the volume where system metadata will reside. The file resides in
the Guardian space $SYSTEM.ZSQLMX.MXANCHOR and is assigned a security of
“N---.”
3 InstallSqlmx issues an INITIALIZE SQL statement to initialize NonStop
SQL/MX. If NonStop SQL/MX cannot be successfully initialized, the installation is
aborted and the anchor file is removed. Whether initialization is successful or not,
InstallSqlmx creates the log /usr/tandem/sqlmx/bin/initlog. The
viewable log file initlog contains status information about the SQL/MX
initialization.
The INITIALIZE SQL operation also creates metadata tables for the schema
MXCS_SCHEMA in the system catalog.
InstallSqlmx also implements the national character set specified with the -n
option. The national character set is associated with NCHAR and NATIONAL
CHARACTER types and with N string literals, host variables, and SQL functions
and predicates.
4 InstallSqlmx loads MXCS metadata tables in the MXCS_SCHEMA of the
system catalog with their default values.
After loading MXCS metadata tables, InstallSqlmx creates a log at
/usr/tandem/sqlmx/bin/mxcslog. The viewable log file mxcslog contains
status information about the MXCS initialization operation.
5 InstallSqlmx verifies that the system metadata tables were created in the
volume specified with the -l option of the InstallSqlmx command.
6 If the -nofcheck option is not specified, InstallSqlmx performs FCHECK on
volumes of the local node to locate SQL/MP tables with added columns. If an
SQL/MP table with an added column was duplicated, the addedColumn flag
might not have been carried over to the duplicated table, resulting in problems.
FCHECK correctly sets this flag for SQL/MP tables with added columns. NonStop
SQL/MX depends on the addedColumn flag being set correctly in the label of all
SQL/MP tables.
InstallSqlmx also creates a viewable log,
/usr/tandem/sqlmx/bin/fchecklog, that contains details about the
FCHECK operation.
If a large number of disk drives are attached to the local node, the FCHECK
portion of InstallSqlmx can take a long time to complete. To avoid this delay,
you can run FCHECK before you run InstallSqlmx.