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-2
Fallback Considerations
Fallback Considerations
•
To ensure you are able to fall back successfully, you must install certain SPRs
before you attempt to fall back. For more information, see these references:
°
Section 3, Installing NonStop SQL/MX
°
G06.nn Release Version Update Compendium
°
Readme file for the RVU to which you would fall back
•
Falling back to a release of NonStop SQL/MX earlier than Release 1.8 is not
supported.
•
To fall back to Release 1.8, you must reinstall a previous RVU and certain versions
of some prerequisite or co-requisite software products.
•
To fall back to an SQL/MP or Enscribe database environment, you need not
reinstall a previous RVU. Both NonStop SQL/MP and Enscribe are included in the
current RVU.
•
If you are migrating to Release 2.1 or Release 2.0 from an SQL/MP database
environment, do not delete an SQL/MP metadata tables until you are sure you will
not need to fall back. Deleting these metadata tables prevents a successful
fallback.
•
Release 2.1 and Release 2.0 applications that you develop prior to fallback are not
usable with previous SQL/MX releases with which Release 2.1 and Release 2.0 do
not interoperate.
•
Applications that you compiled with the Release 2.1 compiler need to be
recompiled with the previous release of the SQL compiler (Release 2.0 or Release
1.8) after fallback.
•
If you fall back to a database environment that does not support multi-environment
(globally placed and locally placed) SQL user modules, you must properly manage
all applications and modules created in the Release 2.1 or Release 2.0
environment when you fall back. For instructions, see Managing Module Files and
Their Applications During Fallback From Release 2.1 or Release 2.0 on
page 11-25.
•
If you are falling back from Release 2.1 or Release 2.0 to a Release 1.8 in a non-
SQL/MX environment, you should remove all Release 2.1 or Release 2.0 objects,
including user tables and system metadata tables, before attempting to fall back.
SQL/MX objects are difficult to remove from a system with an RVU earlier than the
G06.23 RVU. Removing the objects is described later in this section.
•
If you modify or create new SQL/MP aliases, defaults, or stored procedures in Java
(SPJs) in the Release 2.1 or Release 2.0 environment, there are no automated
tools for moving the associated SQL/MX metadata back to SQL/MP metadata
tables. To move metadata, you need to execute MXCI commands, such as
CREATE MPALIAS, CREATE PROCEDURE, and INSERT INTO DEFAULTS, after