SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Privilege and Alias Messages (1000 through 1999)
HP NonStop SQL/MX Messages Manual—523730-004
3-9
SQL 1034
Cause. See the accompanying error message for the cause.
Effect. The operation fails.
Recovery. Apply the recovery of the accompanying error message
SQL 1035
Where catalog-name is the name of an SQL/MX catalog.
Cause. You attempted to create a catalog using the name of an already existing
catalog.
Effect. The operation fails.
Recovery. None if this is the desired catalog. Otherwise, correct the catalog name and
resubmit.
SQL 1036
Cause. An attempt was made to drop SQL by a user who is not the super ID.
Effect. The operation fails.
Recovery. The super ID needs to issue the DROP SCHEMA statement.
SQL 1037
Where node is the name of the node referenced by the operation.
Cause. In a replication or distribution context: An operation attempted to create a
catalog reference or a partition on a node where SQL/MX has not been installed.
Effect. The operation fails.
Recovery. Either reissue the statement specifying a different node, or install SQL/MX
on node and resubmit.
1034 SQL/MX was not able to initialize.
1035 Catalog catalog-name already exists.
1036 Only super ID can execute DROP SQL.
1037 SQL/MX is not installed on system node.