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

Managing an SQL/MX Distributed Database
HP NonStop SQL/MX Installation and Management Guide—523723-004
13-25
Managing Mixed Releases of NonStop SQL/MX
recovery. Another important reason for keeping TRANSACTIONS OFF is to
provide the system administrator time for additional recovery operations, as
needed, before the applications can start transaction activity. For additional
information, see the TMF Planning and Configuration Guide.
•
A number of situations can cause severe problems with the consistency of an
SQL/MX database. Various techniques can resolve these problems. You should
not, however, attempt these operations without help from your service provider:
°
Recover a node with distributed objects by using the TIME option of TMF. This
procedure can cause an inconsistent database.
°
Perform a RESTORE of objects on a node, such that the restored objects
would not be consistent with the rest of the database.
°
Use the MXTOOL GOAWAY utility on portions of a network database.This
procedure can leave unresolvable references in other metadata.
If a situation arises that you think might affect the network-distributed SQL/MX
database, contact your service provider for additional information.
Managing Mixed Releases of NonStop SQL/MX
Neither Release 2.1 or Release 2.0 supports interoperability with Release 1.8 in a
distributed database environment. You cannot perform queries—through embedded
SQL or dynamic SQL—from a node running Release 2.1 or Release 2.0 on a node
running Release 1.8, and vice versa. You can, however, use Release 1.8 query plans
and modules that have been compiled on a Release 2.1 or Release 2.0 node, as these
are within the range of the oldest support plan release (800). Please note these other
restrictions:
•
Running different releases of SQL/MX software simultaneously on separate nodes
of an interrelated SQL/MX database application is not allowed between Release
2.1 or Release 2.0 nodes and Release 1.8 nodes.
•
Running a later release of SQL/MX software on a development node that supports
a production node or nodes running an earlier release of SQL/MX software is not
allowed between Release 2.1 or Release 2.0 nodes and Release 1.8 nodes.
•
Upgrading to a later release of NonStop SQL/MX or downgrading to an earlier
release is allowed.
You can use different SQL/MX software releases if the releases are within the
supported range and Release 2.1 or Release 2.0 nodes and Release 1.8 nodes do not
interoperate in the same distributed network. For more information, see Versioning
Issues on page 1-12.