Distribution messages (25400-25499)
SQL 25401
25401 Catalog catalog has not been registered on node node.
-
Where,
-
catalog is the ANSI name of the target catalog. It must be visible on the local node;
-
node is a remote node where catalog visibility is required.
Cause
You attempted to access or create a database object in catalog catalog on node node, but catalog has not been registered on that node.
Effect
If the message is issued as an error, the operation fails. If the message is issued as a warning (accompanying warning 25406), a late name resolution or automatic recompilation is attempted.
Recovery
When the message is issued as an error, correct the error and retry the operation. If the message is issued as a warning, NonStop SQL/MX attempts to recover automatically.
SQL 25402
25402 Catalog catalog has previously been registered on node node.
-
Where,
-
catalog is the ANSI name of the target catalog. It must be visible on the local node;
-
node is a remote node where a reference to the target catalog already exists.
Cause
You attempted to register catalog catalog on node node, but a reference to catalog already exists on that node.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25403
25403 Catalog catalog already exists on node node1, but it is unrelated to the catalog of the same name on the local node node2.
-
Where,
-
catalog is the ANSI name of the target catalog;
-
node1 is a remote node where an independent catalog with the desired ANSI name already exists;
-
node2 is the name of the local node.
Cause
You attempted to access catalog catalog on node node1, but an independent catalog with the same name already exists on that node.
Effect
If the message is issued as an error, the operation fails. If the message is issued as a warning (accompanying warning 25406), a late name resolution or automatic recompilation is attempted.
Recovery
If the message is issued as an error, correct the error and retry the operation. If the message is issued as a warning, NonStop SQL/MX attempts to recover automatically.
SQL 25404
25404 Catalogs catalog1 and catalog2 must have identical visibility.
Catalogs have identical visibility when they are registered on the same set of nodes.
Cause
You attempted to establish a relationship between catalog1 and catalog2, which have different visibility.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25405
25405 Catalog catalog cannot be created because location location is a remote node.
-
Where,
-
catalog is the ANSI name of the target catalog;
-
location is the location from a CREATE CATALOG operation.
Cause
A CREATE CATALOG operation specified a remote location, either explicitly or because the default volume is remote.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25406
25406 Runtime visibility check failed for type of object object trying to access node.
-
Where,
-
type of object is the object type of object (for instance, index);
-
object is the ANSI name of a database object specified in the DML query;
-
node is the expand node name of a remote node where one or more partitions of object resided when the DML query was compiled.
Cause
When the DML query was compiled, the affected database object had partitions on a remote node, and the database object's catalog was visible on both the remote node and the local node. When the query was executed, the visibility of the object's catalog changed. See accompanying messages 1002, 25401, or 25403 for more detail of the visibility change.
Effect
If the message is issued as an error, it is accompanied by error 1002, and the query fails. If the message is issued as a warning, it is accompanied by warning 25401 or 25403, and late name resolution or automatic recompilation is attempted. If that succeeds, the query executes. If not, the query fails and additional errors are issued.
Recovery
If the message is issued as an error, correct the error and resubmit.
SQL 25407
25407 File system error error was encountered on access to the system schema on node.
Cause
Late name resolution encountered the reported file system error when trying to access the system schema tables on the specified node.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25420
25420 Node node could not be accessed. File system error number.
-
Where,
-
node is the remote node that is required, implicitly or explicitly, by a replication operation;
-
number is the file system error that resulted from the attempt to access node.
Cause
A replication operation required access to a remote node that cannot be accessed because of the reported file system error.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25421
25421 An automatic catalog reference for catalog already exists on node node.
-
Where,
-
catalog is the ANSI name of the target catalog;
-
node is a remote node where an automatic reference of the target catalog exists.
Cause
The target node of a REPLICATE SCHEMA operation already has an automatic reference for the specified schema catalog.
Effect
The operation fails.
Recovery
None. Replicas of the specified schema already exist on the node.
SQL 25422
25422 Catalog catalog cannot be unregistered from node node because database objects in the catalog are present on the node.
-
Where,
-
catalog is the ANSI name of the target catalog for the UNREGISTER CATALOG command;
-
node is the name of the target node for the UNREGISTER CATALOG command.
Cause
An UNREGISTER CATALOG operation attempted to remove a catalog reference from a node where one or more database objects in that catalog are present.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25423
25423 Schema schema has no replica on node node.
-
Where,
-
schema is the ANSI name of the affected schema;
-
node is the remote node with no replica of the affected schema.
Cause
The target node of an UNREPLICATE SCHEMA operation does not have a replica of the affected schema.
Effect
The operation fails.
Recovery
None. The affected schema has no replica on the target node.
SQL 25424
25424 A replica of schema schema already exists on node node.
-
Where,
-
schema is the ANSI name of the affected schema;
-
node is the remote node where a replica of the affected schema exists.
Cause
The target node of a REPLICATE SCHEMA operation already has a replica of the affected schema.
Effect
The operation fails.
Recovery
None. A replica of the affected schema already exists on the desired node.
SQL 25425
25425 Node node contains the only automatic catalog reference of catalog catalog. Schema replicas cannot be removed.
-
Where,
-
node is the node where the single automatic replica of the target catalog resides;
-
catalog is the ANSI name of the target catalog.
Cause
The target node of an UNREPLICATE SCHEMA operation holds the only automatic reference for the affected schema catalog.
Effect
The operation fails.
Recovery
Correct the error and resubmit.
SQL 25426
25426 Volume volume could not be accessed. File system error number.
-
Where,
-
volume is the name of a volume that is required, implicitly or explicitly, by the operation. The volume name is fully qualified (for example, \NODEX.$VOLY);
-
number is the file system error that resulted from the attempt to access volume.
Cause
The operation required access to a volume, local, or remote, that cannot be accessed because of the reported file system error.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25427
25427 Catalog catalog1 cannot be unregistered from node node because it is related to catalog2 which has a reference on the target node.
-
Where,
-
catalog1 is the ANSI name of the target node for the UNREGISTER CATALOG command;
-
node is the name of the target node for the UNREGISTER CATALOG command;
-
catalog2 is the ANSI name of a catalog that is related to the target catalog.
Cause
An UNREGISTER CATALOG operation using the RESTRICT option attempted to remove a catalog reference from a node. However, the target catalog is related to one or more other catalogs that are visible on the target node. This error is issued once per related catalog.
Effect
The operation fails.
Recovery
Use the CASCADE option on UNREGISTER CATALOG.
SQL 25428
25428 Catalog catalog1 cannot be registered on node node because it is related to catalog2 which has no reference on the target node.
-
Where,
-
catalog1 is the ANSI name of the target catalog for the REGISTER CATALOG command;
-
node is the name of the target node for the REGISTER CATALOG command;
-
catalog2 is the ANSI name of a catalog that is related to the target catalog.
Cause
A REGISTER CATALOG operation using the RESTRICT option attempted to register a catalog on a node. However the target catalog is related to one or more other catalogs that are not visible on the target node. This error is issued once per related catalog.
Effect
The operation fails.
Recovery
Use the CASCADE option on REGISTER CATALOG.
SQL 25429
25429.Catalog catalog cannot be unregistered from node node because it is the only catalog reference that has an automatic replication rule.
-
Where,
-
catalog is the ANSI name of the target catalog for the UNREGISTER CATALOG command;
-
node is the name of the target node for the UNREGISTER CATALOG command.
Cause
An UNREGISTER CATALOG operation attempted to remove the single automatic catalog reference for a catalog.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 25430
25430 The system catalog cannot be the target of a REGISTER CATALOG or UNREGISTER CATALOG command.
Cause
A REGISTER CATALOG or UNREGISTER CATALOG operation was attempted for the system catalog.
Effect
The operation fails.
Recovery
None.
SQL 25431
25431 Node node runs a release of SLQ/MX that supports only SQL/MP tables.
Cause
A REGISTER CATALOG operation attempted to register the catalog on a Release 1.8 node.
Effect
The operation fails.
Recovery
None.
SQL 25490
25490 DDB Debug Warning: text.
Cause
A test condition was encountered by debug mode software. The explanatory text contains the details.
Effect
The affected operation succeeds.
Recovery
None. This message is issued as a warning.