Neoview Messages Manual (R2.2)

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.
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.
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 details about the visibility of the 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.
error
is a file-system error number.
node
is the expand node name of a remote 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 For information about file-system errors, see Chapter 23 (page 463).
SQL 25420
25420 Node node could not be accessed. File system error number.
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.
Distribution Messages (25400-25499) 305