SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Versioning and Distribution Messages (25000
through 25399)
HP NonStop SQL/MX Messages Manual—523730-004
18-12
SQL 25218
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 node that encounters the incompatibility or 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 later
than the local node’s MXV.
Effect. The operation fails.
Recovery. Migrate to an SQL/MX version that is compatible with the affected
schema’s version.
SQL 25219
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 earlier than the MXV of one or
more of the involved database objects). Such a query cannot be compiled.
Effect. The operation fails.
Recovery. Investigate and resolve the situation. Note that the message text does not
specify which nodes or database objects are involved, because an unknown number of
nodes and database objects can be affected.
SQL 25300
Where module is the name of the affected module.
Where version1 is the module version of the affected module.
Where node is the name of the node that detects the incompatibility.
Where version2 is the executing node’s oldest supported plan version.
25218 Schema schema has schema version version1; node cannot
access or represent schemas with versions higher than MXV1.
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.
25300 Module module has module version version1; node node
does not support module versions lower than version2.