Teradata SQL Error and Failure Codes from Error 5580 To 5591

SQLServerF1_Header_Small

5580 Target samples were overwritten at system level.
Explanation: The user attempted to set the samples on the prime keys system name, database name, table name at system
level, but the corresponding samples has already been set.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name, database name, table name or the specified level.

5581 Internal error while cleaning up SAMPLE Segment.
Explanation: This is an internal error with the Target Level Emulation Feature.
Generated By: OPT modules.
For Whom: Internal
Remedy: Please save the traceback and any pertinent information that would help an analyst reproduce the problem,
and contact the Global Support Center.

5582 Invalid character format.
Explanation: Soundex supports Unicode and Latin1 charactor format only.
Generated By: Fltsoundex
For Whom: User
Remedy: Rewrite the query.

5583 Invalid Input: only Latin letters allowed.
Explanation: Soundex supports simple Latin letters as input.
Generated By: Fltsoundex
For Whom: User
Remedy: Rewrite the query.

5584 Data exception: numeric value out of range.
Explanation: Widthbucket input error: WBC <= 0 or WBB1=WBB2.
Generated By: FltWidthbucket
For Whom: User
Remedy: Rewrite the query.

5585 Invalid Input: numeric value within range only.
Explanation: Trigonometry or Widthbucket supports numeric input within range only.
Generated By: FltTrigonomf or FltWidthbucket
For Whom: User
Remedy: Rewrite the query.

5586 Random not allowed in inserted column value(s).
Explanation: Use of random function disallowed for either of the cases: 1.) For creating a PI column value in a simple
insert statement like, insert t1 (random(1,10),…). 2.) For insert/update of column(PI or non-PI) value(s) through mload. As
the random function may produce inconsistent results.
Generated By: OptIns,OptEdIns,OptEdUpd
For Whom: End User.
Remedy: Use insert select if you have to use Random in PI columns insert into t1 select (random(1,10),…);

5587 Reference to function “%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 function table,
which is not allowed. 2. The specified item is a function, but the context of query returning the error requires the item to be
a table,view, macro, permanent journal table, trigger, or stored procedure.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5588 Function “%VSTR” already exists
Explanation: The user tried to create a table, view, macro, trigger, procedure or function, and a function with that name already existed. This error occurs on the CREATE TABLE, VIEW, MACRO, TRIGGER, PROCEDURE or FUNCTION statement.
Generated By: RES/OPD modules.
For Whom: End User.
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different name and resubmit the request.

5589 Function “%VSTR” does not exist.
Explanation: The user referenced a function that does not exist in the database.
Generated By: RES/OPD modules.
For Whom: End User.
Remedy: Check the spelling of the function. Check for the correct database name. Check for the correct number of arguments.
Check for compatible arguments types. Correct the request and resubmit it.

5590 “%VSTR” is not a function.
Explanation: The specified item is a table, view, macro, trigger, permanet journal, procedure and the context of the query returning the error requires the item to be a function.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5591 Invalid parameter list.
Explanation: This error occurs in either of the following situations:
1) The user named some of the parameters in the create or replace function/type statement, which is not allowed. The user must either name all the parameters or not name any parameters.
2) The user has specified duplicate parameter names.
3) SELF cannot be a parameter name in method parameters.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

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