Teradata SQL Error and Failure Codes from Error 3516 To 3526

3516 More than one primary index or primary key specified.
Explanation: Tables can have only one primary index and one primary key. The user can add a primary key if and only
if there’s not already a primary key exist in table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Decide which index will be the primary index. The other indexes can be redefined as secondary. Resubmit the
request.
In the case of a primary key, the user must take either of the following steps:
<1> If the current primary key is mapped to an unique secondary index then drop the primary key using DROP INDEX
and resubmit the request.
<2> If the current primary key is mapped to an unique primary index then define this index as an unique secondary index
using CREATE INDEX statement.

3517 A column can appear only once in an index.
Explanation: A column that is identified to appear in an index must be unique.
Generated By: OPT modules.
For Whom: End User.
Remedy: Check the column names, delete any duplicates, and resubmit the request.

3518 Too many columns in a composite index.
Explanation: The number of columns in an index is limited to 64. This index could either be a primary index, secondary
index or reference index.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change the index definition and resubmit the request.

3519 Two indexes with the same columns.
Explanation: The user tried to create an index containing the same columns as an existing index.
Generated By: OPT modules.
For Whom: End User.
Notes: Regardless of column order, indexes containing the same columns are considered identical.
Remedy: Change the index definition and resubmit request.

3520 A constant value in a query is not valid for column %VSTR.
Explanation: A constant in a user statement represents a value too big for the designated column, or if the column data
type is DATE, represents an invalid date.
Examples: 32768 cannot be assigned to a column of type SMALLINT. 871332 cannot be assigned to a column of type DATE.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change the constant in query and resubmit request.

3521 Table reference(s) detected where constants expected.
Explanation: In INSERT statements, the right-most side of the assignments must either be constants or expressions that
contain only constants.
Generated By: OPT modules.
For Whom: End User.
Notes: Macro parameter values and USING references are considered constants.
Remedy: Correct the error and resubmit the request.

3522 Internal error: A statement node does not represent an existing step.
Explanation: Parse tree node encountered does not represent a step to be generated.
Generated By: GEN modules.
For Whom: System Support Representative.
Remedy: This is an internal problem, not a user error. If this problem persists, contact your support representative.

3523 %FSTR does not have %VSTR access to %DBID.%TVMID.
Explanation: The user does not have the proper access rights to execute this request, or the owner of the requested view
or macro does not have the proper access rights to underlying tables.
Generated By: SQL modules.
For Whom: End User.
Remedy: Obtain the necessary access rights.

3524 %FSTR does not have %VSTR access to database %DBID.
Explanation: The user does not have the proper access rights to execute this request, or the requested database does not
have the proper access rights.
Generated By: SQL modules.
For Whom: End User.
Remedy: Obtain the necessary access rights.

3525 The user cannot create or drop a PRIMARY index.
Explanation: The user tried to create or drop a primary index.
Generated By: OPT modules.
For Whom: End User.
Remedy: To change the primary index of a table, create a new table. Insert data into the new table by using the
INSERT…SELECT statement; drop the old table, and rename the new table with the old table name.

3526 The specified index does not exist.
Explanation: The user tried to drop an index that does not exist.
Generated By: OPT modules.
For Whom: End User.
Remedy: Determine why the index does not exist.

Above are list of Teradata Errors or Failure Codes from Error 3516 To 3526 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *