HP NonStop SQL/MX Messages Manual page 576

Table of Contents

Advertisement

Utility Messages (20000 through 23099)
SQL 20751
20751 A user-defined transaction has been started. VERIFY
cannot be performed.
Cause. A TMF transaction is currently active. The VERIFY process does not allow
active transactions.
Effect. The operation fails.
Recovery. Commit or terminate the current transaction and resubmit.
SQL 20752
20752 The cmdname command cannot work on object object-name
that has an object type of type. cmdname supports only
objects that have an object type of BT.
Where,
cmdname is the name of the utility.
object-name is the name of the specified object.
type is the object's type as found in the metadata—base table (BT).
Cause. You possibly specified a utility operation on a view, stored procedure, or an
alias for an SQL/MP object. The utility operation on these objects is not allowed.
Effect. The operation fails.
Recovery. Specify the name of a table and resubmit.
SQL 20753
20753 An internal error was encountered by the VERIFY
operation.
Cause. An unexpected error caused VERIFY to terminate.
Effect. The operation fails.
Recovery. None. Contact your service provider.
SQL 20754
20754 File system error (error) was returned while retrieving
the object from the resource fork.
Where error is the error returned by the file system.
HP NonStop SQL/MX Messages Manual—640324-001
18- 100

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents