HP NonStop SQL/MX Messages Manual page 627

Versioning and Distribution Messages (25000
through 25399)
Where MXV1 is the MXV of the node that executes the query.
Cause. The accessing node runs a non-GA version of SQL/MX and is compatible only
with schemas created by its own version.
Effect. The operation fails.
Recovery. Upgrade or downgrade the accessing node to an SQL/MX release that is
compatible with the affected schema's version.
SQL 25218
25218 Schema schema has schema version version1; node cannot
access or represent schemas with version higher than MXV1.
Where schema is a schema that is accessed by a DDL or utility operation.
Where version1 is the schema version of that schema.
Where node is the name of the node that encounters the incompatibility or the name of
the node where metadata for the schema is stored.
Where MXV1 is the MXV of that node.
Cause. A DDL or utility operation attempted to access a schema with a version higher
than the local node's MXV.
Effect. The operation fails.
Recovery. Migrate to an SQL/MX version that has an MXV that is compatible with the
affected schema version.
SQL 25219
25219 The query can not be compiled because of a version
mismatch; the highest schema version of the involved tables
or views is higher than the lowest SQL/MX Software Version
(MXV) of the involved nodes.
Cause. A mixed-version query was detected by the compiler (for example, a query
where the MXV of one or more of the involved nodes is lower than the OSV of one or
more of the involved database objects). Such a query cannot be compiled.
Effect. The query compilation fails.
Recovery. Investigate and resolve the situation. Note that the message text does not
specify which node(s) or database object(s) are involved the reason being that an
unknown number of nodes and database objects may be affected.
HP NonStop SQL/MX Messages Manual—640324-001
19 -13