Manualshelf

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

ManualsBrandsHP ManualsServerHP NonStop G-Series
531532533534535536537538539540
Versioning and Distribution Messages (25000
through 25399)
HP NonStop SQL/MX Messages Manual—523730-004
18-4
Cause. The remote node node runs a non-General Availability (non-GA) release of
SQL/MX and cannot access remote nodes that have an MXV different from its own
(MXV1).
Effect. The operation fails.
Recovery. Migrate the remote node to a supported GA release. Or, conversely,
migrate the local node to the same non-GA release as the remote node.
SQL 25103
Where version is the compiler version of a required compiler program.
Where filename is the expected Guardian file name of the required compiler
program file.
Cause. The compiler of the specified, supported version is required to compile the
query or module; however, that compiler does not exist in the default compiler location.
Effect. The operation fails.
Recovery. Install the specified version compiler in the expected location.
SQL 25200
Where object is the name of the affected database object.
Where version1 is the schema version of that database object’s schema.
Where node is the name of the node that detects the incompatibility.
Where version2 is that node’s oldest supported schema version.
Cause. You attempted to access a table or view in a schema with a schema version
that is earlier than the accessing node’s earliest supported schema version. This
message can be issued from the local node or from an ESP on a remote node.This
message is accompanied by message 25001, which explains what actual software
component reported the error.
Effect. The operation fails.
Recovery. Upgrade the affected schema to a version that is compatible with the MXV
of the nodes that need to access the schema.
25103 A SQL/MX compiler of version version is required but
cannot be found at the expected location (filename).
Note. As of the ABU SPR, this message is no longer generated.
25200 Table or view object cannot be accessed because of a
version incompatibility. Its schema has version version1;
node does not support schema versions lower than version2.