HP NonStop SQL/MX Messages Manual page 641

Versioning and Distribution Messages (25000
through 25399)
Where 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.
Where error is a Guardian file system error number.
Where 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. 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.
Where 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.
HP NonStop SQL/MX Messages Manual—640324-001
Distribution Messages (25400-25499)
19 -27