Neoview Messages Manual (R2.2)

Cause An attempt was made 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 the GMCSC.
SQL 25265
25265 An internal error occurred during operation: text.
operation
is the UPGRADE, DOWNGRADE, or RECOVER operation specified by the
user.
text
is an abbreviated reason for the internal error.
Cause A programming error was detected internally.
Effect The operation fails.
Recovery This is an internal error. Contact the GMCSC.
SQL 25266
25266 This release of RECOVER cannot process schema-or-catalog because
an original operation was started by version1 software. The current
SQL/MX Software Version (MXV) is version2.
schema-or-catalog
is the schema or catalog name that was mentioned in the RECOVER
command.
version1
is the software version that issued the original UPGRADE or
DOWNGRADE command.
version2
is the MXV of the system that executes the RECOVER command.
Cause A recover operation was attempted after a fallback to a release earlier than the one
where the original UPGRADE or DOWNGRADE was started.
Effect The operation fails.
Recovery Migrate the system to version1 and retry the RECOVER operation.
SQL 25267
25267 The schema schema-name has been granted schema level privileges;
it cannot be downgraded to version.
schema-name
is a schema that is affected by a DOWNGRADE command.
version
is the target version of a DOWNGRADE command.
Cause A DOWNGRADE operation was attempted that involves one or more schemas with
schema-level privileges that are not supported in the target version.
Effect The operation fails.
Recovery Revoke the offending privileges from the specified schema, and retry the
DOWNGRADE command.
SQL 25300
25300 Module module has module version version1; node node does not
support module versions lower than version2.
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.
300 Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29999)