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

Introduction to SQL/MX Database Management
HP NonStop SQL/MX Installation and Management Guide—523723-004
1-13
Software Versioning
run-time libraries (SRLs) or system libraries on a node. Only one instance of this
software can exist on a node.
The system software contains APIs that can obtain all the earliest supported releases
that correspond to the MXV. These APIs can also obtain the object schema versions
(OSVs) of objects on which the system software must operate. NonStop SQL/MX uses
these OSVs to perform version checking. For example, when an object is opened, the
executor compares the OSV for that object with the earliest supported schema version.
If the object’s OSV is earlier than the earliest supported schema version, a versioning
error is generated. The earliest supported MXV is used to determine if a remote node
is running an incompatible earlier release of NonStop SQL/MX.
Version Identification
All version identification in NonStop SQL/MX is numeric. The higher the version
number, the later the version. General availability (GA) software releases are assigned
version numbers that are multiples of 20. General availability releases do not
interoperate with Early Adopter Program (EAP) releases or other releases whose
version numbers are not multiples of 20.
The SQL/MX software installed on a node specifies the “earliest supported release” for
version items that have a lower boundary for compatibility and interoperability. All
version numbers between the earliest supported version and the MXV are compatible.
All version numbers outside of this range are incompatible.
Software Version Identifiers for NonStop SQL/MX Release
2.1 and Release 2.0
Table 1-3 lists the software version identifiers for Release 2.1 and Release 2.0.
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.
Table 1-3. Version Identifiers for Release 2.1 and Release 2.0
Version Item
Release 2.1
Version Identifier
Release 2.0 Version
Identifier
Current MXV 1400 1200
Current compiler version 1400 1200
Earliest supported MXV 1200 1200
Current plan version 1400 1200
Earliest supported plan version 800 800