Versioning and distribution messages (25000 through 25399)

SQL 25001

25001 Program executable, executing on node, has encountered a version error.

Where,

executable is the OSS path name or Guardian file name of the program file for the process that encounters the version error.

node is the node where the process executes.

Cause

An SQL/MX system process, for example, an ESP or the compiler, encountered a versioning error. The message is issued since it might not be clear to the user which executable actually encountered the error.

Effect

None, this message will always be issued as a warning. The actual error is described in an accompanying message.

Recovery

Not Applicable.

SQL 25002

25002 A versioning internal error occurred: missing compatibility check.

Cause

This is a versioning internal error, please contact your service provider.

Effect

The operation fails.

Recovery

None.

SQL 25003

25003 A versioning internal error occurred: abort transaction message cleanup.

Cause

This error signals to the call-level interface (CLI) that although the active transaction has been aborted, message -8839 should not be issued. This error occurs when a downrev compiler started by the default compiler encounters an error.

Effect

The CLI suppresses the generation of message -8839.

Recovery

Not applicable.

SQL 25006

25006 The following feature is only available for schemas with version feature-version and higher: string. Schema schema has schema version schema-version.

Where,

feature-version is the minimum version schema that can accommodate the features used by the object;

string is a short text description of the maximum version feature used by the object;

schema is the affected schema of the object;

schema-version is the schema version of schema.

Cause

An operation attempted to create or alter an object with features of later versions compared to the schema version of the object.

Effect

The operation fails.

Recovery

Upgrade the schema to the reported feature version and retry.

SQL 25007

25007 The following feature is not supported: string.

Where string is a short text description of the feature. For example, HASH2 Partitioning.

Cause

An operation is performed to create or alter an object with a feature that is known but not supported.

Effect

The operation fails.

Recovery

None.

SQL 25008

25008 The current command requires a schema with version feature-version or higher. Schema schema has schema version schema-version.

feature-version

is the minimum schema version that can accommodate the features required by the operation.

schema

is the fully qualified ANSI name of the schema that is affected by the operation.

schema-version

is the schema version of schema.

Cause

The command requires at least feature-version version metadata for the affected objects.

Effect

The operation fails.

Recovery

Upgrade the metadata for schema, then retry the operation.

SQL 25100

25100 Remote node node runs an incompatible version of SQL/MX software. The SQL/MX software version (MXV) of node is MXV1, the local node does not support MXVs older than MXV2.

Where,

node is the name of the affected remote node;

MXV1 is the MXV of the affected remote node;

MXV2 is the local node's earliest supported MXV.

Cause

The remote node node has an MXV MXV1 earlier than the local node's earliest supported MXV MXV2, which is not supported.

Effect

The operation fails.

Recovery

Migrate the remote node to an MXV that is later than or equal to the local node's oldest supported MXV. Or, conversely, fallback the local node to an MXV with a corresponding oldest supported MXV that is lower than or equal to the remote node's MXV.

SQL 25103

25103 A SQL/MX compiler of version version is required but cannot be found at the expected location (filename).

Where,

version is the compiler version of a required compiler program;

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 25106

25106 A query running on node-1 cannot use ESPs on node-2.

Where,

node-1 is the node name of the local node.

node-2 is the node name of a remote higher-version node where the query plan attempts to place ESPs.

Cause

The query plan places ESPs on a node that runs on a higher version of SQL/MX than the local node.

Effect

The execution fails.

Recovery

If the local node is running on SQL/MX R3.3: Set CQD REMOTE_ESP_ALLOCATION to OFF, then recompile the query. If the local system is running SQL/MX R3.4 or higher: Recompile the query.

SQL 25200

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.

Where,

object is the name of the affected database object;

version1 is the schema version of that database object schema;

node is the name of the node that detects the incompatibility;

version2 is that node's oldest supported schema version.

Cause

An attempt is made to access a table or view in a schema with a schema version that is lower than the accessing node's oldest supported schema version. This error can be issued from the local node or from an ESP on a remote node.

Effect

The request fails. This message is accompanied by message 25001 which explains what actual software component reported the error.

Recovery

Upgrade the affected schema to a version that is compatible with the MXV of the nodes that need to access the schema.

SQL 25201

25201 Table or view object cannot be accessed because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2.

Where,

objectis the name of the affected database object;

version1 is the schema version of that database object schema;

node is the name of the node that detects the incompatibility;

version2 is that node's MXV.

Cause

An attempt is made to access a table or view in a schema with a schema version that is higher than the accessing node's MXV. This error can be issued from the local node or from an ESP on a remote node.

Effect

The request fails.

Recovery

Downgrade the affected schema to a version that is compatible with the MXV of the nodes that need to access the schema.

SQL 25202

25202 Table or view object cannot be accessed on node because of a version incompatibility. Its schema has version version1; node does not support schema versions lower than version2.

Where,

object is the name of the affected database object;

node is the name of the node where object is present;

version1 is the schema version of object schema;

version2 is that node's oldest supported schema version.

Cause

An attempt is made to access a database object with an object schema version that is incompatible with one or more nodes where the object (or a partition or an index of the object - resides). This message indicates that a migration has been made without properly upgrading database objects of old schemas that are no longer supported on the new version.

Effect

The request fails. The object (and all other objects in the affected schema) is inaccessible.

Recovery

Perform a fallback of the software on the affected node to a version that supports the database objects that are present on the node.

SQL 25203

25203 Table or view object cannot be accessed on node because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2.

Where,

object is the name of the affected database object;

node is the name of the node where object is present;

version1 is the schema version of object schema;

version2 is that node's MXV.

Cause

An attempt is made to access a database object with an object schema version that is incompatible with one or more nodes where the object (or a partition or an index of the object) resides.

This message indicates that a fallback has been made without properly removing database objects of the higher version.

Effect

The request fails. The object (and all other objects in the affected schema) is inaccessible.

Recovery

Migrate the software on the affected node to a version that supports the database objects that are present on the node.

SQL 25204

25204 Table or view object1 has schema version version1; this is incompatible with the version of the compiler that compiles the query. The compiler version is version2.

Where,

object1 is the name of a database object that the affected query references;

version1 is the object schema version of object1;

version2 is the compiler version of the compiler that compiles the query.

Cause

The affected query references a database object with an object schema version that is higher than the compiler version of the compiler. This can happen if a downrev compiler is explicitly being used to compile the query or module.

Effect

The request fails.

Recovery

Do not explicitly use a downrev compiler to compile the query or module.

SQL 25205

25205 Schema schema1 has schema version version1; this is incompatible with the version of the compiler that executes the operation. The compiler version is version2.

Where,

schema1 is the name of a schema that a DDL or utility operation references;

version1 is the schema version of schema;

version2 is the compiler version of the compiler that executes the DDL or utility operation.

Cause

The affected DDL or utility operation references a database object in a schema with a schema version that is higher than the compiler version of the compiler that executes the operation. This can happen if one of these is true:

• A downrev compiler is explicitly being used to execute the operation.

• The operation references an object in a remote uprev schema.

Effect

The request fails.

Recovery

Depending on the actual cause:

• Do not explicitly use a downrev compiler to execute the operation.

• Execute the operation from a node where the schema is defined.

SQL 25206

25206 The system schema on node node has system schema version version1; this is incompatible with the version of the compiler. The compiler version is version2.

Where, node is the name of the node with an incompatible version system schema;

version1 is the system schema version of node;

version2 is the compiler version of the compiler that compiles the query or executes the DDL or utility operation.

Cause

The affected query compilation, DDL, or utility operation need to access system schema tables with a system schema version that is incompatible with the version of the compiler that compiles the query and executes the operation. This can happen if:

• The local system schema version is later than the MXV of a node that is involved in the affected query. Compilation of such a query requires a downrev compiler.

• The local system schema version is higher than the schema version of a schema that is involved in a DDL or Utility operation. Execution of such an operation requires a downrev compiler.

• There is a need to access the system schema on a remote uprev node, and the system schema version of that system schema is later than the current compiler version.

Effect

The request fails.

Recovery

Downgrade the system schema on the affected node to a version that is compatible with the required compiler version.

SQL 25207

25207 The system schema on node node1 has system schema version version1; node node2 does not support system schema versions lower than version2.

Where,

node1 is the name of the node with an incompatible version system schema;

version1 is the system schema version of node1;

node2 is the name of the node where the incompatibility is detected;

version2 is the earliest supported system schema version for node2.

Cause

The affected operation needs to access system schema tables with a system schema version that is very low. This error can be reported for any type of operation: query compilation, query execution, or DDL or Utility operations.

Effect

The request fails.

Recovery

Upgrade the system schema on the affected node to a compatible version.

SQL 25208

25208 The system schema on node node has system schema version version1; the local node cannot access system schemas with versions higher than MXV1.

Where,

node is the name of the node with an incompatible version system schema;

version1is the system schema version of node;

MXV1 is the MXV of the local node.

Cause

During late name resolution for the affected query, you attempted to access an uprev system schema.

Effect

The request fails.

Recovery

Downgrade the system schema on the affected node to a version that is compatible with the MXV of the local node.

SQL 25209

25209 Related schemas must have identical schema version. Schema schema1 has version version1; schema schema2 has version version2.

Where,

schema1 and schema2 are schemas that would be related as the result of the affected DDL or utility operation;

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;

version1 is the schema version of schema;

node is the node where the operation is executed or the node where metadata for the schema resides;

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 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 a DDL or utility operation accesses;

version1 is the schema version of that schema;

node is the name of the node that encounters the incompatibility or the name of the node where metadata for the schema is stored;

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.

SQL 25220

25220 Schema schema cannot be created with a version lower than version.

Where,

schema is the fully qualified ANSI name of the target of a CREATE SCHEMA command;

version is the local system schema version.

Cause

The CREATE_DEFINITION_SCHEMA_VERSION CQD is set to a schema version that is lower than the local system schema version. This setting is not permitted for CREATE SCHEMA.

Effect

The operation fails.

Recovery

Allow the system to select the schema version for the new schema: CONTROL QUERY DEFAULT CREATE_DEFINITION_SCHEMA_VERSION 'SYSTEM'

SQL 25221

25221: Schema schema cannot be created with version version1 because its catalog already contains schemas with version version2.

Where,

schema is the fully qualified ANSI name of the target of a CREATE SCHEMA command;

version1 is the attempted schema version;

version2 is the schema version of one or more existing schemas in the affected catalog.

Cause

The CREATE_DEFINITION_SCHEMA_VERSION CQD is set to a schema version that is different from the schema version of existing schemas in the affected catalog.

Effect

The operation fails.

Recovery

Allow the system to select the schema version for the new schema: CONTROL QUERY DEFAULT CREATE_DEFINITION_SCHEMA_VERSION 'SYSTEM'

SQL 25222

25222 version is not a valid schema version.

Where version is the value that is in effect for the CREATE_DEFINITION_SCHEMA_VERSION CQD.

Cause

A CREATE SCHEMA command created a schema with a value that is not a valid schema version.

Effect

The operation fails.

Recovery

Use a valid schema version value for the CREATE_DEFINITION_SCHEMA_VERSION CQD. For SQL/MX R3.0, these values are valid: 1200 and 3000. Or, allow the system to select the schema version: CONTROL QUERY DEFAULT CREATE_DEFINITION_SCHEMA_VERSION 'SYSTEM'.

SQL 25223

25223 The command command requires the system schema version to be at least NNNN.

Where,

command is the command being executed;

NNNN is the system schema version.

Cause

An attempt was made to execute the specified command, but the system schema version was less than the version denoted by NNNN.

Effect

The operation fails.

Recovery

Upgrade the metadata to the appropriate schema version and resubmit the command.

SQL 25250

25250 Schema schema cannot be downgraded; object_type object has object feature version OFV.

Where,

schema is the name of a schema that is affected by the DOWNGRADE operation;

object is the three-part ANSI name of a database object in schema;

object_type is the type of object. The following object types might appear in the error message: table, index, constraint, trigger, and view. The object type table includes internally generated objects associated with a base table.

OFV is the object feature version of object.

Cause

A DOWNGRADE operation affects a schema containing one or more objects that use features that are not supported in the target version.

Effect

The DOWNGRADE operation fails.

Recovery

Use the FEATURE_VERSION_INFO built-in function to obtain the objects names. Drop the affected objects or alter them so that they no longer have features that are not supported in the target version.

SQL 25251

25251 The operation operation involves node node which does not support schema versions lower than version.

Where,

operation is the actual operation: UPGRADE or DOWNGRADE;

node is the Expand node name of an involved node;

version is the oldest supported schema version of the node.

Cause

The target version of an UPGRADE or DOWNGRADE operation is lower than the oldest supported schema version of one or more nodes where an involved schema is visible.

Effect

The operation fails.

Recovery

The VERSION_INFO built-in function can be used to obtain the names and MXVs of all nodes where a schema is visible. Fallback the specified node and other involved nodes to a version that supports the target schema version. Or, specify a target version that is compatible with all involved nodes.

SQL 25252

25252 The operation operation involves node node which does not support schema versions higher than version.

Where,

operation is the UPGRADE or DOWNGRADE operation;

node is the Expand node name of an involved node;

version is the MXV of node.

Cause

The target version of an UPGRADE or DOWNGRADE operation is higher than the MXV of one or more nodes where an involved schema is visible.

Effect

The operation fails.

Recovery

The VERSION_INFO built-in function can be used to obtain the names and MXVs of all nodes where a schema is visible. Migrate the specified node(s) and other involved nodes to a version that supports the target schema version. Or, specify a target version that is compatible with all involved nodes.

SQL 25254

25254 The RESTRICT option was specified for the operation operation and related catalog catalog exists.

Where,

operation is either UPGRADE or DOWNGRADE;

catalog is the external format ANSI name of a related catalog. More than one related catalog can exist.

Cause

An UPGRADE or DOWNGRADE of all metadata in a catalog used the RESTRICT behavior, and one or more related catalogs exist.

Effect

The operation fails.

Recovery

Use the CASCADE option. The GET NAMES OF RELATED CATALOGS command and the RELATEDNESS built-in function return the names of all catalogs related to a named catalog.

SQL 25256

25256 The schema version of the schema is version1; it cannot be downgraded to version2.

Where,

schema is the schema name of a schema that is affected by a DOWNGRADE operation;

version1 is the schema version of schema prior to the DOWNGRADE operation;

version2 is the target version of the DOWNGRADE operation. It is higher than version1.

Cause

A DOWNGRADE operation affects a schema with a schema version that is lower than the target version of the operation.

Effect

The operation fails.

Recovery

Execute a corresponding UPGRADE operation to upgrade the affected schema to the current version and then re-execute the DOWNGRADE operation.

SQL 25257

25257 No schemas are affected by the operation operation.

Where operation is the UPGRADE or DOWNGRADE operation you specified.

Cause

All schemas affected by an UPGRADE or DOWNGRADE operation already have a schema version equal to the target version.

Effect

None. This message is issued as a warning.

Recovery

None. The specified operation is effectively a no operation (no-op).

SQL 25258

25258 You are not authorized to perform this operation.

Cause

Only the Super ID is authorized to perform UPGRADE, DOWNGRADE, and related RECOVER operations.

Effect

The operation fails.

Recovery

Log on as the Super ID and execute the operation again.

SQL 25259

25259 version is not a valid schema version.

Where version is the target version of a DOWNGRADE operation.

Cause

You specified a target version value that is not a valid schema version.

Effect

The operation fails.

Recovery

Specify a valid schema version.

SQL 25260

25260 No UPGRADE or DOWNGRADE operation is in progress. There is nothing to recover.

Cause

A RECOVER command is issued with a catalog name that has not been specified as the target of an active UPGRADE or DOWNGRADE operation.

Effect

The RECOVER command fails.

Recovery

Use the same specification on the RECOVER command that was originally used on the UPGRADE or DOWNGRADE command.

SQL 25261

25261 The original operation operation is active and cannot be recovered.

Where operation is the UPGRADE or DOWNGRADE operation that you specified.

Cause

A RECOVER command was issued and the original UPGRADE or DOWNGRADE operation is still being actively processed.

Effect

The RECOVER command fails.

Recovery

Terminate the processing of the original command and then reissue the RECOVER command.

SQL 25262

25262 Cannot perform operation because metadata table table is referenced by view view.

Where,

operation is the UPGRADE or DOWNGRADE operation you specified;

table is the 3-part ANSI name of a metadata table that is referenced by a user view;

view is the 3-part ANSI name of the user view.

Cause

The named user view references a metadata table that will be dropped as a result of the UPGRADE or DOWNGRADE command.

Effect

The operation fails.

Recovery

Remove the offending relationship and then reissue the UPGRADE or DOWNGRADE operation. It is advisable to save the view text so that the view can be recreated after the UPGRADE or DOWNGRADE operation.

SQL 25263

25263 The operation operation cannot be executed in a user-defined transaction.

Where operation is UPGRADE or DOWNGRADE operation.

Cause

The specified operation is executed in a user-defined transaction.

Effect

The operation fails.

Recovery

Commit or abort the user-defined transaction and then reissue the operation.

SQL 25264

25264 Definition schema schema cannot be dropped because user schemas of the same version exist in its catalog.

Where schema is a definition schema name.

Cause

You attempted to drop the definition schema but user schemas of the same version exist in the catalog.

Effect

The operation fails.

Recovery

This is an internal error. Contact your service provider.

SQL 25265

25265 An internal error occurred during operation: text.

Where,

operation is UPGRADE, DOWNGRADE, or RECOVER;

text is an abbreviated reason for the internal error.

Cause

A programming error is detected internally.

Effect

The operation fails.

Recovery

This is an internal error. Contact your service provider.

SQL 25266

25266 This release of RECOVER cannot process catalog because an original operation was started by version 1 software. The current SQL/MX Software Version (MXV) is version 2.

Where,

catalog is the catalog name that was mentioned in the RECOVER command;

version 1 is the software version that issued the original UPGRADE or DOWNGRADE command;

version 2 is the MXV of the system that executes the RECOVER command.

Cause

You attempted to perform a recover operation after a fallback to a release earlier than the one where the original UPGRADE or DOWNGRADE command was started.

Effect

The operation fails.

Recovery

Migrate the system to version 1 and retry the RECOVER operation.

SQL 25268

25268: The DOWNGRADE command cannot complete because the version of the system schema on remote_node is higher than 1200.

Where remote_node is the Expand node name of a remote node that is related to the node where the DOWNGRADE command is executed.

Cause

The DOWNGRADE command was executed in a distributed environment where one or more affected catalogs were originally created on remote_node and where the system schema version on that node is higher than 1200.

Effect

The DOWNGRADE command fails.

Recovery

Execute the following command on remote_node:

 >> DOWNGRADE ALL METADATA TO VERSION 1200

Execute the following command on the local node:

 >> RECOVER ALL METADATA RESUME

SQL 25269

25269 : The version of the system schema is version-1; metadata in catalog catalog cannot be downgraded to version version-2.

Where,

version-1 is the actual version of the system schema;

catalog is the external format ANSI name of the user-specified catalog;

version-2 is the user-specified target version for the DOWNGRADE operation.

Cause

Certain versions of user schemas cannot be represented in a higher version system schema. A DOWNGRADE of all metadata in a user catalog specified such a schema version which is lower than the system schema version.

Effect

The operation fails.

Recovery

Either use the DOWNGRADE ALL METADATA command to downgrade all metadata on the entire system or downgrade the metadata in the system catalog before downgrading metadata in user catalogs.

SQL 25270

25270 The version of the metadata in the system catalog must remain at version as long as user schemas of that version exist on node.

Where,

version is the actual version of the system schema;

node is the Expand node name of the local system.

Cause

Certain versions of user schemas cannot be represented in a higher version system schema. Such user schemas exist on the system, and an UPGRADE of all metadata in the system catalog to a higher version was attempted.

Effect

The operation fails.

Recovery

Either use the UPGRADE ALL METADATA command to upgrade all the metadata on the entire system or upgrade only the metadata in user catalogs before upgrading metadata in the system catalog.

SQL 25271

25271 Schema level privileges exist for schema schema-name.

Where,

schema-name is the fully qualified ANSI name of the affected schema.

Cause

You specified a target version to DOWNGRADE that does not support schema level privileges.

Effect

No action is performed and no recovery is required.

Recovery

Use REVOKE command to remove schema level privileges for all the schemas that are affected by the DOWNGRADE command and retry DOWNGRADE.

SQL 25272

25272 Privileges on type name have been granted to privilege group privilege-group.

Where,

type is the type of the affected schema.

name is the fully qualified ANSI name of the affected schema or object.

privilege-group is the name of the affected privilege group.

Cause

You specified a target version to DOWNGRADE that does not support privilege groups.

Effect

No action is performed and no recovery is required.

Recovery

Either use the REVOKE command to remove group privileges on all the schemas and objects that are affected by the DOWNGRADE command or use the DROP PRIVILEGE GROUP command to drop the affected privilege group completely.

SQL 25273

25273 The DOWNGRADE operation affects the DBS configuration.

Cause

You specified a target version to DOWNGRADE that does not support the DBS.

Effect

No action is performed and no recovery is required.

Recovery

Before you use InstallDBS to cleanup the DBS installation, you need to delete all the tenant database and then retry the DOWNGRADE.

SQL 25274

25274 Cannot DOWNGRADE metadata for the system catalog when grants to privilege groups exist.

Cause

You specified a target version to DOWNGRADE that does not support privilege groups.

Effect

No action is performed and no recovery is required.

Recovery

Remove group privileges on all schemas and objects, using the REVOKE statement and then retry the DOWNGRADE.

SQL 25300

25300 Module module has module version version1; node node does not support module versions lower than version2.

Where,

module is the name of the affected module;

version1 is the module version of the affected module;

node is the name of the node that detects the incompatibility;

version2 is the executing node's oldest supported plan version.

Cause

An attempt is made to load a module with a module version that is lower than the executing node's oldest supported plan version.

Effect

The request fails.

Recovery

Recompile the module with a supported version compiler.

SQL 25301

25301 Module module has module version version1; the local node does not support module versions higher than version2.

Where,

module is the name of the affected module;

version1 is the module version of the affected module;

version2 is the MXV of the local node.

Cause

An attempt is made to load a module with a module version that is higher than the MXV.

Effect

The request fails.

Recovery

Recompile the module with a supported version compiler.

SQL 25302

25302 The query plan version is version1; node node does not support query plan versions lower than version2.

Where,

version1 is the plan version of the affected query;

node is the name of the node that detects the incompatibility;

version2 is the executing node's oldest supported plan version.

Cause

There are two possibilities:

• Automatic recompilation is attempted (if allowed) with the current compiler. If the recompilation succeeds, this message is returned as a warning and the query is executed again.

• Automatic recompilation is not supported or failed. This message is returned as an error.

Effect

The operation fails.

Recovery

Recompile the module with a supported version compiler.

SQL 25303

25303 The query plan version is version1; node node does not support query plan versions higher than version2.

Where,

version1 is the plan version of the affected query;

node is the name of the node that detects the incompatibility;

version2 is the MXV of the node that detects the incompatibility.

Cause

You attempted to execute a query plan fragment with a plan version that is later than the MXV of the node that executes the plan or plan fragment.

Effect

There are two possibilities:

• Automatic recompilation is attempted (if allowed) with a downrev compiler that produces plans with a plan version that is compatible with version2 . If the recompilation succeeds, this message is returned as a warning and the query is re-executed.

• Automatic recompilation is not supported or failed. This message is returned as an error. The operation fails.

Recovery

Recompile the plan or module with a supported version compiler that generates plans that are compatible with all involved nodes.

SQL 25311

25311 System module module has a wrong module version. The expected module version is version1, the actual module version is version2.

Where,

module is the name of the affected system module;

version1 is the expected module version of module;

version2 is the actual module version of module.

Cause

The system module was manually renamed to indicate a version other than the actual version.

Effect

The request fails.

Recovery

Reinstall the system module.

SQL 25312

25312 A version version1 compiler is required to compile the query. The current compiler version is version2.

Where,

version1 is the required compiler version;

version2 is the actual compiler version.

Cause

The query affects one or more nodes with an MXV lower than the current compiler version.

Effect

The request fails.

Recovery

Explicitly use a compiler of the specified version.

SQL 25313

25313 AA compiler with version less than or equal to version1 and higher than or equal to version2 is required to compile the query. The current compiler version is version3.

Where,

version1 is the highest compiler version that can compile the query;

version2 is the lowest compiler version that can compile the query;

version3 is the actual compiler version.

Cause

The query affects one or more nodes with an MXV lower than the current compiler version.

Effect

The request fails.

Recovery

Explicitly use a compiler with version in the specified interval.