Neoview Messages Manual (R2.2)

SQL 1030
1030 File label file name could not be accessed. File system error
error.
file name
is the name of an HP Neoview database file.
error
is a file-system error number.
Cause See the accompanying error message for the cause.
Effect The operation fails.
Recovery For information about file-system errors, see Chapter 23 (page 463).
SQL 1031
1031 Object object-name could not be dropped.
object-name
is the SQL object.
Cause See the accompanying error message for the cause.
Effect The HP Neoview database software does not drop the object.
Recovery Apply the recovery of the accompanying error message.
SQL 1034
1034 SQL/MX was not able to initialize.
Cause For the cause, see the accompanying error message.
Effect The operation fails.
Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
SQL 1035
1035 Catalog catalog-name already exists.
catalog-name
is the name of an HP Neoview database 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
1036 Only services ID can execute DROP SQL.
Cause An attempt was made to drop SQL by a user who is not the services ID.
Effect The operation fails.
Recovery The services ID needs to issue the DROP SCHEMA statement.
SQL 1037
1037 SQL/MX is not installed on system segment.
segment
is the name of the segment referenced by the operation.
Cause In a replication or distribution context: An operation attempted to create a catalog
reference or a partition on a segment where the HP Neoview database has not been installed.
Effect The operation fails.
Recovery Either reissue the statement specifying a different segment, or install the HP
Neoview database on segment and resubmit.
24 Data Definition Language (DDL) Messages (1000 Through 1999)