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

Falling Back From NonStop SQL/MX Release 2.1 or
Release 2.0
HP NonStop SQL/MX Installation and Management Guide—523723-004
A-8
Recompile Release 1.8 Applications
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. NonStop 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
The mxinit script creates the PROCS and PARAMS tables, the MPALIAS and
DEFAULTS tables, and ODBC tables (ZONAM2ID, ZODS, ZODT, ZOAS2DS, ZORES,
ZOENV) in the same subvolume as the system catalog. These tables get registered in
the system catalog.
mxinit creates a link for MXCI from /usr/bin/ to /usr/tandem/sqlmx/bin/ so
you can enter commands without typing in the full path. For more information about
installing and configuring NonStop ODBC/MX and starting the NonStop ODBC/MX
server, see the ODBC/MX Driver for Windows.
Recompile Release 1.8 Applications
If you recompiled Release 1.8 applications for Release 2.1 or Release 2.0, you must
recompile them for Release 1.8. For more information, see the SQL/MX Reference
Manual for the RVU to which you are falling back.
Falling Back to Non-SQL/MX Environments
Falling back to a non-SQL/MX database environment does not require a return to a
previous RVU. Release 2.1 or Release 2.0 can coexist on a system node with both the
SQL/MP and the Enscribe database environments. Overviews of both these fallback
scenarios are presented next, but neither is discussed in detail in this appendix.
Falling Back to NonStop SQL/MP
NonStop SQL/MP and NonStop SQL/MX can coexist on a NonStop system. Because
these products can coexist and because NonStop SQL/MP continues to be distributed
on each RVU of the NonStop system, falling back to NonStop SQL/MP from Release
2.x does not require that you reinstall a previous RVU. To fall back, you need only:
1. Drop Release 2.1 or Release 2.0 Objects on page A-4.
2. Stop using NonStop SQL/MX.