SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)
Falling Back to SQL/MX Release 1.8
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
8-7
Remove the InstallSqlmx Script
Remove the InstallSqlmx Script
Delete InstallSqlmx after you fall back from SQL/MX Release 2.x to SQL/MX
Release 1.8. From the SQL/MX Release 1.8 environment, enter this command from
the OSS space:
rm /usr/tandem/sqlmx/bin/InstallSqlmx
Initialize SQL/MX Release 1.8 (Optional)
If necessary, reinitialize your SQL/MX Release 1.8 database environment by running
the
mxinit initialization script from the /usr/tandem/sqlmx/bin directory.
Note that the OSS environment is case-sensitive, so enter the command in the
appropriate case. The
mxinit script will re-create the SQL/MX Release 1.8 metadata
tables for use by SQL/MX if they do not already exist.
1. Log on to the NonStop server by using the super ID (user ID 255,255).
2. Start the OSS shell by entering this command at the TACL prompt:
osh
You are now in the OSS environment. To run mxinit:
a. Change the directory by entering:
cd /usr/tandem/sqlmx/bin
b. Run the mxinit script by entering:
run mxinit [ -noFcheck ]
mxinit determines the location and name of the SQL/MP system catalog. The
-noFcheck option disables FCHECK from being run. By default, FCHECK is run on
all volumes to check for SQL/MP tables with added columns. If a table with an added
column was duplicated, the addedColumn flag might not be carried over to the
duplicated table, resulting in problems. FCHECK correctly sets this flag for tables with
added columns. SQL/MX depends on the addedColumn flag being correctly set in the
label of all SQL/MP tables.
To get help on the
mxinit command, from the /usr/tandem/sqlmx/bin directory,
enter:
mxinit -help
Caution. When you fall back from SQL/MX Release 2.x to SQL/MX Release 1.8, the
InstallSqlmx script remains in the /usr/tandem/sqlmx/bin directory. InstallSqlmx
is not designed to run from the SQL/MX Release 1.8 environment. If you attempt to do so,
error messages are generated, and the SQL/MX installation aborts.
Note. If your SQL/MX Release 1.8 environment is intact (for example, you did not alter or
purge the PROCS, PARAMS, MPALIAS, and DEFAULTS tables), this step is unnecessary.