Number
|
Severity
|
Text and Explanation
|
1901
|
16
|
Column `%.*s' -- Can't create index on a column of BIT data type.
Explanation: Adaptive Server could not perform the requested action. Rewrite
the command to conform to the requirement specified in the error
message.
|
1902
|
16
|
Cannot create more than one clustered index on table `%.*s'. Drop the existing clustered index `%.*s' before creating another
Explanation: Refer to the writeup for this error.
|
1903
|
16
|
%d is the maximum allowable size of an index. Composite index specified is %d bytes.
Explanation: Refer to the writeup for this error.
|
1904
|
16
|
Cannot specify more than %d column names for index key list. %d specified.
Explanation: A composite index is any index that uses more than one column.
Error 1904 occurs when more than 31 columns are combined in a
single composite index . Change your create index statement
to include no more than the maximum number of columns allowed.
|
1905
|
21
|
Could not find `zero' row for index `%.*s' the table in sysindexes.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
1906
|
11
|
Cannot create an index on table `%.*s', because this table does not exist in database `%S_DBID'.
Explanation: Command failed. Check your database for the object not found
and re-enter the command with the correct name.
|
1907
|
10
|
Create index on non-empty table not supported yet
Explanation: This is an informational message but may require follow-up
action. Contact your System Administrator.
|
1908
|
16
|
Too many parameters -- symbol table overflow.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1909
|
16
|
Can't use duplicate column names in index key list. Column name `%.*s' listed more than once.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1910
|
16
|
Cannot create more than %d indexes on one table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1913
|
16
|
There is already an index on table `%.*s' named `%.*s'
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1914
|
16
|
Cannot create index on object `%.*s' because it is not a user table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1915
|
14
|
Only the owner of table `%.*s' or a user with System Administrator (SA) role can create an index on it.
Explanation: You do not have the permission to execute this command. Have
the object owner or a user with the needed role run this command.
|
1916
|
16
|
CREATE INDEX options %s and %s are mutually exclusive.
Explanation: Refer to the writeup for this error.
|
1918
|
10
|
Non-clustered index (index id = %d) is being rebuilt.
Explanation: This is an informational message. Unless otherwise specified,
no action is required. Contact your System Administrator about any
warning issued in the message.
|
1919
|
16
|
Column `%.*s' -- Can't create index on a column of TEXT or IMAGE data type.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1920
|
16
|
A column in a primary key constraint's column list is not constrained to be not null, column name: `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1921
|
16
|
An index with the same columns in the same order already exists on the table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1922
|
16
|
An unknown index creation error occurred: %d.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
1923
|
16
|
A table cannot have more than one primary key, attempt to define a second primary key failed on table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1924
|
16
|
You cannot create an index on the sysaudits table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1927
|
25
|
Create Index failed because user curwrite level is not equal to the level of table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
1928
|
16
|
Cannot create clustered index '%.*s' on '%.*s' which has %d partitions because the maximum number of partitions allowed on a table with clustered index is %d.
Explanation: Refer to the writeup for this error.
|
1929
|
20
|
Failed to reserve/initialize allocation hints space in index `%.*s' on table `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the
current process. Report the error to your System Administrator.
|
1930
|
16
|
Cannot specify more than %d column names for index key list. %d specified. Check sp_dboption for nonunique index option, it has added an extra key for indentity coulumn.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message. (Discontinued
in 11.9.2).
|
1931
|
16
|
You cannot re-create the same non-clustered index (ID %d) for object ID %ld in database `%.*s' because you dropped it twice in a single transaction. Transaction rolled back.
Explanation: For a database which has been marked for `ddl
in tran', a non-clustered index cannot be re-created if
it has already been dropped twice within a transaction.
|
1932
|
16
|
You cannot re-create the same clustered index for object ID %ld in database `%.*s' more than once in a single transaction. Transaction rolled back.
Explanation: For a database which has been marked for `ddl
in tran', a clustered index cannot be re-created more
than once within a transaction.
|
1933
|
12
|
The object `%.*s' is not a partitioned table. UPDATE PARTITION STATISTICS can only be run on partitioned tables.
Explanation:
|
1934
|
16
|
Invalid partition number %d. Valid partition number is a positive integer.
Explanation: Re-try the query using a valid number.
|
1936
|
10
|
Warning: Clustered index '%.*s' has been created on the empty partitioned table '%.*s'. All insertions will go to the first partition. To distribute the data to all the partitions, re-create the clustered index after loading the data.
Explanation: This is an informational message. Take the indicated action
if you wish to distribute data across partitions.
|
1937
|
10
|
Warning: Clustered index '%.*s' has been created on the partitioned table '%.*s' with %d partitions using the segment %d with %d devices. For complete I/O parallelism, each partition should be on a separate device.
Explanation: This is an informational message but may require follow-up
action. Contact your System Administrator.
|
1938
|
16
|
Cannot create index or unique constraint because cursor '%.*s' is still open. Close the cursor(s) before creating index or constraint.
Explanation: Re–try the query after taking the indicated action.
|
1939
|
16
|
Cannot create a clustered index with sorted_data option on the 11.0 partitioned table '%.*s'. This option isn't allowed. To create the index do not use this option.
Explanation: Re–try the query using the recommended action.
|
1940
|
16
|
Cannot create clustered index on table '%.*s' because there are one or more isolation level 0 scans, or RE ORG command, active on the table.
Explanation: Retry the command after the scans are complete.
|
1941
|
10
|
Warning: Clustered index '%.*s' has been created with ignore_dup_row on table '%.*s', which uses data-only locking. ignore_dup_row cannot be enforced for subsequent insertions and updates.
Explanation: This is an informational message but may require follow-up
action. Contact your System Administrator.
|
1942
|
16
|
You cannot drop and re-create the same clustered index with sorted data for object ID %ld in database '%.* s' in a single transaction. Transaction rolled back.
Explanation: Adaptive Server could not perform the requested action. Modify
your command to meet the Adaptive Server requirement for the objects
or variables shown in the error message.
|
1944
|
16
|
The clustered index cannot be created on a partitioned table using serial sort. The CONSUMER value specified in the CREATE INDEX command must be greater than 1.
Explanation: Modify your DDL command to meet the Adaptive Server requirement
for the objects or variables shown in the error message.
|