Data Definition Language (DDL) messages (1000 through 1999)
SQL 1001
1001 An internal error occurred in module name on line num. DETAILS(details).
-
Where,
-
name is the name of the module;
-
num is the line number;
-
details are the details of the error.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1002
1002 Catalog catalog does not exist or has not been registered on node node.
Cause
The catalog is not visible on the local node, because it either does not exist or exists elsewhere on the network but has not been registered on the local node.
Effect
The operation fails.
Recovery
Enter a valid catalog name (or register the catalog on the node indicated) and resubmit.
SQL 1003
1003 Schema schema does not exist.
Cause
In a replication context: a REPLICATION SCHEMA operation specified a schema that does not exist. The specified schema must exist to complete the operation.
Effect
The operation fails.
Recovery
Check that a schema named schema exists and resubmit the statement. If the schema is a metadata schema, upgrade metadata to the required version, and resubmit the statement.
SQL 1004
1004 Object object-name does not exist or object type is invalid for the current operation.
Cause
You attempted an operation on an object that does not exist or attempted an operation on an object with the wrong type. For example, you tried to drop a view but specified a table name.
Effect
The operation fails.
Recovery
Check that an object object-name exists. If you did not fully qualify the name, check that the defaults generate the correct fully qualified name and resubmit.
SQL 1005
1005 Constraint constraint-name does not exist.
Cause
The ALTER TABLE statement you attempted requires the existence of a constraint named constraint-name.
Effect
The operation fails.
Recovery
Check that a constraint named constraint-name exists for the table specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table.
SQL 1006
1006 Index index-name does not exist.
Cause
The operation you attempted requires the existence of an index named index-name.
Effect
The operation fails.
Recovery
Check that an index named index-name exists. If you did not fully qualify the name, check that the defaults generate the correct qualified name.
SQL 1008
1008 User user does not exist.
Cause
The username specified in a GRANT statement, the username or user ID in a REVOKE statement, or the authorization ID in a CREATE SCHEMA statement does not represent a valid Guardian user.
Effect
The operation fails.
Recovery
Correct the username or the user ID and resubmit the statement.
SQL 1009
1009 Column column-name does not exist in the specified table.
Cause
The referenced table does not have a column with this name.
Effect
The operation fails.
Recovery
Replace either the table name or the column name (whichever is incorrect) and resubmit.
SQL 1010
1010 The statement just specified is currently not supported.
Cause
The statement that you specified is not available for use.
Effect
The operation fails.
Recovery
Do not attempt to use this SQL/MX statement.
SQL 1012
1012 No privileges were granted. You lack grant option on the specified privileges.
Cause
You attempted to grant privileges for which you do not have grant options.
Effect
No privileges are granted.
Recovery
You must have grant options for privileges to grant them.
SQL 1013
1013 Not all privileges were granted. You lack grant option on some of the specified privileges.
Cause
You attempted to grant privileges, but you do not have grant options for at least one of them.
Effect
NonStop SQL/MX granted some privileges, but not all that you attempted to grant.
Recovery
You must have grant options for privileges to grant them.
SQL 1014
1014 Privileges were not revoked. Dependent privilege descriptors still exist.
Cause
You attempted to revoke a privilege for a user who has granted privileges to another user. Privileges must be revoked in reverse order from how they were granted. If you perform a grant to another user who, then performs a grant to a third user, you cannot revoke privileges from the second user until that user revokes privileges from the third user.
Effect
NonStop SQL/MX did not revoke the privileges.
Recovery
Ensure that the dependent privileges are first revoked from the user whose privileges you want to revoke.
SQL 1015
1015 Some of the specified privileges could not be revoked.
Cause
You attempted to revoke a privilege that does not exist or that is granted by another user.
Effect
NonStop SQL/MX did not revoke the privileges.
Recovery
Reissue the statement with proper authorization.
SQL 1016
1016 Redundant references to column column-name were specified in the constraint or trigger definition.
Cause
You created a constraint with multiple references to column-name.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 1017
1017 You are not authorized to perform this operation.
Cause
You attempted a DDL or utility operation without proper authorization, or remote password validation failed.
Effect
The operation fails.
Recovery
Reissue the command with the proper authorization.
DDL and utility operations are restricted as follows:
-
Operations on a database catalog are restricted to the catalog owner only.
-
Operations on a database schema are restricted to the schema owner only.
-
Operations on a database object are restricted to the schema owner and the object owner.
-
In all cases, if super.super is a security administrator or security administrators are not defined, super.super is authorized to perform DDL and utility operations.
-
Also, invalid remote password for the user might trigger this error. Verify the remote password for the user and resubmit.
The error descriptions of SQL messages 1017 and 25258 are same.
SQL 1019
1019 No valid primary partition for table-name could be found.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1020
1020 Privilege settings on metadata tables cannot be changed.
Cause
You attempted to change the privilege settings on a metadata schema or table.
Effect
NonStop SQL/MX does not change the settings.
Recovery
None.
SQL 1021
1021 SQL is already initialized on system node-name.
Cause
NonStop SQL/MX has already been initialized on this node.
Effect
No operation is performed.
Recovery
None if SQL is operating normally.
SQL 1022
1022 Schema schema-name already exists.
Cause
You attempted to create a schema in a catalog with an existing schema name.
Effect
The operation fails.
Recovery
If you did not use a fully qualified name, check that the default generates the correct catalog name. Retry the request, specifying a schema that does not already exist.
SQL 1023
1023 Only super ID can name an authorization ID other than the current user name.
Cause
You attempted to create a schema with the authorization ID of another user. Only the super ID can do this.
Effect
The operation fails.
Recovery
Log on as the super user to create a schema with another owner.
SQL 1024
1024 File system error error-number occurred on text-string-1. text-string-2.
-
Where,
-
error-number is an error originating from the file system;
-
text-string-1 is the file name;
-
text-string-2 is (optionally) additional details about the error.
Cause
To determine the cause, look up this error number in the file system manual.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1025
1025 Request failed. One or more dependent objects exist.
Cause
This error might occur when you drop a constraint, an index, or a table. You cannot drop these objects if they have dependent objects and the drop-behavior is RESTRICT.
Effect
NonStop SQL/MX does not perform the operation.
Recovery
For DROP statements that support the CASCADE drop-behavior, you can reissue the statement specifying CASCADE. For other DROP statements, you must first drop each of the dependent objects, then drop the object.
SQL 1026
1026 Only the schema owner or super ID can drop a schema.
Cause
An attempt was made to drop a schema by someone other than its owner or the super ID.
Effect
No SQL objects are dropped.
Recovery
The owner of the schema (or super ID) must issue the DROP SCHEMA statement.
SQL 1027
1027 The definition schema definition-schema-name is dropped when its catalog is dropped.
Cause
You attempted to drop the schema containing the metadata tables for the catalog.
Effect
No SQL objects are dropped.
Recovery
Use DROP SCHEMA statements to drop all the user-created schemas in the catalog. Then use the DROP CATALOG statement to drop the catalog. The schema definition-schema-name is dropped when you drop its catalog.
SQL 1028
1028 The schema must be empty. It contains at least one object object-name.
Cause
You attempted to drop a schema that contains one or more objects.
Effect
The schema is not dropped.
Recovery
Either drop all the objects in schema-name and resubmit the statement, or resubmit the DROP statement using the CASCADE option.
SQL 1029
1029 Object object-name could not be created.
Cause
This error can result from various CREATE statements. To determine the cause, see the accompanying error messages.
Effect
The object is not created.
Recovery
Apply the recovery of the accompanying error messages.
SQL 1030
1030 File label Guardian name could not be accessed. File system error error.
Cause
A file system error occurred while accessing the file label for Guardian name and the stored row count could not be retrieved.
Effect
The operation fails.
Recovery
Apply the recovery of the accompanying error message.
SQL 1031
1031 Object object-name could not be dropped.
Cause
See the accompanying error message for the cause.
Effect
NonStop SQL/MX 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
See the accompanying error message for the cause.
Effect
The operation fails.
Recovery
Apply the recovery of the accompanying error message.
SQL 1035
1035 Catalog catalog-name already exists.
Cause
You attempted to create a catalog using the name of an 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 super ID can execute DROP SQL.
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 must issue the DROP SCHEMA statement.
SQL 1037
1037 SQL/MX is not installed on system node.
Cause
In a replication or distribution context: An operation attempted to create a catalog reference or a partition on a node where NonStop SQL/MX has not been installed.
Effect
The operation fails.
Recovery
Either reissue the statement specifying a different node, or install NonStop SQL/MX on node and resubmit.
SQL 1038
1038 Not all user catalogs have been dropped from the system.
Cause
You attempted to drop SQL while one or more user-created catalogs existed.
Effect
The operation fails.
Recovery
Drop all user-created catalogs before dropping SQL.
SQL 1039
1039 The DROP SQL statement could not be executed.
Cause
See the accompanying error message for the cause.
Effect
NonStop SQL/MX does not drop SQL.
Recovery
Apply the recovery of the accompanying error message.
SQL 1040
1040 The use of ALTER on metdata tables is not permitted.
Cause
An ALTER TABLE statement was issued naming a table that is part of the SQL/MX metadata. Such tables cannot be altered.
Effect
The operation fails.
Recovery
None.
SQL 1041
1041 The primary key has already been defined.
Cause
You attempted to add a primary key to a table that already contains a primary key.
Effect
The operation fails.
Recovery
None.
SQL 1042
1042 All PRIMARY KEY or UNIQUE constraint columns must be NOT NULL.
Cause
You did not specify NOT NULL on one or more columns that are included in a UNIQUE or PRIMARY KEY constraint.
Effect
The operation fails.
Recovery
Reissue the statement with NOT NULL specified for all columns that are in the PRIMARY KEY and UNIQUE constraints.
SQL 1043
1043 Constraint constraint-name already exists.
Cause
You assigned the same constraint name to two constraints on the same table. Constraint names must be unique among all the constraints for a table.
Effect
The operation fails.
Recovery
Make all the constraint names for the table unique. Use SHOWDDL to see the names of existing constraints.
SQL 1044
1044 Constraint constraint-name could not be created because the referenced columns in the referenced table are not part of a unique constraint.
Cause
The columns that constraint-name references in the referenced table are not part of a unique constraint.
Effect
The operation fails.
Recovery
Check that constraint-name references a unique or primary constraint in the referenced table.
SQL 1045
1045 The unique constraint cannot be used because it is deferrable.
Cause
The referential constraint is referencing the unique constraint that is declared as deferrable. This is an internal error.
Effect
The operation fails.
Recovery
Check that the referential constraint references a unique constraint that is not declared deferrable. Contact your service provider.
SQL 1046
1046 Referenced and referencing column lists do not match for constraint constraint-name.
Cause
The list of referencing columns in constraint-name does not match the list of unique key columns that it is referencing.
Effect
The operation fails.
Recovery
Verify that the constraint-name list of referencing columns matches the list of referenced columns.
SQL 1047
1047 Request failed. Dependent view view-name exists.
Cause
An object that has a dependent view cannot be dropped unless you use the CASCADE option on the DROP statement.
Effect
The operation fails.
Recovery
To drop the object and all its dependent objects, you can either drop each of the dependent objects using individual DROP statements before dropping the object itself, or use the CASCADE clause on the DROP statement for the object.
SQL 1048
1048 The statement currently supports only RESTRICT drop behavior.
Cause
Drop behavior CASCADE was specified on a DROP statement that supports only RESTRICT drop behavior.
Effect
The operation fails.
Recovery
Reissue the DROP statement, specifying RESTRICT or omitting the drop behavior (which will default to RESTRICT).
SQL 1049
1049 Constraint cannot be dropped because it was specified to be NOT DROPPABLE.
Cause
You attempted to drop a constraint that cannot be dropped.
Effect
The operation fails.
Recovery
None.
SQL 1050
1050 Constraint cannot be dropped because it is used as a referenced object for a foreign key.
Cause
You attempted to drop a unique or primary constraint, with dependent referential constraints, using the RESTRICT option, which does not remove such constraints.
Effect
The drop command fails.
Recovery
If you want to drop the dependent referential constraints, use the CASCADE option for the DROP CONSTRAINT command.
SQL 1051
1051 You do not have the required privilege(s) on object-name.
Cause
You do not have adequate privileges to create a view or a trigger.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for the required security needed to create a view or trigger.
SQL 1052
1052 Constraint cannot be dropped because it does not belong to the specified table.
Cause
An ALTER TABLE statement with DROP CONSTRAINT specified a name that is not the name of a constraint on this table.
Effect
No constraint is dropped.
Recovery
Either correct the table name or the constraint name and reissue the statement. You can use the SHOWDDL statement to display the names of constraints on the table.
SQL 1053
1053 Unique index index-name could not be created because the specified column(s) contain duplicate data.
Cause
The rows existing in the table violate the uniqueness constraint specified in the CREATE INDEX statement.
Effect
The index is not created.
Recovery
Either change the list of columns for the unique index, or change the rows in the table to remove duplicates. Then reissue the statement.
SQL 1054
1054 Index index-name already exists.
Cause
You attempted to create an index with the name of an index that already exists on the specified table.
Effect
The index is not created.
Recovery
Choose a different name for the index and reissue the statement.
SQL 1055
1055 Object object-name already exists.
Cause
You attempted to create an object with a name that is already in use for a table, a view, or a stored procedure in this schema.
Effect
The operation fails.
Recovery
Verify that the object name is correct. If the name is not fully qualified, verify that the current schema is set correctly. You can choose a different name, or drop the existing object with this name and then reissue the statement.
SQL 1057
1057 SQL/MX objects cannot be created on volume-name: File system error error-number.
Cause
An attempt to create a file on volume volume-name resulted in file system error error-number.
Effect
The operation fails.
Recovery
Apply the recovery of the accompanying error message.
SQL 1058
1058 Lock lock-name already exists.
Cause
The statement required creation of a lock with a unique lock name, which was not generated.
Effect
The operation fails.
Recovery
Specify a unique lock name and resubmit.
SQL 1059
1059 Request failed. Dependent constraint constraint-name exists.
Cause
You attempted to drop a table that has a referential constraint or a check constraint that refers to another table.
Effect
NonStop SQL/MX does not drop the table.
Recovery
Either drop all constraints that refer to other tables and then drop the table, or reissue the DROP TABLE statement, specifying the CASCADE option.
SQL 1061
1061 Dropping metadata catalog catalog-name is not allowed.
Cause
You attempted to drop a catalog that is part of the SQL/MX metadata.
Effect
The operation fails.
Recovery
None.
SQL 1062
1062 Dropping metadata schema schema-name is not allowed.
Cause
You attempted to drop a schema that is part of the SQL/MX metadata.
Effect
The operation fails.
Recovery
None.
SQL 1063
1063 Dropping metadata index index-name is not allowed.
Cause
An attempt was made to drop an index that is part of the SQL/MX metadata.
Effect
The operation fails.
Recovery
None.
SQL 1064
1064 Dropping metadata view tablename is not allowed.
Cause
An attempt was made to drop a view that is a metadata object. Metadata views and their creation are not currently supported, so this error should not be encountered.
Effect
The operation fails.
Recovery
None.
SQL 1065
1065 Creating constraint constraint-name in metadata schema is not allowed.
Cause
You attempted to create a constraint on a metadata table.
Effect
The operation fails.
Recovery
None.
SQL 1066
1066 Creating index index-name in metadata schema is not allowed.
Cause
You attempted to create an index on a metadata table.
Effect
The operation fails.
Recovery
None.
SQL 1069
1069 Schema schema-name could not be dropped.
Cause
See the accompanying error message for the cause of the problem.
Effect
The operation fails.
Recovery
Apply the recovery action from the accompanying error message.
SQL 1070
1070 Object object-name could not be created. File error: error-number.
Cause
An attempt to create object object-name resulted in file system error error-number.
Effect
The operation fails.
Recovery
Apply the recovery of the accompanying error message.
SQL 1071
1071 Object ANSI name could not be accessed.
Cause
The statement issued required access to the Guardian file underlying object ANSI name.
Effect
The operation fails.
Recovery
Apply the recovery action from the accompanying error message.
SQL 1072
1072 Unique constraint constraint-name-1 is disabled, so foreign key constraint constraint-name-2 could not be created.
-
Where,
-
constraint-name-1 is the name of the disabled constraint;
-
constraint-name-2is the name of the foreign key constraint.
Cause
You created a referential constraint that references a unique constraint that has been disabled. This is an internal error.
Effect
The operation fails.
Recovery
Create the referential constraint that references a unique constraint that has not been disabled.
SQL 1073
1073 Only super ID can execute INITIALIZE SQL.
Cause
You attempted to initialize NonStop SQL/MX, but you are not the super ID. Only the super ID can perform this function.
Effect
The operation fails.
Recovery
Log on as the super ID before executing this command.
SQL 1075
1075 The catalog must be empty. It contains at least one schema schema-name.
Cause
An attempt was made to drop a catalog that is not empty.
Effect
The catalog is not dropped. None of its schemas are dropped.
Recovery
Drop all schemas in the catalog and resubmit.
SQL 1077
1077 Metadata table table-name does not contain information for view view-name.
Cause
NonStop SQL/MX required metadata information about object view-name and was unable to find it in table-name.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1078
1078 The format of the specified location name ‘location-name' is not valid.
Cause
An invalid name was supplied in a LOCATION clause.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for limitations on names allowed in the LOCATION clause. Correct the name and resubmit.
SQL 1079
1079 SQL/MX was not able to prepare the statement.
Cause
See the accompanying error message for the cause.
Effect
The operation fails.
Recovery
Apply the recovery of the accompanying error message.
SQL 1080
1080 The DDL request has duplicate references to column column-name.
Cause
You attempted to create a table that has two columns with the same name. If you name a column "SYSKEY," duplication can result from the implicit creation by NonStop SQL/MX of a column named SYSKEY to ensure uniqueness for the clustering key.
Effect
The operation fails.
Recovery
Remove duplicate column names and resubmit.
SQL 1081
1081 Loading of index index-name failed unexpectedly.
Cause
Population of the index failed, either because another concurrent operation was being performed on the base table or because data could not be loaded into the index by the Call-level interface (CLI).
Effect
The operation fails.
Recovery
Determine the cause of the CLI failure and resubmit.
SQL1082
1082 Validation for constraint constraint-name failed unexpectedly.
Cause
The constraint validation failed, either because a concurrent operation was being performed on the table or on the referenced table (for a referential integrity constraint), or data in the table violates the constraint.
Effect
The constraint operation fails.
Recovery
If a concurrent operation is in progress, wait until it has finished and try the operation again. If data in the table violates the constraint, remove that data and resubmit.
SQL 1083
1083 Validation for constraint constraint-name failed; incompatible data exists in table.
Cause
Data in the table violates the check constraint.
Effect
The constraint operation fails.
Recovery
Remove data that violates the constraint from the table and resubmit.
SQL 1084
1084 An invalid default value was specified for column column-name.
Cause
An invalid default value was specified in the column definition for column-name.
Effect
Creation of the table or addition of the column fails.
Recovery
Specify a valid default value for the column and resubmit.
SQL 1085
1085 The calculated key length is greater than maximum-key-length.
Cause
The length of the primary key, which is calculated by the number of primary key columns and their data types, exceeds the maximum length.
Effect
The operation fails.
Recovery
Ensure that the key length is less than the maximum bytes allowed and resubmit. If a trigger is created on a table that has a primary key with a length greater than the maximum key length, error 1085 and error 1041 are returned.
SQL 1086
1086 Lock lock-name does not exist.
Cause
Lock lock-name was specified, but does not exist.
Effect
The operation fails.
Recovery
Create a lock lock-name or specify a valid lock name and resubmit.
SQL 1087
1087 DDL lock cannot be granted; invalid operation has been specified.
Cause
An invalid utility operation requested a DDL lock.
Effect
The lock request fails.
Recovery
Specify a valid utility operation, or check to see if invalid utilities are being run, and resubmit.
SQL 1088
1088 The system generated column SYSKEY must be specified last or not specified at all in the STORE BY column list.
Cause
If the system-generated column SKSKEY is specified in the STORE BY list of columns, it must be specified last.
Effect
The operation fails.
Recovery
Correct the STORE BY clause and resubmit.
SQL 1089
1089 The system generated column SYSKEY must be specified last or not specified at all in the index column list.
Cause
The system-generated SYSKEY column was not the last column in a CREATE INDEX statement.
Effect
The operation fails.
Recovery
Change the column list to place SYSKEY at the end of the list and resubmit the statement.
SQL 1090
1090 Self-referencing constraints are currently not supported.
Cause
You attempted to create a self-referencing constraint. A referential constraint is self-referencing if the foreign key is referencing the primary key of the same table.
Effect
The operation fails.
Recovery
Remove the self-reference and resubmit.
SQL 1094
1094 Object object-name could not be dropped because it is not of type object-type.
-
Where,
-
object-name is the ANSI name of the object stated in the DROP command;
-
object-type is the type of object that was stated in the DROP command.
Cause
A DROP TABLE specified an object that is not a base table, or a DROP VIEW specified an object that is not a view, or a DROP PROCEDURE specified an object that is not a procedure.
Effect
The operation fails.
Recovery
Reissue the DROP statement with the correct combination of specified object type and actual object type.
SQL 1095
1095 The PARTITION BY column column-name should also be part of the clustering/storage key.
Cause
This error is reported if a column specified in the partitioning key of the "PARTITION BY (partitioning_columns>)" clause of a CREATE TABLE or CREATE INDEX statement is not also a member of the clustering key.
Effect
The table or index is not created.
Recovery
Either remove the offending column from the partitioning key specification (and possibly replace it with a column that is a member of the clustering key) or add the offending column to the clustering key by using the STORE BY clause or by adding it to the primary key.
SQL 1098
1098 Partition key (key) already specified for object object-name.
Cause
You attempted to create or change a table so that more than one partition has the same first key.
Effect
The operation fails.
Recovery
Change the statement so that it does not define two partitions to have the same first key, and resubmit.
SQL 1099
1099 Column column-number is unnamed. You must specify an AS clause for that column expression, or name all the columns by specifying a view column list.
Cause
You attempted to create a view by using a query expression in which column-number was unnamed.
Effect
The operation fails.
Recovery
Correct the statement to supply an AS clause for each unnamed column and resubmit.
SQL 1100
1100 Table table-name could not be selected.
Cause
See the accompanying error message for clarification.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1101
1101 Table table-name could not be updated.
Cause
See the accompanying error message for clarification.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1102
1102 Rows could not be inserted into table table-name.
Cause
See the accompanying error message for clarification.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL1103
1103 Rows could not be deleted from table table-name.
Cause
See the accompanying error message for clarification.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1104
1104 Default value string is too long for column column-name.
Cause
The specified default value for column-name is longer than the maximum of 239 characters.
Effect
The operation fails.
Recovery
Correct the error and resubmit.
SQL 1105
1105 CREATE TABLE LIKE statement cannot contain both HORIZONTAL PARTITIONS and STORE BY clauses.
Cause
A CREATE TABLE...LIKE statement specifies both the WITH PARTITIONS and STORE BY clause, which is not allowed.
Effect
The operation fails.
Recovery
Correct the error and resubmit.
SQL 1106
1106 The specified partition partition-location of object table-name does not exist.
-
Where,
-
partition-location is the location of the specified partition;
-
table-name is the name of the table.
Cause
The location name partition-location specified in the partition operation does not exist.
Effect
The partition operation fails.
Recovery
Specify a valid partition location name and resubmit.
SQL 1108
1108 The number of columns specified in the view column list, view-col-num, does not match the degree of the query expression, query-col-num.
-
Where,
-
view-col-num is the number of columns in the view column list;
-
query-col-num is the number of columns resulting from the query expression used to define the view.
Cause
The number of columns in the query do not equal the number of columns specified for the view.
Effect
The operation fails.
Recovery
Specify a query statement that has a degree that matches the number of columns in the view column list, and resubmit.
SQL 1109
1109 The WITH CHECK OPTION clause appears in the definition of view view-name, but the view is not updatable.
Cause
You used WITH CHECK OPTION in the definition of a view that is not updatable.
Effect
The operation fails.
Recovery
Either make the view updatable or omit the WITH CHECK OPTION and resubmit.
SQL 1111
1111 An error occurred while starting a transaction on object table-name.
Cause
The transaction could not be started, possibly due to another transaction being active on the object.
Effect
The operation fails.
Recovery
Determine why the transaction failed and resubmit.
SQL 1112
1112 An index column list cannot contain only the system-generated column SYSKEY.
Cause
The column list specified in a CREATE INDEX statement consisted only of the system-generated column SYSKEY.
Effect
The operation fails.
Recovery
Change the column list to include additional columns and reissue the statement.
SQL 1114
1114 Metadata tables for catalog catalog-name could not be created on location-info.
-
Where,
-
catalog-name is the name of an SQL/MX catalog;
-
location-info is the location where the tables could not be created.
Cause
This error can result from various CREATE statements issued to create the metadata. See the accompanying error messages to determine the cause.
Effect
One or more objects are not created.
Recovery
See the accompanying error messages for recovery action.
SQL 1115
1115 Label Guardian name could not be created for ANSI name (file error error).
-
Where,
-
Guardian name is the name of the Guardian file for the label creation that failed;
-
ANSI name is the name of the table;
-
error is the error number returned.
Cause
A file system error occurred on the attempt to create the label.
Effect
The table is not created.
Recovery
Correct the file system error and reissue the CREATE statement.
SQL 1116
1116 The current partitioning scheme requires a user-specified clustering key on object table-name.
Cause
The partitioning scheme requires a user-specified clustering key.
Effect
The operation fails.
Recovery
Specify a clustering key, either through a PRIMARY KEY, STORE BY, or PARTITION BY clause.
SQL 1117
1117 Dropping the only partition of an object is not allowed. At least two partitions must exist to perform the drop.
Cause
You attempted to drop the only partition of the object.
Effect
The operation fails.
Recovery
None.
SQL 1118
1118 Creating object table-name is not allowed in metadata schema.
Cause
You attempted to create an object in the metadata schema.
Effect
The operation fails.
Recovery
Specify a different schema and resubmit.
SQL 1119
1119 Dropping metadata object table-name is not allowed.
Cause
You attempted to use the DROP TABLE statement to drop a table that is part of SQL/MX metadata.
Effect
The table is not dropped.
Recovery
Metadata tables can be dropped only by using the DROP SQL statement or the MXTOOL GOAWAY utility. Both methods will irrevocably destroy the database.
SQL 1120
1120 Use of float datatype in a partitioning key is not allowed.
Cause
You attempted an operation on a partitionable table that has float datatype in the partitioning key.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1121
1121 Partitions cannot be added or dropped on table table-name. These partition operations are not allowed on tables whose clustering key consists only of the SYSKEY.
Cause
You attempted to do an invalid ADD, DROP, or MODIFY of a partition.
Effect
The operation fails.
Recovery
None.
SQL 1122
1122 The number of specified partition key values (partition-key-value-list) for object object-name exceeds the number of user defined key columns, key-col-number.
-
Where,
-
partition-key-value-list is a list of the partition key values;
-
object-name is the name of the object;
-
key-col-number is the number of columns in the user-defined key.
Cause
The number of specified partition key values (partition-key-value-list) for object object-name exceeds the number of user-defined key columns, key-col-number.
Effect
The operation fails.
Recovery
Fix the statement and resubmit.
SQL 1123
1123 Not all of the partition key values (key) for object object-name could be processed. Please verify that the correct key value data types were specified.
Cause
You attempted to access a table using a first key value that contains an element that is not supported.
Effect
The operation fails.
Recovery
Correct the syntax and resubmit.
SQL 1125
1125 API request version number mismatch.
Cause
This is an internal error.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1126
1126 Operation cannot be performed because object is not an SQL/MP alias.
Cause
You attempted to perform an operation that is specific to MP aliases on an object that is not an MP alias.
Effect
The operation fails.
Recovery
Specify an object that is an SQL/MP alias and resubmit.
SQL 1127
1127 The specified table table-name is not a base table. Please verify that the correct table was specified.
Cause
You attempted to perform an operation that can be performed only on a base table, and the specified object is not a base table.
Effect
The operation fails.
Recovery
Specify a valid base table and resubmit.
SQL 1128
1128 An invalid API request was encountered. Details: description.
Cause
Internal error.
Effect
NonStop SQL/MX is unable to perform the requested operation.
Recovery
None. Report the entire message to your service provider.
SQL 1130
1130 The column requires a default value.
Cause
You attempted to create a column that requires a default value, without specifying a default value.
Effect
The operation fails.
Recovery
Specify a valid default value for the column and resubmit.
SQL 1132
1132 An added column cannot have DEFAULT NULL and NOT NULL at the same time.
Cause
You attempted to add a column that is both DEFAULT NULL and NOT NULL.
Effect
The operation fails.
Recovery
Determine whether the column should be DEFAULT NULL or NOT NULL and resubmit.
SQL 1133
1133 Only super ID can perform this operation.
Cause
You attempted to perform an operation that can be performed only by the super ID.
Effect
The operation fails.
Recovery
Log on as the super ID and then resubmit.
SQL 1134
1134 A concurrent utility or DDL is being performed on object object-name, its parent, or one of its dependencies. That operation must complete before the requested operation can run.
Cause
You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object, its parent, or its dependencies.
Effect
The operation fails.
Recovery
Wait until the concurrent operation has finished and then resubmit.
SQL 1135
1135 Clustering key column column-name must be assigned a NOT NULL NOT DROPPABLE constraint.
Cause
You attempted to make a column that is not NOT NULL NOT DROPPABLE a part of the clustering key of a table.
Effect
The operation fails.
Recovery
Specify that the column-name is NOT NULL NOT DROPPABLE and resubmit.
SQL 1136
1136 For an added column, the PRIMARY KEY clause cannot specify NOT DROPPABLE.
Cause
You used the ALTER TABLE statement to add a column specifying a primary key that is not droppable. A primary key added through ALTER TABLE must be droppable.
Effect
The operation fails.
Recovery
Change the ALTER TABLE statement to specify DROPPABLE for the primary key.
SQL 1137
1137 An internal error occurred: invalid index status. Details: description.
Cause
This is an internal error in the interface between utilities and the catalog manager.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1138
1138 An internal error occurred: invalid input parameter(s). Object name and status are required.
Cause
This is an internal error in the interface between utilities and the catalog manager.
Effect
The operation fails.
Recovery
None. Contact your service provider.
SQL 1139
1139 System-generated column column-name of base table table-name cannot appear in the search condition of a check constraint definition.
-
Where,
-
column-name is the name of a column of table-name;
-
table-name is the name of the affected table.
Cause
You attempted to create a check constraint that references a system-generated column. The column named SYSKEY is often system-generated.
Effect
The operation fails.
Recovery
Modify the statement so that no check constraints reference any system-generated column and resubmit.
SQL 1140
1140 Row-length
actual-row-length exceeds the maximum allowed row-length of
maximum-row-length for
table-or-indexname
.
-
Where,
-
actual-row-length is the length of a row of the table or index;
-
maximum-row-length is the largest row size allowed;
-
name is the name of the table or index.
Cause
On a CREATE or ALTER TABLE statement or a CREATE INDEX statement, the size of the row exceeds the maximum allowed row size.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for row size limit calculations. Change the column definitions and reissue the statement.
SQL 1141
1141 Label file-name for object could not be accessed. File system error error-number.
-
Where,
-
file-name is the Guardian file name of a partition of object;
-
error-number is a Guardian file system error.
Cause
An ALTER TABLE or ALTER INDEX operation encountered a file system error.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1142
1142 Because it is not audited, this table cannot have a column added that is declared NOT NULL, or has a CHECK, UNIQUE, PRIMARY KEY, or FOREIGN KEY constraint.
Cause
Internal error.
Effect
NonStop SQL/MX is unable to perform the requested operation.
Recovery
None. Contact your service provider.
SQL 1143
1143 Validation for constraint constraint-name failed; incompatible data exists in referencing base table referencing-table-name and referenced base table referenced-table-name. To display the data that violates the constraint, please use the following DML statement: statement-text.
-
Where,
-
constraint-name is the name of a column constraint or table constraint;
-
referencing-table-name is the table on which the constraint is being added;
-
referenced-table-name is the table specified in the FOREIGN KEY clause.
-
statement-text is a query.
Cause
You attempted to add a referential integrity constraint that is violated by rows already in the table.
Effect
The operation fails.
Recovery
Run the query statement-text to see the rows that violate the referential constraint. Either change those rows or change the referential constraint definition and resubmit.
SQL 1144
1144 A quoted string was expected in first key clause for column column-name on table table-name, but the value detected is (first-key-string).
-
Where,
-
column-name is the column in table-name;
-
table-name is the name of the table;
-
first-key-string is the erroneous value used in the FIRST KEY clause for column-name.
Cause
In a CREATE TABLE statement, a value specified as first key is not a quoted string, but the type of the column for which this value is specified is one of the character data types.
Effect
The operation fails.
Recovery
Correct the value first-key-string to be a type that is compatible with the type of column column-name and resubmit.
SQL 1145
1145 The catalog name catalog-name is reserved for SQL/MX matadata.
Cause
NonStop SQL/MX reserves certain catalog names for its own use.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for reserved names. Change catalog-name to a name that is not reserved and resubmit.
SQL 1146
1146 Object object-name could not be altered because it is not a object-type.
-
Where,
-
object-name is the name of the object being requested;
-
object-type is the type of object required for the DDL statement issued.
Cause
The type of the object specified in the command is inconsistent with the DDL command being used. For example, this occurs if DROP TABLE is used, and the object you specify is an INDEX.
Effect
The operation fails.
Recovery
Check that the correct object name was specified and execute a statement that is consistent with that type of object.
SQL 1147
1147 System-generated column column-name of base table table-name cannot appear in a unique or primary key constraint.
Cause
You tried to create a unique or primary key constraint on the SYSKEY column.
Effect
The operation fails.
Recovery
Do not use the SYSKEY as part of the unique or primary key.
SQL 1148
1148 System-generated column column-name of base table table-name cannot appear in a referential integrity constraint definition.
Cause
You tried to create a referential constraint on a table column that is the SYSKEY, which is not supported.
Effect
The operation fails.
Recovery
Do not use the SYSKEY as part of the referenced key.
SQL 1150
1150 Table table-name was not created because Partition Overlay Support could not generate volume names for the partitions to reside on.
Cause
When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, NonStop SQL/MX could not generate the location names automatically and, because the CQD POS_RAISE_ERROR is set, the table is not created.
Effect
The operation fails.
Recovery
To correct the error, choose a recovery method:
-
Verify that the disk volumes are available on the current node and retry the request.
-
Specify the volume names where the partitions need to be created for the given CREATE TABLE statement through CONTROL QUERY DEFAULT POS_LOCATIONS, and then retry the request.
-
Do not set the CQD POS_RAISE_ERROR, in which case, a simple table without partitions is created when the volume names cannot be generated.
SQL 1151
1151 POS (Partition Overlay Support) was not applied because volume names could not be generated for the partitions. So a simple table table-name was created without partitions.
Cause
When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, NonStop SQL/MX could not generate the location names automatically, and because the CQD POS_RAISE_ERROR is not set, the given table is created as a simple table without partitions as it would be if the Partition Overlay Support feature was not enabled.
Effect
The POS feature was not applied. A simple table without partitions was created.
Recovery
None if a nonpartitioned table is requested. To request a partitioned table, delete the table, verify that disk volumes are available, and resubmit. You can also specify the volume names where the partitions need to be created for the given CREATE TABLE through CONTROL QUERY DEFAULT POS_LOCATIONS, and then retry the request.
SQL 1154
1154 Cannot create object object-name as the table size is too big to fit on the system.
Cause
NonStop SQL/MX could not create the object because the requested table size is bigger than the total amount of disk space available on the cluster.
Effect
The SQL operation fails.
Recovery
Check that the table size requested fits the cluster, and then retry the statement.
SQL 1158
1158 Object name already exists.
Cause
You specified a create of synonym name on an object, but an object of that name already exists.
Effect
The operation fails.
Recovery
Correct the syntax so that the correct name is used.
SQL 1159
1159 name does not exist.
Cause
You specified an alter or drop of synonym name, but a synonym of that name does not exist.
Effect
The operation fails.
Recovery
Correct the syntax so that the correct name is used.
SQL 1160
1160 A mismatch between the NOT DROPPABLE PRIMARY KEY constraint and the STORE BY clause was detected. When both clauses are specified, the STORE BY key column list must be the same as, or a prefix of, the PRIMARY KEY column list. This mismatch is caused by differences between the columns themselves, the order of columns, or the ASC/DESC attribute.
Cause
You attempted to create a table that contains both a NOT DROPPABLE PRIMARY KEY constraint and a STORE BY clause. The syntax specified is not correct. The STORE BY column list must be the same as, or a prefix of, the NOT DROPPABLE PRIMARY KEY column list.
Effect
The operation fails.
Recovery
If you want the STORE BY column list that specifies the clustering key to be different than the PRIMARY KEY, specify a DROPPABLE PRIMARY KEY. If you want the PRIMARY KEY to be the same as the STORE BY key, do not specify a STORE BY clause. Correct the syntax and resubmit.
SQL 1162
1162 User user-name already owns object-type object-name. Operation ignored.
-
Where,
-
user-name is a valid Guardian username;
-
object-type is CATALOG or SCHEMA or TABLE or TRIGGER or VIEW or PROCEDURE;
-
object-name is CATALOG or SCHEMA or TABLE or TRIGGER or VIEW or PROCEDURE name.
Cause
The object object-name is already owned by the user user-name.
Effect
The operation fails.
Recovery
Not applicable.
SQL 1165
1165 Parallel operation operation failed on table-name. The serial operation for this object will be performed.
Cause
An error occurred on the DDL operation when using the parallel method. The DDL operation is retried using the serial method.
Effect
The label create, drop, or alter operation that is part of the DDL statement is performed serially, rather than in parallel. The serial method decreases performance compared to the parallel method.
Recovery
No corrective action is necessary. This message is a warning.
SQL 1168
1168 Internal error: unable to find object associated with UID uid.
Cause
Object not found by the specified UID.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 1174
1174 An invalid data type was specified for column column-name.
Cause
The data type specification for a column is missing.
Effect
The command fails.
Recovery
Specify a data type for the column.
SQL 1176
1176 Column column-name has DEFAULT NULL and cannot be referenced by NOT DROPPABLE constraint constraint-name.
Cause
You attempted to create a table with a column that has DEFAULT NULL, and which is referenced by an IS NOT NULL predicate in a NOT DROPPABLE check constraint.
Effect
The operation fails.
Recovery
Determine whether the column should be DEFAULT NULL or NOT NULL and resubmit.
SQL 1177
1177 SELECT cannot be revoked from the executable of a stored routine if the authorization ID has EXECUTE authority.
Cause
You attempted to REVOKE SELECT privilege on the EXECUTABLE from a user who has EXECUTE privilege for the target function. If a user has EXECUTE privilege on a function, the user must also have SELECT on the EXECUTABLE.
Effect
The operation fails.
Recovery
Remove SELECT privilege from the EXECUTABLE using REVOKE EXECUTE on the function from the user.
SQL 1178
1178 Internal error: unable to find catalog associated with uid uid-name.
Cause
An internal error was encountered.
Effect
The operation fails.
Recovery
Contact Hewlett Packard Enterprise support to analyze the failure.
SQL 1180
1180 The required subvolume name for locations in schema schema-name is subvol-name.
-
Where,
-
schema-name is the schema in which the object is being created;
-
subvol-name is the designated subvolume name for that schema.
Cause
One or more LOCATION clauses in the CREATE or MODIFY statement contained a Guardian location whose subvolume did not match the designated subvolume for the schema in which the object was being created.
Effect
The object was not created.
Recovery
Either correct the invalid LOCATION clauses or remove them and allow the system to generate the Guardian locations.
SQL 1181
1181 Label Guardian name could not be dropped. (file error error).
-
Where,
-
Guardian name is the name of the table, index, view, or routine being dropped;
-
error is the returned file-system error number.
Cause
The object you attempted to drop resulted in file system error error.
Effect
The DDL DROP operation fails.
Recovery
See previous messages in this SQL/MX operation to determine the necessary corrective actions. Also, use the file system error error-number to analyze the cause. Fix the error and resubmit.
SQL 1182
1182 Error error was returned by the file system on resource fork Guardian name.
Cause
See the Guardian Procedure Errors and Messages Manual for a description of file system error error.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1183
1183 Error error was returned by the file system on metadata table ANSI name (file name Guardian name).
-
Where,
-
error is the error returned;
-
ANSI name is the metadata table;
-
Guardian name is the name of the file.
Cause
See the Guardian Procedure Errors and Messages Manual for a description of file system error error.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1184
1184 You do not have the required privilege(s) on column-name.
-
Where,
-
column-name is the name of a column specified in the references part of a referential integrity constraint.
Cause
You attempted to establish a referential integrity constraint on a column for which the executing user ID has no REFERENCES privileges.
Effect
The operation fails.
Recovery
Establish correct column privileges and resubmit.
SQL 1185
1185 The location name is either invalid or missing.
Cause
A partition location is either invalid or missing.
Effect
The operation fails.
Recovery
Specify the correct location for all partitions involved in the affected command.
SQL 1186
1186 Column column-name is of type column-data-type which is not compatible with the default value's type, value-data-type.
-
Where,
-
column-name is the name of the column that has an error.
-
column-data-type is the data type of column-name.
-
value-data-type is the value specified as the default value for the column.
Cause
The value specified as the default for the column is incompatible with the type of the column.
Effect
The operation fails.
Recovery
Change either the column data type or the value for the default to be compatible types and resubmit.
SQL 1187
1187 The schema name schema-name is reserved for SQL/MX metadata.
Cause
NonStop SQL/MX reserves certain schema names for its own use.
Effect
The operation fails.
Recovery
See the SQL/MX Reference Manual for reserved schema names. Choose a name that is not reserved and reissue the CREATE statement.
SQL 1188
1188 Referential integrity constraint constraint-name for table table-name could not be created due to circular dependency: dependency-information.
-
Where,
-
constraint-name is the name of a column constraint or table constraint;
-
table-name is the name of the table specified in the operation;
-
dependency-information is a list of unique constraints that cause the circular dependency.
Cause
You tried to define a referential constraint that is creating a circular dependency, where one of the columns of the table is referencing a column that belongs to the same table, either directly or indirectly.
Effect
The operation fails.
Recovery
None. You cannot define a referential constraint that creates a circular dependency.
SQL 1189
1189 The number clustering key columns for table-or-index exceeds maximum-number-key-columns.
-
Where,
-
maximum-number-key-columns is the maximum number of key columns. For SQL/MX R 3.0, the value is maximum-number-key-columns 1024.
Cause
The number of columns specified in the primary key or index columns exceeds the maximum number allowed.
Effect
The operation fails.
Recovery
Ensure that the number of key columns or index columns is less than the maximum limit and resubmit.
SQL 1190
1190 SQL/MP system catalog catalog-locationcould not be found - error error-number.
-
Where,
-
catalog-location is a name of the form $vol.sql.catalogs;
-
error-number identifies the error encountered.
Cause
Unable to locate the device for the SQL/MP system catalog or the label of $vol.sql.catalogs.
Effect
The operation fails.
Recovery
Check that the devices for the SQL/MP system catalog and the file $vol.sql.catalogsexist. If they do, contact your service provider.
SQL 1191
1191 SQL/MP system catalog catalog-location could not be found - DEVICE_GETINFOBYLDEV error error-number.
-
Where,
-
catalog-location is a name of the form $vol.sql.catalogs;
-
error-number identifies the error encountered.
Cause
Unable to find SQL/MP system catalog table $vol.sql.catalogs.
Effect
The SQL/MX operation fails with an error.
Recovery
Check that the SQL/MP system catalog table $vol.sql.catalogs exists. If it does, contact your service provider.
SQL 1192
1192 SQL/MP system catalog catalog-location could not be found -FILE_GETINFOBYNAME_ error error-number.
-
Where,
-
catalog-location is a name of the form $vol.sql.catalogs;
-
error-number identifies the error encountered.
Cause
Unable to find SQL/MP system catalog table $vol.sql.catalogs.
Effect
The operation fails.
Recovery
Check that the SQL/MP system catalog table $vol.sql.catalogs exists. If it does, contact your service provider.
SQL 1193
1193 Internal first key size is size bytes; it exceeds the maximum of limit bytes.
Cause
The internal form of a first key specification for a partition is larger than the metadata can accommodate.
Effect
The operation fails.
Recovery
Reduce the size of the first key specification and then resubmit.
SQL 1195
1195 The number of columns for table-or-index exceeds the maximum limit of max-no-of-columns.
Cause
The number of columns for table-or-indexis higher than the permitted maximum. For SQL/MX R 3.0, the maximum is 2100.
Effect
The operation fails.
Recovery
Reduce the number of columns and then resubmit.
SQL 1196
1196 The SQL/MP system catalog catalog-name could not be found due to an invalid SQL/MP location name.
Cause
An invalid SQL/MP system catalog location was specified or defaulted to.
Effect
The operation fails.
Recovery
Specify a correct SQL/MP system catalog location, or set the Guardian default system and volume to valid values.
SQL 1197
1197 SQL/MP object name sqlmp-name is not valid.
Cause
You specified an invalid SQL/MP object name.
Effect
The operation fails.
Recovery
Specify a correct SQL/MP object name and resubmit.
SQL 1221
1221 SQL/MP alias for file file-name could not be created. File system error: error-number.
-
Where,
-
file-name is the Guardian file name specified in the CREATE SQL/MP ALIAS command;
-
error-number is the Guardian file-system error number.
Cause
NonStop SQL/MX was unable to obtain file information about file-name.
Effect
The operation fails.
Recovery
Use the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1222
1222 The file type for file file-name is not valid.
Cause
You specified a Guardian file name that is not an SQL/MP database object.
Effect
The operation fails.
Recovery
Specify a Guardian file name for the SQL/MP database object.
SQL 1223
1223 Optimizer hints are not allowed in statement-name statement.
Cause
You specified optimizer hints in the text of a statement.
Effect
The operation fails.
Recovery
Remove the optimizer hints and resubmit the statement.
SQL 1224
1224 An invalid data type was specified for routine parameter parameter-name.
Cause
You specified a data type for this routine parameter that is not supported.
Effect
NonStop SQL/MX is unable to complete the operation.
Recovery
Specify a different data type.
SQL 1225
1225 Mixing priv-type privilege with other privileges is not allowed.
Cause
A privilege other than EXECUTE/USAGE is specified in the same GRANT or REVOKE statement, which is not allowed.
Effect
The operation fails.
Recovery
Use separate GRANT or REVOKE statements for EXECUTE/USAGE and other privileges.
SQL 1226
1226 No valid combination of privileges was specified.
Cause
The GRANT or REVOKE statement did not specify a valid combination of privileges.
Effect
The operation fails.
Recovery
Specify a valid combination of privileges in the GRANT or REVOKE statement.
SQL 1231
1231 User-defined routine procedure-name could not be created.
Cause
The stored procedure could not be created.
Effect
The CREATE PROCEDURE statement fails.
Recovery
Fix the error conditions identified in messages preceding this message and reissue the CREATE PROCEDURE statement.
SQL 1232
1232 A file error occurred when saving dropped table DDL for table table-name to oss-pathname.
-
Where,
-
table-name is the table being dropped whose DDL was to be saved;
-
oss-pathname is the HPE NonStop Kernel Open System Services (OSS) pathname of the file to which the DDL was to be saved.
Cause
An OSS file system error occurred when you attempted to save a table DDL. Possible reasons are:
-
The directory /usr/tandem/sqlmx/ddl did not exist or could not be created.
-
The system did not have write access to /usr/tandem/sqlmx/ddl.
-
Insufficient OSS file space was available.
Effect
The table is not dropped.
Recovery
Either correct the file system problem and drop the table or perform a SHOWDDL on the existing table, capture the output, set. SAVE_DROPPED_TABLE_DDL to "OFF," and drop the table.
SQL 1233
1233 Creating schema in SQL/MX system catalog catalog-name is prohibited.
Cause
You attempted to create a schema in the system catalog.
Effect
The operation fails.
Recovery
Choose a different catalog name and reissue the CREATE statement.
SQL 1234
1234 SQL/MP object object-name is the same as previous mapping.
Cause
An ALTER SQL/MP ALIAS command specified the same SQL/MP database object as was previously mapped.
Effect
The operation succeeds. This is a warning message only.
Recovery
None.
SQL 1235
1235 An invalid combination of EXTENT sizes and MAXEXTENTS was specified for table or index table-name.
Cause
A CREATE or ALTER statement specified an invalid combination of EXTENT sizes and MAXEXTENTS.
Effect
The operation fails.
Recovery
Correct the error and retry the operation.
SQL 1236
1236 The schema name specified for SQL object object-name is not valid. The schema name must be the same as the schema being created.
Cause
You specified a schema name for an object that is different from the name of the schema being created.
Effect
The operation fails.
Recovery
Specify a schema name for the object that matches the name of the schema being created.
SQL 1237
1237 SQL/MP alias for file-name could not be altered. File system error: error-number.
-
Where,
-
file-name is the Guardian file name specified in the ALTER SQL/MP ALIAS command;
-
error-number is the Guardian file-system error number.
Cause
NonStop SQL/MX was unable to obtain file information about file-name.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1238
1238 The character set used in TRIGGER text must be ISO88591.
Cause
You specified a literal with a character set other than ISO88591 in the text of a create trigger statement.
Effect
The operation fails.
Recovery
Specify only ISO88591 literals in the command.
SQL 1239
1239 The character set used for string literals in VIEW must be ISO88591.
Cause
You specified a literal with a character set other than ISO88591 in the text of a create view statement.
Effect
The operation fails.
Recovery
Specify only ISO88591 literals in the command.
SQL 1240
1240 The character set for a PARTITION KEY column must be ISO88591.
Cause
You specified a literal with a character set other than ISO88591 as a partition key.
Effect
The operation fails.
Recovery
Specify only ISO88591 literals as partition keys.
SQL 1241
1241 The character set for HEADING must be ISO88591.
Cause
You specified a literal with a character set other than ISO88591 in a HEADING clause.
Effect
The operation fails.
Recovery
Specify only ISO88591 literals in HEADING clauses.
SQL 1242
1242 The character set for string literals in CONSTRAINT must be ISO88591.
Cause
You specified a literal with a character set other than ISO88591 in the text of a constraint.
Effect
The operation fails.
Recovery
Specify only ISO88591 literals in constraints.
SQL 1243
1243 The hexadecimal form of string literals is not allowed in this context.
Cause
You specified a hexadecimal literal in the text of the statement, which is not allowed.
Effect
The operation fails.
Recovery
Do not specify hexadecimals in this type of command.
SQL 1244
1244 This operation is not allowed because object name is a SQL/MP object.
Cause
You specified a Guardian type name for an SQL operation that does not support SQL/MP objects.
Effect
The operation fails.
Recovery
Either repeat the operation using a valid ANSI name or perform the operation in SQL/MP using the Guardian type name.
SQL 1245
1245 The supplied partition key value (key-value) for column column-name of object object-name is not valid.
-
Where,
-
key-value is the specified first key value;
-
column-name is the column of object-name that corresponds to the invalid key value.
-
object-name is the name of the affected object.
Cause
A utility command specified an invalid key value.
Effect
The operation fails.
Recovery
Specify valid key values and resubmit.
SQL 1246
1246 The supplied partition key value (key-value) is inconsistent with the data type of column column-name of object object-name.
-
Where,
-
key-value is the specified first key value;
-
column-name is the column of object-name that corresponds to the invalid key value.
-
object-name is the name of the affected object.
Cause
A utility command specified a key value that is inconsistent with the data type of the column that corresponds to the key value.
Effect
The operation fails.
Recovery
Specify valid key values and resubmit.
SQL 1248
1248 Partition name partition-name has already been used. Each partition in an object should have a unique name.
Cause
Partition names are required to be unique within the set of partitions of an object.
Effect
The CREATE statement fails.
Recovery
Choose a name that is not the same as any other partition name in this object and reissue the CREATE statement.
SQL 1249
1249 Insert into log-table-name log table failed.
Cause
Insert into one of the translation log tables has failed. The log-table-name specifies the translation log table where the insert failed.
Effect
The UPGRADE operation failed.
Recovery
RECOVER must be used to recover from the UPGRADE operation failure. Before attempting the UPGRADE operation again, the failure of insert intolog-table-name has to be corrected.
SQL 1250
1250 DROP cannot be performed on object object-name because a utility operation (operation-type) associated with DDL_LOCK lock-name is currently running.
-
Where,
-
object-name is the ANSI name of the object named in the DROP command;
-
operation-type is the type of utility operation;
-
lock-name is the ANSI name of the DDL lock object that is associated with the utility operation.
Cause
You attempted to drop an object that a utility command is using.
Effect
The operation fails.
Recovery
Wait until the utility operation has finished, and then retry the DROP operation.
SQL 1251
1251 The extra insignificant digits of default value value are truncated to match the scale of the data type of column column-name.
-
Where,
-
value is the default value that was specified for column-name;
-
column-name is the name of the column in the table.
Cause
A CREATE TABLE or ALTER TABLE...ADD COLUMN specified a default value with a scale greater than the scale of the column.
Effect
The scale of the default value is set to that of the column; extra digits to the right are discarded.
Recovery
None. This is a warning message only.
SQL 1252
1252 The existing index index-name to be used by a unique or primary constraint has not been populated. Please populate the index and then try to add the constraint again.
Cause
An existing index that is not populated has been chosen for a unique or primary constraint, which is not allowed.
Effect
The operation fails.
Recovery
Populate the index and resubmit.
SQL 1254
1254 Duplicate unique constraints are not allowed with same set of columns.
Cause
You attempted to specify both the unique and primary key constraints or multiple unique constraints on the same set of columns, which is not allowed.
Effect
The operation fails.
Recovery
Change your query so that both unique and primary constraints or multiple unique constraints are not specified on the same set of columns.
SQL 1261
1261 Error error-number was returned by the SQL/MX CLI while processing the UDR_JAVA_OPTIONS setting jvm-startup-options.
-
Where,
-
error-number is the SQLCODE value;
-
jvm-startup-options is a set of Java Virtual Machine startup options, specified in the application's UDR_JAVA_OPTIONS default setting.
Cause
An unanticipated error occurred during a CREATE PROCEDURE operation.
Effect
The operation fails.
Recovery
Retry the operation. If the operation continues to fail, contact your service provider.
SQL 1262
1262 The command cannot be executed because operation is in progress for schema.
Cause
You attempted a DDL or utility operation on a database object while a schema-level operation was in progress for that object's schema or a previously attempted DDL or utility operation had failed.
Effect
The DDL or utility operation fails.
Recovery
-
Wait until the operation has finished, and then retry the DDL or utility operation.
-
For a failed schema level operation, run RECOVER SCHEMA with RESUME or CANCEL option to complete or cancel the failed schema level operation and retry the DDL or utility operation.
SQL 1263
1263 Object names that start with text are reserved for SQL/MX metadata.
Cause
You specified an SQL/MX reserved object name.
Effect
The object is not created.
Recovery
See the SQL/MX Reference Manual for the list of reserved object names. Choose a name that is not reserved and reissue the CREATE statement.
SQL 1264
1264 Duplicate privileges are not allowed in a GRANT or REVOKE statement.
Cause
You specified duplicate privileges in a GRANT or REVOKE statement.
Effect
The operation fails.
Recovery
Reissue the GRANT or REVOKE statement, specifying a single privilege or a list of distinct privileges.
SQL 1265
1265 Duplicate grantees not allowed in a GRANT or REVOKE statement.
Cause
You specified duplicate grantees in a GRANT or REVOKE statement.
Effect
The operation fails.
Recovery
Reissue the GRANT or REVOKE statement specifying a single grantee or a list of distinct grantees.
SQL 1266
1266 Only priv-type privilege is supported for a object-type.
Cause
You specified an unsupported privilege on a procedure or a routine or a sequence in a GRANT statement.
Effect
The operation fails.
Recovery
Resubmit the GRANT statement specifying the valid privilege for the procedure or routine or sequence.
SQL 1267
1267 EXECUTE privilege is incompatible with this object type.
Cause
You specified a privilege that is not supported for the object type in a GRANT statement.
Effect
The operation fails.
Recovery
Reissue the GRANT statement specifying the valid privilege for the object type.
SQL 1268
1268 Duplicate columns are not allowed in a GRANT or REVOKE statement.
Cause
You specified duplicate column names with the update or references privilege in a GRANT or REVOKE statement.
Effect
The operation fails.
Recovery
Correct the GRANT or REVOKE statement by specifying a single column name or a list of distinct column names.
SQL 1269
1269: Column level privileges cannot be granted or revoked on a schema.
Cause
You specified column level privileges on a schema in a GRANT or REVOKE statement.
Effect
The operation fails.
Recovery
Reissue the GRANT or REVOKE statement on the schema without any column specification.
SQL 1270
1270 ALLOCATE or DEALLOCATE failed for object sql object-name due to file error file-system error-number on filename.
-
Where,
-
sql object-name is the ANSI name of the affected SQL database object;
-
file-system error-number is a Guardian file system error code.
Cause
A CREATE or ALTER operation encountered a file system error error-number during processing of the ALLOCATE or DEALLOCATE attribute.
Effect
The operation fails.
Recovery
See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
SQL 1271
1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object.
-
Where,
-
object-name is the ANSI name of the affected database object;
-
number is the specified number of extents.
Cause
A CREATE or ALTER operation specified an ALLOCATE attribute value that was greater than the MAXEXTENTS value for the affected database object, which is not allowed.
Effect
The operation fails.
Recovery
If possible, alter the MAXEXTENTS attribute value to be greater than the desired number of extents to be allocated. The current maximum value for MAXEXTENTS is 768.
SQL 1272
1272 The system is not licensed for use of SQL/MX format tables.
Cause
The site has not purchased DDL Licensing.
Effect
The operation fails.
Recovery
Purchase DDL Licensing (product number T0394).
SQL 1273
1273 The specified MAXEXTENTS value must be greater than the number of extents allocated.
Cause
The value that you specified to change MAXEXTENTS is less than or equal to the allocated extents.
Effect
The operation fails.
Recovery
Use a MAXEXTENTS value greater than the allocated extents.
SQL 1274
1274 The specified or default MAXEXTENTS value is not sufficient. The MAXEXTENTS value has been automatically set to the new value of newextentvalue for the file filename.
Cause
You specified an insufficient MAXEXTENTS value while creating an index.
Effect
The SQL operation completed with a warning.
Recovery
This is a warning only.
SQL 1275
1275 Constraint constraint1 cannot be dropped because it is needed by unique constraint constraint2.
Cause
You attempted to drop a constraint that is needed by a UNIQUE constraint, which is not allowed because it would leave a UNIQUE constraint on a column, but without a NOT NULL constraint for that column.
Effect
The operation fails.
Recovery
To drop the constraint, you must remove the UNIQUE constraint or add an additional NOT NULL constraint to the columns that contain UNIQUE constraints and only one NOT NULL constraint for that column.
SQL 1276
1276 The PARTITION clause cannot be specified for an SQL/MP Table, SQL/MP view or SQL/MX view. The partition partition-name was specified for object table-name.
-
Where,
-
partition-name is the partition name or number specified;
-
table-name is the SQL/MX view name specified.
Cause
The PARTITION clause was used with an SQL/MX view.
Effect
The statement does not compile.
Recovery
Remove the PARTITION clause and compile the statement again.
SQL 1277
1277 Unrecognized partitioning scheme for object object-name.
Cause
NonStop SQL/MX does not recognize the partitioning scheme stored in the metadata for the named object.
Effect
The named object is considered corrupt and is inaccessible.
Recovery
Do not attempt recovery. Hewlett Packard Enterprise support will perform recovery operations in response to an automatically generated dial-out message about this condition. Consider running the VERIFY operation on the named object to check for inconsistencies in the metadata with respect to the partitioning scheme.
SQL 1278
1278 The command cannot be executed because operation is in progress for all schemas in catalog catalog.
Cause
You attempted to execute a DDL or utility operation that affected catalog or a schema in that catalog.
Effect
The operation fails.
Recovery
Wait until the operation is finished and then retry the failed DDL or utility operation.
SQL 1289
1289 The use of ALTER on definition schemas and metadata schemas is not permitted.
Cause
An attempt was made to alter a definition schema or metadata schema.
Effect
The operation fails.
Recovery
None.
SQL 1295
1295 Target column ColumnName has mismatching default type.
Cause
The data type of the specified default value for the column does not match the column data type.
Effect
The command fails.
Recovery
Specify a default value of a matching data type for the column.
SQL 1300
1300 Catman generated unknown Exception for procedure procedure-name.
Cause
An unanticipated error occurred while reading metadata for a stored procedure.
Effect
The operation fails.
Recovery
Retry the operation. If it continues to fail, report the error to your service provider.
SQL 1301
1301 NO ACTION referential action for referential-triggered-action clause is not yet supported as specified by ANSI SQL99 standard. To alter the behavior, set an appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
Cause
NO ACTION referential action is specified in the referential integrity definition, and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is ‘OFF.'
Effect
The NO ACTION referential action cannot be defined.
Recovery
To alter the behavior of NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
SQL 1302
1302 NO ACTION referential action for referential-triggered-action clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
Cause
NO ACTION referential action is specified in the referential definition and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is ‘SYSTEM.'
Effect
The NO ACTION referential action has RESTRICT referential action semantics. It is recorded as NO ACTION in the metadata table.
Recovery
To alter the behavior of the NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
SQL 1303
1303 SQL/MP table or alias name table-name is not allowed in this context.
-
Where,
-
table-name is the ANSI name of an SQL/MP ALIAS, or the Guardian file name of an SQL/MP table.
Cause
An SQL/MP database object was referenced in a create view or create trigger operation, which is not allowed.
Effect
The operation fails.
Recovery
Specify only SQL/MX native database objects in create view or create trigger operations.
SQL 1304
1304 SQL/MX could not obtain the location of the system schema tables.
Cause
The Guardian location of the system schema tables could not be obtained from the anchor file.
Effect
The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure.
Recovery
Correct the error, as reported in the accompanying messages, and resubmit.
SQL 1305
1305 The specified schema location subvolume is already in use by schema schema.
-
Where,
-
subvolume is the Guardian subvolume name specified in the LOCATION clause of the CREATE SCHEMA command;
-
schema is the ANSI name of an existing schema that already uses subvolume as a schema subvolume.
Cause
In a CREATE SCHEMA command, you specified subvolumein the LOCATION clause; however, this subvolume is already being used as schema subvolume by schema.
Effect
The statement fails unless it includes the optional REUSE clause to allow reuse of the same schema subvolume name. If the REUSE clause is used, this is a warning message and the schema is created successfully. The warning can be issued repeatedly for a single CREATE SCHEMA command if multiple schemas already exist with subvolume as the schema subvolume.
Recovery
Only schemas that are RDF replicated to another node should have the same subvolume names as their corresponding schemas on the other node. To create these, use the optional REUSE clause in the CREATE SCHEMA statement. All other schemas should have unique subvolume names. Schemas that are, or will be, related as RDF primary and backup schemas must have identical schema names and subvolumes on the primary and backup nodes.
SQL 1306
1306 SQL/MX was not able to generate a unique schema location for schema schema.
Cause
In a CREATE SCHEMA command, you did not specify a LOCATION clause, but NonStop SQL/MX was unable to generate a schema subvolume name that is not already being used by existing schemas.
Effect
The operation fails.
Recovery
Retry the CREATE SCHEMA several times. If it continues to fail, contact your service provider.
SQL 1307
1307 The schema location subvolume is reserved for SQL/MX metadata.
-
Where,
-
subvolume is the Guardian subvolume name specified in the LOCATION clause of the CREATE SCHEMA command.
Cause
In a CREATE SCHEMA command, you specified subvolume in the LOCATION clause, however subvolume names with the format
ZSDdigit>anything> are reserved for SQL/MX metadata schemas.
Effect
The operation fails.
Recovery
Specify a subvolume name using the format
ZSDletter>anything> in the LOCATION clause, and resubmit.
SQL 1309
1309 Object type for object-name is not valid for the current operation.
Cause
You specified an object for an SQL operation that does not support its object type.
Effect
The operation fails.
Recovery
Specify an object of valid object type and retry the operation.
SQL 1310
1310 The CREATE SCHEMA statement does not support the creation of triggers.
Cause
You specified creation of triggers in the CREATE SCHEMA statement.
Effect
The operation fails.
Recovery
Remove the creation of triggers from the CREATE SCHEMA statement and resubmit. Create triggers in separate statements.
SQL 1311
1311 Unable to action-text constraint constraint-name due to the above errors.
Cause
An error occurs during the creation of the constraint. The error that described the cause of the failure already appears. This error message provides clarification.
Effect
The operation fails.
Recovery
No recovery is necessary.
SQL 1312
1312 Unable to action-textobject-name due to the above errors.
-
Where,
-
action-text is either
create tableorcreate index; -
object-name is either a table name or index name.
Cause
An error occurs during the creation of the table or index. The error that described the cause of the failure already appears. This error message provides clarification.
Effect
The operation fails.
Recovery
No recovery is necessary.
SQL 1330
1330 The command cannot be executed because the operation is in progress on system.
-
Where,
-
operation is either UPGRADE or DOWNGRADE;
-
system is the name of a system where the operation is active.
Cause
A DDL command affects a catalog that is currently being processed by an UPGRADE or a DOWNGRADE operation.
Effect
The command fails.
Recovery
Run the command after the UPGRADE or DOWNGRADE operation is complete.
SQL 1390
1390 The PL/MX compile failed. Details: error-details.
-
Where,
-
error-details is the text that provides more information about the errors encountered.
Cause
There are one or more errors during the compilation of the PL/MX source while executing a CREATE FUNCTION.
Effect
The command fails.
Recovery
Correct the errors and run the CREATE FUNCTION statement again.
SQL 1391
1391 Unable to receive reply from PLMXCMP, possibly caused by internal errors when compiling PL/MX statements.
Cause
A communication or other error occurs between NonStop SQL/MX and the PL/MX compiler.
Effect
The command fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1392
1392 Unable to send request to PLMXCMP process.
Cause
There is a problem while sending information from NonStop SQL/MX to the PL/MX compiler.
Effect
The command fails.
Recovery
If the error persists, contact your service provider.
SQL 1401
1401 The default value of column column-name contains characters that cannot be converted to ISO_MAPPING 'character-set'.
Cause
Unable to convert the default value of column column-name from UCS2 to the ISO_MAPPING character-set during the generation of an internal query while processing a DDL command.
Effect
The operation fails.
Recovery
None.
SQL 1403
1403 The use of CREATE INDEX on metadata tables is not permitted.
Cause
You used the CREATE INDEX statement and attempted to create an index on a SQL/MX metadata table.
Effect
The CREATE INDEX statement fails.
Recovery
Use CREATE INDEX with user tables only.
SQL 1404
1404 The use of ALTER INDEX on metadata indexes is not permitted.
Cause
You used the ALTER INDEX statement and attempted to alter a SQL/MX metadata index.
Effect
The ALTER INDEX statement fails.
Recovery
Use ALTER INDEX with user indexes only.
SQL 1500
1500 The CATSYS - CAT_REFERENCES system schema relationship for catalog catalog might be corrupt.
Cause
A row for catalog was found in the CATSYS system schema table, but no corresponding row could be found in the CAT_REFERENCES system schema table.
Effect
The operation fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1501
1501 The OBJECTS - MP_PARTITIONS definition schema relationship for typeobject might be corrupt.
-
Where,
-
type is the type of the affected object;
-
object is the fully qualified ANSI name of the affected object.
Cause
A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected MP_PARTITIONS definition schema table.
Effect
The operation fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1502
1502 The OBJECTS - REPLICAS definition schema relationship for type object might be corrupt.
-
Where,
-
type is the type of the affected object;
-
object is the fully qualified ANSI name of the affected object.
Cause
A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected REPLICAS definition schema table.
Effect
The operation fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1503
1503 The OBJECTS - PARTITIONS definition schema relationship for type object might be corrupt.
-
Where,
-
type is the type of the affected object;
-
object is the fully qualified ANSI name of the affected object.
Cause
A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected PARTITIONS definition schema table.
Effect
The operation fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1504
1504 table has no OBJECTS entry in definition schema.
-
Where,
-
table is the fully qualified ANSI name of a table in definition schema;
-
definition schema is the fully qualified ANSI name of the affected definition schema.
Cause
A row for table could not be found in the OBJECTS table in definition schema.
Effect
The operation fails.
Recovery
Retry the operation. If the error persists, contact your service provider.
SQL 1506
1506 The system schema metadata for schema schema is inconsistent between nodes node1 and node2.
-
Where,
-
schema is the fully qualified schema name that is mentioned by the current DDL or utility operation;
-
node1 and node2 are the Expand nodes on which schema is visible.
Cause
A SCHEMATA row for schema is expected to exist on node1 and node2. However, the SCHEMATA row is not found on node2.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 1510
1510 Identity column col-name can be of the following data types only: LARGEINT, unsigned INTEGER and unsigned SMALLINT.
Cause
An unsupported data type is specified for IDENTITY column.
Effect
The operation fails.
Recovery
Modify the IDENTITY column data type to LARGEINT, unsigned INTEGER, or unsigned SMALLINT, and resubmit the statement.
SQL 1570
1570 The MAXVALUE for the sequence generator must be greater than the MINVALUE for seq-name.
Cause
For the sequence or IDENTITY column, the MAXVALUE specified is less than the MINVALUE.
Effect
The operation fails.
Recovery
Specify the MAXVALUE greater than the MINVALUE, and resubmit the statement.
SQL 1571
1571 The INCREMENT BY value cannot be zero for seq-name.
Cause
For the sequence or IDENTITY column, the INCREMENT BY option value is zero.
Effect
The operation fails.
Recovery
Specify a non-zero value for the INCREMENT BY value, and resubmit the statement.
SQL 1572
1572 The seq-gen-optionvalue cannot be a negative number for col-name.
Cause
A negative value is specified for the internal sequence generator option (seq-gen-option).
Effect
The operation fails.
Recovery
Specify a positive value for the internal sequence generator option, and resubmit the statement.
SQL 1573
1573 The START WITH value must be greater than or equal to the MINVALUE and less than or equal to the MAXVALUE for seq-name.
Cause
For the sequence or the IDENTITY column, the START WITH value is not in the MINVALUE and MAXVALUE range.
Effect
The operation fails.
Recovery
Specify the START WITH value greater than or equal to the MINVALUE and lesser than or equal to the MAXVALUE, and resubmit the statement.
SQL 1574
1574 The CYCLE option is currently not supported for col-name.
Cause
An unsupported option (CYCLE) is specified. Currently, only the NO CYCLE option is supported.
Effect
The operation fails.
Recovery
Specify NO CYCLE option and resubmit the statement.
SQL 1575
1575 The INCREMENT BY value cannot be greater than the MAXVALUE for col-name.
Cause
The INCREMENT BY internal sequence generator option value specified was greater than MAXVALUE.
Effect
The operation fails.
Recovery
Specify an INCREMENT BY option value less than MAXVALUE, and resubmit the statement.
SQL 1576
1576 The seq-gen-option value is greater than the maximum allowed for seq-name data type.
-
Where,
-
seq-gen-option is the sequence generator attribute.
-
seq-name is the ANSI name of the sequence or the IDENTITY column ANSI name.
Cause
The sequence generator or the IDENTITY column option (seq-gen-option) value is greater than the maximum value allowed for the sequence data type.
Effect
The operation fails.
Recovery
For IDENTITY columns of LARGEINT data type, the error message does not contain the column name.
For example:
IDENTITY column A of type unsigned SMALLINT with MAXVALUE 65536:*** ERROR[1576] The MAXVALUE value is greater than the maximum
allowed for the IDENTITY column A data type. IDENTITY column A of type LARGEINT with MAXVALUE 9223372036854775807:*** ERROR[1576] The MAX
VALUE value is greater than the maximum allowed for the IDENTITY column data type.SQL 1577
1577 The seq-gen-option value is lesser than the minimum allowed for seq-name datatype.
-
Where,
-
seq-gen-option is the sequence generator attribute.
-
seq-name is the ANSI name of the sequence or the IDENTITY column.
Cause
The sequence generator or the IDENTITY column option (seq-gen-option) value is lesser than the minimum value allowed for the sequence data type.
Effect
The operation fails.
Recovery
Specify a value greater than the minimum value allowed for the data type, and resubmit the statement.
SQL 1590
1590 Column col-name is not an IDENTITY column.
Cause
Specified column name for ALTER operation is not an IDENTITY column.
Effect
The operation fails.
Recovery
Correct the IDENTITY column name, and resubmit the statement.
SQL 1591
1591 The MAXVALUE option for the col-namemust be equal to or greater than the current value of seq-gen-value.
-
Where,
-
col-name is the IDENTITY column name;
-
seq-gen-value is the current numeric value of internal sequence generator.
Cause
You specified MAXVALUE which was less than the current value of internal sequence generator.
Effect
The operation fails.
Recovery
Specify a MAXVALUE equal to or greater than the current value of internal sequence generator and resubmit the statement.
SQL 1592
1592 Only the MAXVALUE or INCREMENT BY option can be altered for the col-name.
Cause
The internal sequence generator option specified cannot be altered. Only MAXVALUE and INCREMENT BY options are altered.
Effect
The operation fails.
Recovery
Specify either the MAXVALUE or INCREMENT BY internal sequence generator options, and resubmit the statement.
SQL 1593
1593 Only one col-nameoption can be altered at a time.
Cause
For an IDENTITY column, more than one internal sequence generator option is specified for an ALTER operation.
Effect
The operation fails.
Recovery
Specify either the MAXVALUE or INCREMENT BY internal sequence generator options, and resubmit the statement.
SQL 1594
1594 An error occurred trying to access the current value of the IDENTITY column col-name.
Cause
An internal error occurred while accessing the current value of the IDENTITY column.
Effect
The operation fails.
Recovery
For details, see the additional diagnostic messages. Correct the cause and resubmit the statement.
SQL 1595
1595 The MAXVALUE option for the IDENTITY column col-namemust be a valid numeric value.NO MAXVALUE is not allowed.
Cause
An unsupported option (NO MAXVALUE) is specified for an ALTER operation.
Effect
The operation fails.
Recovery
Specify a valid numeric value for the MAXVALUE option and resubmit the statement.
SQL 1596
1596 Recalibration of the sequence-type sequence generator failed. Please see additional messages for details.
Cause
The recalibration of the CURRENT_VALUE column in the internal or external sequence generator table failed.
Effect
The operation fails.
Recovery
See the additional messages provided with the failure. The additional messages can help you determine the root cause. Correct the cause, and resubmit the statement.
SQL 1597
1597 The maximum of the IDENTITY column, col-name, for the table, table-name, could not be obtained.
-
Where,
-
col-name is the IDENTITY column name;
-
table-name is the table that contains the IDENTITY column.
Cause
The maximum value of the IDENTITY column cannot be obtained from the table.
Effect
The operation fails.
Recovery
Resubmit the statement. If it fails, manually obtain the maximum value of the IDENTITY column. Increment this value by using the INCREMENT BY option value for the IDENTITY column.
If the IDENTITY column default specification type is GENERATED BY DEFAULT, recalibrate the CURRENT_VALUE of the internal sequence generator using the following command:
ALTER TABLE table-name ALTER COLUMN column-name RECALIBRATE TO value NO SELECT
-
Where,
-
table-name is the table that contains the IDENTITY column;
-
column-name is the IDENTITY column name;
-
value is the CURRENT_VALUE of the IDENTITY column.
-
If the IDENTITY column default specification type is GENERATED ALWAYS AS IDENTITY, recalibrate the CURRENT_VALUE of the internal sequence generator using the
ALTER TABLE ALTER COLUMN SET INCREMENT BYmanual calibration instructions.
SQL 1598
1598 The new CURRENT_VALUE, current-value,for the IDENTITY column, col-name, for the table, table-name, will be greater than the allowed, maximum-value.
-
Where,
-
current-value is the CURRENT_VALUE of the IDENTITY column;
-
col-name is the IDENTITY column name;
-
table-name is the table which contains the IDENTITY column;
-
maximum-value is the maximum allowed value for the IDENTITY column.
Cause
The new CURRENT_VALUE is greater than the maximum value allowed for the IDENTITY column data type or is greater than the MAXVALUE option. The CURRENT_VALUE is calculated by adding INCREMENT BY option value to the base current value.
Effect
The operation fails.
Recovery
Determine if changing the options of the IDENTITY column results in calculation of a valid new CURRENT_VALUE maximum. If a new maximum does exist, alter the options using
ALTER TABLE ALTER COLUMN SET command, and resubmit the RECALIBRATE command.
SQL 1599
1599 The recalibration value is greater-or-less-than-an-option value, recalibration-value,of the IDENTITY column, col-name, for the table, table-name.
Where greater-or-less-than-an-option indicates whether the recalibration value is greater or less than a specific value and is one of these phrases:
-
Is less than the current maximum
-
Is less than the START WITH option
-
Is less than the MINVALUE option
-
Is greater than the MAXVALUE
-
recalibration-value is the specified recalibration value;
-
col-name is the IDENTITY column name;
-
table-name is the table that contains the IDENTITY column.
Cause
The specified recalibration value does not comply with these rules:
-
For the IDENTITY column, the recalibration value must not be less than the START WITH and MINVALUE options.
-
The recalibration value must not be greater than the MAXVALUE option of the IDENTITY column.
-
The recalibration value must not be greater than the maximum value allowed for the IDENTITY column data type.
-
If the statement does not contain the NO SELECT option, the recalibration value provided must be greater than the maximum value in the IDENTITY column.
Effect
The operation fails.
Recovery
Correct the recalibration value, and resubmit the statement.
SQL 1600
1600 Unable to lock table, table-name, for the IDENTITY column, col-name, during recalibration.
-
Where,
-
table-name is the table that contains the IDENTITY column;
-
col-name is the IDENTITY column name.
Cause
The table containing the IDENTITY column could not be locked in SHARED MODE because there is a locking contention on the table.
Effect
The operation fails.
Recovery
Resubmit the statement when the locking contention has cleared.
SQL 1601
1601 Recalibration of the GENERATED ALWAYS AS IDENTITY column, col-name, for the table, table-name, is not allowed with NO SELECT.
-
Where,
-
col-name is the IDENTITY column name;
-
table-name is the table that contains the IDENTITY column.
Cause
The NO SELECT syntax with the default specification type of GENERATED ALWAYS AS IDENTITY is not allowed.
Effect
The operation fails.
Recovery
Remove the NO SELECT syntax and resubmit the statement.
SQL 1610
1610 SET NULL clause cannot be applied to column ColumnName which has a NOT NULL constraint defined on it.
Cause
You attempted to create a referential integrity constraint with the SET NULL clause for a column, which was defined with the NOT NULL property.
Effect
The operation fails.
Recovery
Remove the SET NULL clause in the referential integrity constraint or drop the NOT NULL constraint for the column on which you want to create the referential integrity constraint.
SQL 1611
1611 SET DEFAULT clause cannot be applied to column ColumnName which has a NO DEFAULT clause.
Cause
You attempted to create a referential integrity constraint with the SET DEFAULT clause for a column that was defined without a DEFAULT value.
Effect
The operation fails.
Recovery
Remove the SET DEFAULT clause in the referential integrity constraint or set a DEFAULT value for the column on which you want to create the referential integrity constraint.
SQL 1612
1612 Constraint constraintName could not be created as it is a duplicate of constraintName.
Cause
You attempted to create a column list and the referential actions of a referential integrity constraint, which matches the column list and referential action of another referential integrity constraint in the table.
Effect
The operation fails.
Recovery
None.
SQL 1613
1613 Constraint constraintName could not be created as it conflicts with constraintName.
Cause
You attempted to create a column list of referential integrity constraint, which matches the column list of another referential integrity constraint in the table. However, the referential action differs for these two constraints.
Effect
The operation fails.
Recovery
None.
SQL 1614
1614 Constraint constraintName could not be created as referencing column columnName is part of clustering key of table tableName.
Cause
You attempted to create a referential integrity constraint with a referencing column that is a part of the clustering key of the referencing table.
Effect
The operation fails.
Recovery
None.
SQL 1615
1615 constrainttype cannot be created, since it conflicts with referentialaction referential action of the referential constraint ConstraintName.
-
Where,
-
constrainttype is the type of constraint, NOT NULL, or primary key;
-
referentialaction is the referential action.
-
ConstraintName is the name of the referential constraint.
Cause
The NOT NULL constraint cannot be created on a referencing column with the SET NULL referential action on it. (OR) The primary key constraint cannot be created on the referencing column with the referential action specified because the primary key cannot be updated.
Effect
The operation fails.
Recovery
Drop the referential integrity constraint.
SQL 1616
1616 Similarity Check is not supported for reason.
Cause
When Similarity Check is enabled for views, creating or altering a view containing nested views or a VALUES constructor is not supported. For more information, see the SQL/MX Reference Manual.
When a view definition contains nested views or a VALUES constructor or both, this error is returned for the following conditions:
-
CREATE or ALTER VIEW statement syntax with Similarity Check enabled
-
CREATE VIEW statement syntax does not specify the Similarity Check option and the CQD DDL_VIEW_SIMILARITY_CHECK is set to ON.
Effect
The operation fails.
Recovery
Modify the syntax by removing references to the nested views or VALUES constructor and resubmit the statement.
SQL 1617
1617 Similarity Check is already string.
Cause
You issued an ALTER VIEW statement for one of the following conditions:
-
Enable Similarity Check on a view for which Similarity Check is already enabled.
-
Disable Similarity Check on a view for which Similarity Check is already disabled.
Effect
The operation fails.
Recovery
Use SHOWDDL to verify if Similarity Check is enabled or disabled for a view before submitting an ALTER VIEW statement again.
SQL 1620
1620 Scale should be zero for sequence generator.
Cause
You specified a non-zero value for scale in the CREATE SEQUENCE statement.
Effect
The statement fails to execute.
Recovery
Resubmit the statement with scale set to zero.
SQL 1621
1621 Maximum allowed precision for a sequence generator is .seq-max
Cause
You specified a precision value greater than the maximum supported by the sequence generator.
Effect
The statement fails to execute.
Recovery
Resubmit the statement with the precision value lesser than or equal to the maximum supported precision value.
SQL 1622
1622 INCREMENT BY value is inconsistent with MAXVALUE and MINVALUE settings for seq-name.
Cause
The combination of INCREMENT BY, MINVALUE, and MAXVALUE settings results in the sequence generator generating only a single value per cycle.
Effect
The statement fails to execute.
Recovery
Specify INCREMENT BY, MINVALUE, and MAXVALUE settings so that the sequence generator can generate at least two values per cycle.
SQL 1623
1623 The RESTART WITH value should be equal to or greater than the MINVALUE of the sequence generator.
Message Explanation
Cause
The specified value for resetting the CURRENT_VALUE is lesser than the MINVALUE of the sequence generator.
Effect
The statement fails to execute.
Recovery
Increase the RESTART WITH value to a number greater than or equal to MINVALUE.
SQL 1642
1624 The RESTART WITH value should be equal to or less than the MAXVALUE of the sequence generator.
Cause
The specified value for resetting the CURRENT_VALUE is greater than the MAXVALUE of the sequence generator.
Effect
The statement fails to execute.
Recovery
Decrease the RESTART WITH value to a number lesser than or equal to MAXVALUE.
SQL 1625
1625 The current value for sequence generator sequencegenerator-name could not be updated.
Cause
An unexpected error occurred during the increment of the CURRENT_VALUE of the sequence.
Effect
The statement fails to execute.
Recovery
Re-execute the statement. If the problem persists, contact Hewlett Packard Enterprise support for assistance.
SQL 1628
1628 The new MINVALUE of the sequence generator must be less than or equal to the current value current_value, and the START WITH value of the sequence generator.
Cause
The specified MINVALUE of the sequence generator is greater than the current_value or the START WITH value of the sequence generator.
Effect
The statement fails.
Recovery
The specified MINVALUE of the sequence generator must be less than or equal to the current_value and the START WITH value.
SQL 1629
1629 The MAXVALUE of the sequence generator must be greater than or equal to the current value current_value, and the START WITH value of the sequence generator.
Cause
The specified MAXVALUE for the sequence generator is less than the current_value or the START WITH value of the sequence generator.
Effect
The statement fails.
Recovery
Specify a MAXVALUE greater than the current_value or the START WITH value of the sequence generator.
SQL 1630
1630 The seq-attribute attribute cannot be altered.
Cause
You attempted to alter the CACHE/ORDER attribute of the sequence generator. The ALTER operation is not supported for these attributes in this release of SQL/MX.
Effect
The statement fails.
Recovery
None
SQL 1650
1650 External username external-user-name is not associated with any user.
-
Where,
-
external-user-name is the external user to be dropped, a SQL identifier.
Cause
You specified an external username in the DROP USER command which is not associated with any Guardian user in the metadata.
Effect
The execution fails.
Recovery
Specify a valid external username in the DROP USER command and retry the command.
SQL 1651
1651 External username external-user-name is already associated with another user.
-
Where,
-
external-user-name is the external username to be associated with a Guardian user.
Cause
You specified an external username in the CREATE USER command that is already associated with another Guardian user in the metadata.
Effect
The execution fails.
Recovery
Specify a different external username in the CREATE USER command and retry the command.
SQL 1652
1652 User user-name already has an external username.
-
Where,
-
user-name is the name of the Guardian user.
Cause
You specified a Guardian username in the CREATE USER command that has an existing external username.
Effect
The execution fails.
Recovery
Not applicable.
SQL 1653
1653 External-user-name is not a valid external username.
-
Where,
-
external-user-name is the external username, a SQL identifier.
Cause
You specified a Guardian username in the CREATE USER command that is not valid. Either because it is one of the special authorization Ids 'PUBLIC', 'DB_PUBLIC', or 'SYSTEM', or because it contains one or more spaces, or because it has a valid Guardian username format.
Effect
The execution fails.
Recovery
Specify a valid external username in the CREATE USER command and resubmit.
SQL 1654
1654 Privilege group pg-name does not exist.
-
Where,
-
pg-name is a privilege group name, a SQL identifier.
Cause
You specified a privilege group that does not exist. This can affect ALTER, DROP, and GIVE of a privilege group, as well as GRANT and REVOKE.
Effect
The execution fails.
Recovery
Specify the name of an existing privilege group and retry the command.
SQL 1655
1655 Privilege group pg-name already exists.
-
Where,
-
pg-name is a privilege group name, a SQL identifier.
Cause
You specified a privilege group that is already existing, this affects CREATE of a privilege group.
Effect
The execution fails.
Recovery
Specify a privilege group name that does not exist and retry the command.
SQL 1656
1656 Duplicate user specifications are not allowed.
Cause
You specified a valid username more than once on CREATE or ALTER of a privilege group. This includes the scenario where a user is mentioned using both Guardian username and external username.
Effect
The execution fails.
Recovery
Specify each desired user only once and retry the command.
SQL 1657
1657 User user-name is not a member of privilege group pg-name.
-
Where,
-
user-name is a username specified on ALTER PRIVILEGE GROUP.
-
pg-name is a privilege group name, a SQL identifier.
Cause
You specified a user who is not a member of the privilege group.
Effect
The execution fails.
Recovery
Specify only members of the privilege group and retry the command.
SQL 1658
1658 User user-name is already a member of privilege group pg-name.
-
Where,
-
user-name is a username specified on ALTER of a privilege group.
-
pg-name is a privilege group name, a SQL identifier.
Cause
You attempted to add a user who is already a member of the privilege group.
Effect
The execution fails.
Recovery
Specify only users who are not members of the privilege group and retry the command.
SQL 1659
1659 Privilege group pg-name is not empty.
-
Where,
-
pg-name is a privilege group name, a SQL identifier.
Cause
You specified the RESTRICT option and attempted DROP PRIVILEGE GROUP on a privilege group with one or more members. RESTRICT is the default if neither RESTRICT nor CASCADE is specified.
Effect
The execution fails.
Recovery
Use the CASCADE option to drop a non-empty privilege group.
SQL 1660
1660 pg-name is not a valid privilege group name.
-
Where,
-
pg-name is a privilege group name, a SQL identifier.
Cause
You specified a valid Guardian group name as privilege group name on the CREATE PRIVILEGE GROUP command.
Effect
The execution fails.
Recovery
Specify a valid privilege group name and retry the command.
SQL 1661
1661 Privilege group pg-name is not available for this command.
-
Where,
-
pg-name is a privilege group name, an ANSI identifier.
Cause
You specified a privilege group of an incorrect type (Guardian or implicit) on the ALTER, DROP, or GIVE command.
Effect
The execution fails.
Recovery
Specify the name of an explicit privilege group and retry the command.
SQL 1662
1662 GRANT OPTION cannot be used in combination with a privilege group.
Cause
You specified the WITH GRANT OPTION clause for a GRANT command, or the GRANT OPTION FOR clause for a REVOKE command, in combination with a privilege group grantee.
Effect
The execution fails.
Recovery
Specify correct clause and retry the command.
SQL 1663
1663 User user-name is a security administrator and cannot be added to privilege group pg-name.
-
Where,
-
user-name is the name of a user who is attempted to be added to the privilege group pg-name. The username is displayed either as a Guardian username, or as an external username, depending on how it was entered on the command.
Cause
A security administrator tried to add a user, currently designated as a security administrator to a privilege group this is not permitted.
Effect
The execution fails.
Recovery
Omit the offending username and retry the operation.
SQL 1664
1664 No privileges were granted. Privilege group pg-name has member user-name who is a security administrator.
-
Where,
-
user-name is the username of a designated security administrator who is member of the privilege group pg-name. The username can be an external username, or a Guardian username if the user has no external username.
Cause
A security administrator tried to grant a privilege to a privilege group that has a designated security administrator as member, this is not permitted.
Effect
The execution fails.
Recovery
Specify the correct privilege group name or remove the incorrect user from the privilege group and retry the grant operation.
SQL 1665
1665 External username user-name cannot be dropped.
-
Where,
-
user-name is an external username, a SQL identifier.
Cause
You attempted to drop an external username that is associated with a tenant database using DROP USER command. This is not permitted.
Effect
The operation fails.
Recovery
If the offending external username is in error, correct the name and retry the operation.
SQL 1666
1666 User user-name is not available.
-
Where,
-
user-name is a username specified as grantee on a GRANT or REVOKE command, or as new privilege group member in an ADD or ALTER PRIVILEGE GROUP command.
Cause
A GRANT, REVOKE, ADD PRIVILEGE GROUP, or ALTER PRIVILEGE GROUP command, that was executed in the tenant mode specified a user grantee that is not associated with the tenant's database. This is permitted only when the tenant database is shared.
Effect
The operation fails.
Recovery
If the offending name is in error, correct the name and retry the operation. Alternatively, consider if the offending user should be added to the tenant database or if the tenant database should be shared.
SQL 1667
1667 Privilege group pg-name is not available.
Cause
A GRANT or REVOKE command executed in the tenant mode specified a privilege group grantee that is not associated with the tenant's database. This is permitted only when the tenant database is shared.
Effect
The operation fails.
Recovery
If the specified privilege group name is in error, correct the name and retry the operation. Or, consider if the tenant database must be shared.
SQL 1668
1668 This format name-type name is not available.
-
Where,
-
name-type is either "User" or "Privilege group", depending on the type of offending name.
Cause
A GRANT or REVOKE or GIVE command that was executed in tenant mode specified a Guardian format username/privilege group name. This is not permitted.
Effect
The operation fails.
Recovery
If the offending name is in error, correct the name and retry the operation.
SQL 1669
1669 This command cannot use name-type name.
-
Where,
-
name-type is either 'User' or 'Privilege group', depending on the type of offending name.
-
name is a username or privilege group that was specified on the failing command.
Cause
A GRANT or REVOKE command for a DDL privilege is executed on a schema of a shared tenant database, specifying a user or privilege group that is not associated with the database of the tenant. This error is thrown only in the tenant mode.
Effect
The operation fails.
Recovery
If the offending name is in error, correct the name and retry the operation.
SQL 1670
1670 External usernames are not configured.
Cause
A CREATE USER command was attempted and the EXTERNAL_NAME_CASESENSITIVE CQD is not present in the SYSTEM_DEFAULTS table. An external username can be created only when that CQD is present in the SYSTEM_DEFAULTS table with the value ON or OFF.
Effect
The operation fails.
Recovery
Insert a row for EXTERNAL_NAME_CASESENSITIVE with ON or OFF value. Insert this value manually or use the
InstallSqlmx –e command and then retry the command.
SQL 1671
-
Where,
-
pg-name is a privilege group name that is specified in a DDL command for the privilege group.
-
db-name is the name of the tenant database that the privilege group is associated with.
Cause
An ALTER PRIVILEGE GROUP, GIVE PRIVILEGE GROUP, or DROP PRIVILEGE GROUP command is specified for a privilege group that is associated with a tenant database, and the session is not connected to that database.
Effect
The operation fails.
Recovery
If the offending privilege group name is in error, correct the name and retry the operation. To alter or drop the privilege group, execute the command when connected to the associated tenant database.
SQL 1672
1672 Privilege group grantees and distributed catalogs are not compatible.
Cause
-
Grant privileges to a privilege group on an object or schema in a distributed catalog.
-
Register a catalog where privileges on objects or schemas are granted to a privilege group.
Effect
The operation fails.
Recovery
In a distributed environment, grant privileges only to individual users.
SQL 1750
1750 WITH GRANT OPTION not allowed for security administrators.
Cause
A security administrator attempted to execute a GRANT statement for a privilege using WITH GRANT OPTION for which that security administrator had not explicitly been granted the privilege WITH GRANT OPTION.
Effect
The operation fails.
Recovery
Resubmit the command without the WITH GRANT OPTION.
SQL 1751
1751 No privileges were granted. User user-name is a security administrator.
-
Where,
-
user-name is the grantee for the privilege.
Cause
A security administrator tried to grant privilege to a user, currently designated as a security administrator. A security administrator may not grant a privilege to another security administrator, unless the security administrator granting the privilege has been explicitly granted permission to grant the privilege.
Effect
The operation fails.
Recovery
If the target of the grant (the grantee) is in error, correct the error, and resubmit the GRANT statement. If explicitly granting the privilege WITH GRANT OPTION to the security administrator is appropriate, issue a GRANT statement on the affected object WITH GRANT OPTION by an authorized user such as the object owner, and resubmit the failed GRANT statement.
SQL 1752
1752 User user is not a security administrator.
-
Where,
-
user is the user name or user id.
Cause
An attempt was made to revoke the security administrator designation from a user name or user id specified by user which had not previously been designated as a security administrator.
Effect
The operation fails.
Recovery
Reissue the command, specifying a current security administrator.
SQL 1753
1753 You must be a security administrator to perform this operation.
Cause
An attempt was made by super.super to grant or revoke privileges while the set of security administrators was not empty, super.super was not designated as a security administrator, and super.super did not explicitly have the privilege to grant or revoke the privileges in question.
Effect
The operation fails.
Recovery
Designate super.super as a security administrator or explicitly grant the necessary privileges to super.super, and run the command again.
SQL 1754
1754 Grant to PUBLIC is not allowed.
Cause
An attempt was made by a security administrator to grant a privilege to PUBLIC. A security administrator may not grant a privilege to PUBLIC, unless the security administrator making the grant has been explicitly granted permission to grant the privilege (WITH GRANT OPTION).
Effect
The operation fails.
Recovery
If the target of the grant (PUBLIC) is in error, correct the error, and resubmit the GRANT statement. If explicitly granting the privilege WITH GRANT OPTION to the security administrator is appropriate, issue a GRANT statement on the affected object WITH GRANT OPTION by an authorized user such as the object owner, and resubmit the failed GRANT statement.
SQL 1755
1755 Revoke from PUBLIC is not allowed.
Cause
An attempt was made to execute REVOKE CREATE CATALOG or REVOKE CREATE SCHEMA statement with PUBLIC as one of the entries in the grantee list or PUBLIC as the only entry in the grantee list.
Effect
The operation fails.
Recovery
Remove PUBLIC from the grantee list and retry the operation.
SQL 1756
1756 No GIVE SCHEMA operation is in progress. There is nothing to recover.
Cause
An attempt was made to perform the RECOVER SCHEMA operation after a successful GIVE SCHEMA operation.
Effect
The operation fails.
Recovery
None.
SQL 1757
1757 GIVE TABLE-or-SCHEMA operation cannot be performed because object object-name has incompatible RI constraints for this operation.
-
Where,
-
object-name is either the table name or schema name.
Cause
-
A GIVE TABLE operation on a table that had referential integrity constraints with other table(s).
-
A GIVE SCHEMA operation on a schema that had one or more tables with referential integrity constraints. The referential integrity constraints were on table(s) in different schemas.
Effect
The operation fails.
Recovery
-
Ownership of all the objects in the schema must be changed.
-
The table has referential integrity constraints with other table(s) in the same schema.
SQL 1758
1758 Request failed. Operation cannot be performed because targeted new owner does not have sufficient privileges on object-type object-name.
-
Where,
-
object-type is either Table or View;
-
object-name is either the table name or view name.
Cause
You attempted a GIVE operation on a table or view with a dependent view or table.
Effect
The operation fails.
Recovery
For a GIVE VIEW operation, ensure that sufficient privileges are granted to the new view owner and resubmit the statement.
For a GIVE TABLE operation, if the existing table owner and view owner are the same, ensure that the table owner grants all the privileges on the table to itself and resubmit the statement.
SQL 1759
1759 CREATE access is denied on volume.
-
Where,
-
volume is the name of a disc volume.
Cause
An attempt was made to create a SQL object or part of a SQL object, such as a partition on volume and the CREATE access has been denied by Safeguard.
Effect
The operation fails.
Recovery
If the target location of the command has an error, correct and reissue the statement. Otherwise, check with the Safeguard administrator to determine if the volume security is correct or execute the statement using a user id that has CREATE access for the volume.
SQL 1760
1760 Trigger trigger-name has unsatisfied dependent privileges on table table-name.
-
Where,
-
trigger-name is the name of a trigger that uses the affected table.
-
table-name is the name of a table that is directly or indirectly affected by a GIVE operation.
Cause
A GIVE TABLE or GIVE SCHEMA operation changes privileges on a table used by a trigger. This results on the trigger owner losing the required privileges on that table.
Effect
The operation fails.
Recovery
GRANT the required privileges to the trigger owner and then retry the GIVE operation.
SQL 1762
1762 Database database-name is not available.
-
Where,
-
database-name is the name of a database.
Cause
In the tenant mode, the application is trying to access a catalog of other databases.
In the non-tenant mode, the application is trying to drop a catalog or schema of the database, which is configured as a tenant.
Effect
In the tenant mode, access to the catalog of other database is not allowed if the other database is not shared.
In the non-tenant mode, it is not allowed to drop the catalog which is configured as a tenant database.
The SQL statement or command fails.
Recovery
In the tenant mode, use the catalog associated with the database the application has connected to or the catalog of a shared database.
In the nontenant mode, use the catalog which is not configured as a tenant database.
SQL 1763
1763 This command is not available.
Cause
The command you executed cannot be used in the tenant mode.
Effect
None
Recovery
None
SQL 1764
1764 Volume volume-name is not available for database database-name.
-
Where,
-
volume-name is the name of the volume, which is specified in the LOCATION clause of the CREATE DDL statement.
-
database-name is the name of the database.
Cause
Volume specified in the LOCATION clause of the CREATE DDL statement or the syntax-based utility command is not associated with the database.
Effect
The operation fails.
Recovery
Specify the volume that is associated with the database.
SQL 1771
1771 Request failed. Operation cannot be performed because the owner of object-1 would lose required privileges on object-2.
-
Where,
-
object-1 is a view that uses object-2.
-
object-2 is a view or table that is used by view object-1.
Cause
You attempted to change ownership of a schema, view, or table. As a result, the view owner of object-1 loses SELECT privilege on object-2. It is required that a view owner has select privilege on all objects used by the view, or on their schemas.
Effect
The operation fails.
Recovery
Grant the required privileges directly on the used objects and then retry the GIVE command.