Teradata SQL Error and Failure Codes from Error 5601 To 5614

5601 Error creating UDF/XSP/UDM/UDT/JAR: problem with temporary compile directory.
Explanation: During the creation of a UDF/XSP/UDM/UDT/JAR, a problem was found in creating or accessing the
temporary compile directory.
Generated By: CUFTsk
For Whom: DBA or site support representative.
Remedy: Check the permissions of the directory under which the temporary compile files will be placed. Also check
space availability.

5602 Error creating UDF/XSP/UDM/UDT/JAR: problem accessing the external file “%VSTR “.
Explanation: During the creation of a UDF/XSP/UDM/UDT/JAR, a problem was found in accessing the external files.
Generated By: CUFTsk
For Whom: UDF/UDT/XSP developer
Remedy: Check the files exist in the directory specified. Check the read permissions of the files. Check the spelling of the
supplied directory and external file names.

5603 Errors encountered in compiling UDF/XSP/UDM/UDT/JAR.
Explanation: During the creation of a UDF/XSP/UDM/UDT/JAR, a problem was found during compilation. Compilation
errors exist. The UDF/XSP/UDM/UDT can not be created.
Generated By: CUFTsk
For Whom: UDF/UDT/XSP developer
Remedy: Check the compile errors returned with this error.

5604 Correlated references to Ordered Analytical Functions not allowed in subqueries.
Explanation: Ordered Analytical Functions are not allowed in Subqueries
Generated By: optret.c, synchstf.c
For Whom: End User.
Remedy: Correct query and resubmit

5605 A NEW_TABLE or OLD_TABLE reference is not allowed to be passed to a macro.
Explanation: OLD_TABLE and NEW_TABLE aliases refer to set of rows which cannot be passed as an argument to a
macro.
Generated By: resname2
For Whom: End-User
Remedy: Redefine the trigger without NEW_TABLE or OLD_TABLE reference in the macro argument.

5606 Statistical Functions not allowed in WITH clause.
Explanation: Statistical Functions not allowed in WITH clause.
Generated By: Opt modules
For Whom: End User

5607 Check output for possible warnings encountered in compiling and/or linking UDF/XSP/UDM/UDT.
Explanation: During the creation/replace/drop of a UDF/XSP/UDM/UDT, a problem was found during compilation
or linking. Compilation/linking warnings exist. The UDF/XSP was created/replaced/dropped despite the errors.
Generated By: CUFTsk
For Whom: UDF/UDT/XSP developer
Remedy: Check the compile/link errors returned with this error.

5610 Invalid usage of SAMPLEID.
Explanation: Invalid usage of SAMPLEID. eg: sqrt(sampleid),log(sampleid);
Generated By: OptBySamp
For Whom: End User.
Remedy: None.

5611 The user does not have %VSTR right.
Explanation: The user does not have the proper access rights to execute this request.
Generated By: pardrivr module.
For Whom: End User.
Remedy: Obtain the necessary access rights.

5612 A user, database or role with the specified name already exists.
Explanation: A name must be unique amongst users, databases and roles.
Generated By: pardrivr module.
For Whom: End User.
Remedy: Select a different name and re-submit the request.

5613 GRANT OPTION cannot be granted to a role.
Explanation: WITH GRANT OPTION can only be granted to users or databases.
Generated By: resname2 module.
For Whom: End User.
Remedy: Remove WITH GRANT OPTION and re-submit request.

5614 The ALL option cannot be applied to a role.
Explanation: The ALL option is not applicable to a role since it is a set of privileges and not a database or user.
Generated By: resname2 module.
For Whom: End User.
Remedy: Remove ALL option or change grantee to a user and re-submit the request.

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