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-4
NonStop ODBC/MX Server Configuration Issues
these changes after falling back to Release 1.8, you must manually make
equivalent changes to the Release 1.8 metadata tables after falling back.
NonStop ODBC/MX Server Configuration Issues
Because the NonStop ODBC/MX Server configuration is stored in different tables, you
do not have to create the tables after fallback. After you have reinstalled a previous
RVU, however, you must propagate the NonStop ODBC/MX module files from
T7970PAX and use the Windows NonStop Software Manager to change the MXCS
configuration tables as required. For more information, see:
•
SQL/MX Connectivity Service Administrative Command Reference
•
ODBC Server Installation and Management Manual
NonStop ODBC/MX Driver Configuration Issues
If necessary, reinstall the previous NonStop ODBC/MX driver from the ZMXODBC
subvolume after fallback. If you migrated client data sources, you must remove the
migrated data sources and create new data sources by using the reinstalled driver. For
more information, see the ODBC/MX Driver for Windows.
Falling Back From Release 2.1 or Release 2.0
to Release 1.8
The basic tasks for falling back from Release 2.1 or Release 2.0 to Release 1.8 are:
1. Drop Release 2.1 or Release 2.0 Objects on page A-4
2. Load a Previous RVU on page A-6
3. Drop Remaining Release 2.1 or Release 2.0 Objects on page A-6
4. Install Compatible Versions of Independent Products on page A-7
5. Start TMF on page A-7
6. Fall Back SQL/MX Applications and Their User Modules From Release 2.1 or
Release 2.0 on page A-7
7. Initialize Release 1.8 (Optional) on page A-7
8. Recompile Release 1.8 Applications on page A-8
Drop Release 2.1 or Release 2.0 Objects
1. Identify and drop all Release 2.1 or Release 2.0 objects, including both user tables
and system metadata tables.
Section 8, Querying SQL/MX Metadata describes how to query system metadata
to determine the complete list of Release 2.1 or Release 2.0 schemas in your
system. Using this information, you can use the MXCI DROP command to drop