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-2
Preinstallation Tasks
superseding SPR) on the Release 1.8 system and test it sufficiently for production
use:
°
T9053APO, if the system uses the online disk remirror feature
°
T9053APG, if the node does not use the online disk remirror feature
When you migrate to the G06.23 or later RVU, if a fallback becomes necessary at
a later time, you can fall back to the tested environment. For information about
falling back from Release 2.1 or Release 2.0, see Appendix A, Falling Back From
NonStop SQL/MX Release 2.1 or Release 2.0.
Note that a system load is required to install the fallback SPR.
3. Rename or save a copy of the OSS installation script for the Release 1.8 sample
database. This step is optional.
The sample database provided with Release 2.1 or Release 2.0 uses SQL/MX
tables. If you are migrating a Release 1.8 node to Release 2.1 or Release 2.0, and
you need a sample database consisting of SQL/MP tables, rename or make a copy
of the setmxdb script that generates the Release 1.8 sample database.
Renaming setmxdb in its default OSS directory (/usr/tandem/sqlmx/bin/) or
making a copy of the script to a different directory is necessary because the
setmxdb file in the default location is overwritten during installation of Release 2.1
or Release 2.0.
This OSS command renames setmxdb in its current location:
mv setmxdb setmxdb.r18
Before using the Release 1.8 setmxdb in a Release 2.1 or Release 2.0
environment, see the considerations in the SQL/MX Quick Start.
4. Confirm that TMF is configured and running on the system node where you will
install NonStop SQL/MX. See the guidelines for starting TMF in Section 2,
Preparing to Install NonStop SQL/MX. Also see the TMF Planning and
Configuration Guide for TMF installation guidelines.
TMF is required for SQL compilation and for execution of all SQL/MX utilities and
all DDL and DML statements that require TMF transactions. Note that all SQL/MX
objects must reside on volumes audited by TMF. SQL/MX program files need not
reside on audited volumes.
5. If you want to run FCHECK independently of the InstallSqlmx script, do it
before you run InstallSqlmx in Step 7 of Installing NonStop SQL/MX on
page 3-3. If a large number of disk drives are attached to the local node on your
system, the FCHECK portion of InstallSqlmx can take a long time to complete.
To run FCHECK independently of InstallSqlmx, issue the command for the
volumes you want to check:
FCHECK -MXCHECK -VOL $volume