HP NonStop SQL/MX Messages Manual page 640

Versioning and Distribution Messages (25000
through 25399)
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 a 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.
Where catalog1 and catalog2 are ANSI catalog names.
Note. 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.
Where 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).
Where object is the ANSI name of a database object specified in the DML query.
HP NonStop SQL/MX Messages Manual—640324-001
Distribution Messages (25400-25499)
19 -26