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-3
Planning to Fall Back Other Nodes in the Network
•
You recompiled user modules only.
Applications that you compiled with the SQL/MX Release 2.x compiler need to be
recompiled with the SQL/MX Release 1.8 compiler after fallback.
•
You made changes to metadata tables.
If you changed any MPALIAS, DEFAULTS, PROCS, PARAMS, or ODBC/MX
metadata tables (for example, to add a new SQL/MP alias) and you want to retain
these changes after falling back to SQL/MX Release 1.8, you must manually make
equivalent changes to the SQL/MX Release 1.8 metadata tables after falling back.
To move changed metadata, execute MXCI commands, such as CREATE
MPALIAS, CREATE PROCEDURE, and INSERT INTO DEFAULTS, after
reinstalling SQL/MX Release 1.8. For information about these commands, see the
SQL/MX Reference Manual.
Planning to Fall Back Other Nodes in the Network
If you fall back a node to SQL/MX Release 1.8, SQL/MX applications on the
downgraded node will not interoperate with SQL/MX Release 2.x nodes in the same
Expand network.
Steps for Falling Back From SQL/MX Release
2.x to SQL/MX Release 1.8
The basic tasks for falling back from SQL/MX Release 2.x to SQL/MX Release 1.8 are:
1. Drop SQL/MX Objects
on page 8-4
2. Load a Previous RVU
on page 8-5
3. Install Compatible Versions of Independent Products
on page 8-6
4. Start TMF
on page 8-6
5. Install SQL/MX Release 1.8
on page 8-6
6. Drop Remaining SQL/MX Objects
on page 8-6
7. Remove the InstallSqlmx Script
on page 8-7
8. Initialize SQL/MX Release 1.8 (Optional)
on page 8-7
9. Reconfigure the NonStop ODBC/MX Server and Driver
on page 8-8
10. Fall Back SQL/MX Release 2.x Applications and User Modules to SQL/MX
Release 1.8 on page 8-8