Teradata SQL Error and Failure Codes from Error 5505 To 5516

5505 Column data types cannot be specified with a WITH [NO] DATA clause.
Explanation: When a WITH [NO] DATA clause is specified for a CREATE TABLE statement, column data types cannot
be specified for the table to be created.
Generated By: Syntaxer.
For Whom: User.
Remedy: Remove column data type specification and re-submit query.

5506 Column names must be specified when SELECT list contains an unnamed expression.
Explanation: If the SELECT list contains an expression that does not have an AS or NAMED clause, column names must
be specified for the table to be created.
Generated By: Syntaxer.
For Whom: User.
Remedy: Specify column names and re-submit query.

5507 Referential integrity constraints are not allowed with a WITH [NO] DATA clause.
Explanation: When a WITH [NO] DATA clause is specified for a CREATE TABLE statement, REFERENCE constraints
cannot be specified.
Generated By: Syntaxer.
For Whom: User.
Remedy: Remove referential constraint and re-submit query.

5508 Column name list mismatched with columns from select list or table.
Explanation: The number of column names specified for table to be created is not equal to the number of columns in the
source subquery or table.
Generated By: Resolver.
For Whom: User.
Remedy: Specify the correct number of column names and re-submit query.

5509 Global temporary table cannot be created WITH DATA.
Explanation: If GLOBAL TEMPORARY is specified in a CREATE TABLE statement, only the definition of the base temporary
table is created. A temporary table for data storage is materialized only when the user references the base temporary
table, so ’WITH DATA’ may not be specified for global temporary tables.
Generated By: Syntaxer.
For Whom: User.
Remedy: Change ’WITH DATA’ to ’WITH NO DATA’ and re-submit query.

5510 Invalid session mode for procedure execution.
Explanation: The session mode within which the CALL SQL is submitted is different than the one in which the stored
procedure was created. A stored procedure created in ANSI mode cannot be executed in Teradata mode and vice versa.
Generated By: RES Modules.
For Whom: End User.
Remedy: Change the session mode and resubmit the request or recreate the procedure in the desired session mode and
resubmit the request. DR43887-MK6-03 <-

5511 Reference to [external] stored procedure “%VSTR” is not allowed in this context.
Explanation: This error occurs in either of the following situations.
1. The user tried to insert rows into a [external] stored procedure which is not allowed.
2. The specified item is a [external] stored procedure, but the context of of the query returning the error requires the item to
be a table, view, macro, user-defined function or permanent journal table.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5512 Stored Procedure “%VSTR” already exists.
Explanation: The user tried to create a stored procedure and a table, view, trigger, macro or procedure with that name
already exists. This error occurs on the CREATE PROCEDURE statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Examine the statement and verify that the request is correct. Change the statement to specify a different name
and resubmit the request.

5515 Check constraints were not copied.
Explanation: This is only a warning to let the user know that check constraints will not be copied to the table being created.
This is the case where a table name was specified in the Create Table As/Like statement with column names defined
in the Create Table clause. For example,
CREATE TABLE Table1 (field_1, field_2) Table2 WITH [NO] DATA;
Check constraints on Table2 (if exist) will not be copied to Table1.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

5516 PRIMARY KEY or UNIQUE column(s) must be NOT NULL.
Explanation: The column(s) in the PRIMARY KEY or UNIQUE definition must be defined as NOT NULL.
Generated By: Resolver.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

Above are list of Teradata Errors or Failure Codes from Error 5505 To 5516 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 *