Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide—528593-005
1-30
NonStop SQL/MX Release 2.0 (G06.23 and G06.24)
•
If you modify or create new SQL/MP aliases, defaults, or stored procedures in Java
(SPJs) in the SQL/MX Release 2.0 environment, there are no automated tools for
moving the associated SQL/MX metadata back to SQL/MP metadata tables.
Moving metadata will require you to execute SQLCI 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.
•
If you fall back to a database environment that does not support multienvironment
SQL modules, any and all locally-placed modules must be converted to globally-
placed before you fall back. You will be unable to fall back successfully if a naming
conflict exists between locally-placed or globally-placed modules. For more
information, see the SQL/MX Installation and Management Guide.
•
Before migrating to SQL/MX Release 2.0, HP recommends that you install one of
these DP2 fallback SPRs on the Release 1.8 system and test it sufficiently for
production use:
°
T9053AOY, if the system uses the online disk remirror feature
°
T9053AOZ, if the node does not use the online disk remirror feature
Then you can migrate to G06.24. If a fallback becomes necessary at a later time,
you can fall back to the tested environment. For the steps to fall back from
SQL/MX Release 2.0, see the SQL/MX Installation and Management Guide.
•
You should remove all SQL/MX Release 2.0 objects and their resource forks
before attempting to fall back. SQL/MX objects are difficult to remove from a
system with an RVU earlier than G06.23. Typically, you use the MXCI DROP
command to drop all SQL/MX Release 2.0 objects. If you encounter problems
using MXCI to drop SQL/MX Release 2.0 objects, you can use the mxtool GOAWAY
command instead. (GOAWAY is an OSS command line utility.) For information about
MXCI and mxtool commands, see the SQL/MX Reference Manual. After you fall
back, the SQL/MX GOAWAY utility will not be available and SQL/MX objects will be
much more difficult to remove.
•
After falling back, if you have to remove any residual SQL/MX objects:
1. Use the FUP INFO command to locate any SQL/MX files remaining on the
system. Because SQL/MX objects reside in subvolumes that begin with the
letters ZSD, use this command to find them:
1>FUP INFO $*.ZSD*.*
2. Use the DELETE command of the DIRCHECK disk utility to delete the files.
For example:
Note. Note that a system load is required to install the DP2 fallback SPR.