Teradata SQL Error and Failure Codes from Error 5592 To 5600

SQLServerF1_Header_Small

5592 A function already exists in the database with the same function name and parameter data types.
Explanation: The user tried to create or replace a function which has the same overloaded function name and parameter
data types with an existing function in the database.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5593 Cannot determine the best-fit function for “%VSTR”.
Explanation: The user attempted to call a function. However, the Parser is not able to determine a best-fit function based on the argument(s) provided in the function call.
Generated By: MGC/RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request, or change the function definition to elimiate the ambiguity of
overloaded functions.

5594 Invalid external file option specified for UDF/XSP/UDM/UDT “%VSTR”.
Explanation: The user failed to supply the external file literal in the correct format to create or replace a
UDF/XSP/UDM/UDT. This is also returned when the external name is beyond 30 character limit. Additionally, if the
external name is not specified then the function/specific function name is used. If this is greater than 30 characters, this error will be returned.
Generated By: RES,OPU modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5595 The privilege is not applicable to a function.
Explanation: The applicable privileges on a function object are DROP FUNCTION, ALTER FUNCTION and EXECUTE
FUNCTION. CREATE FUNCTION is a database level privilege.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5596 The mask string is greater than 256 characters long.
Explanation: The arbitary string in the Set Session Functon Trace statement has a maximum length of 256 characters. If it exceed the limit, this error is generated.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5597 Invalid definition for a Global Temporary Trace Table “%VSTR”.
Explanation: The Global Temporary Trace Table has the following restrictions. If the table definition does not comply
with these restrictions, this error is generated.
1) The first two columns of Global Temporary Trace Table are fixed. The first column must be specified as two bytes,
whereas the second column must be specified as an integer type. 2) The table is always NO FALLBACK. 3) Column entries
cannot have any constraints or default values. 4) There cannot be any INDEX declarations including PRIMARY INDEX. 5)
It must be a MULTISET TABLE.
Generated By: SYN/RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5598 This request is not allowed on a Global Temporary Trace Table “%VSTR”.
Explanation: No insert, update or delete operation is allowed on a global temporary trace table, with an exception of the DELETE ALL case.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not submit the request.

5599 Invalid field attribute specified for a UDF/XSP/UDM/UDT parameter.
Explanation: When creating or replacing a UDF/XSP/UDM/UDT, a user can only specify the character type for a function
parameter. Specifying any other field attributes will result in an error.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5600 Error creating UDF/XSP/UDM/UDT: no compiler available.
Explanation: During the creation of a UDF/XSP/UDM/UDT, no compiler was found on any processor.
Generated By: CUFTsk
For Whom: DBA or site support representative.
Remedy: Add a C compiler to any node that has a PE.

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