HP NonStop SQL/MX Messages Manual page 624

Versioning and Distribution Messages (25000
through 25399)
Where version1 and version2 are schema versions of schema1 and schema2,
respectively.
Cause. An attempt was made to create a view, trigger, or referential integrity
constraint that refers to tables or views in schemas of different versions.
Effect. The request fails.
Recovery. Ensure that the affected schemas have the same version.
SQL 25210
25210 Schema schema has schema version version1; node does
not support schema version lower than version2.
Where schema is the name of the schema referenced by a DDL or utility operation.
Where version1 is the schema version of schema .
Where node is the node where the operation is executed or the node where
metadata for the schema resides.
Where version2 is the earliest supported schema version of node.
Cause. The affected DDL or utility operation references a database object in a
schema with a schema version that is lower than the oldest supported schema version
of the node where the operation is executed.
Effect. The request fails.
Recovery. Depends on the circumstance:
•
If the schema is defined on remote downrev nodes only then an upgrade of the
schema should be attempted from one of those nodes.
•
If the schema is defined on the local node then the schema - and all database
objects in it - is inaccessible. A fallback of the local node to a software version that
supports the schema's version is required.
SQL 25211
25211 Table or view object can only be accessed by a node
with SQL/MX Software Version (MXV) version1, the MXV of node
is MXV1.
Where object is the affected table or view.
Where version1 is the schema version of object schema.
Where node is the node that executes the query.
Where MXV1 is the MXV of the node that executes the query.
HP NonStop SQL/MX Messages Manual—640324-001
19 -10