Teradata SQL Error and Failure Codes from Error 7963 To 7975

7963 The statement is not eligible to return a result set.
Explanation: Dynamic result sets are only allowed to be returned for SELECT and some other statements like SHOW
TABLE.
Generated By: Par modules
For Whom: The stored procedure programmer
Remedy: Change the SP_return_result to indicate this request should not return a result set.

7965 JAR file “%VSTR” either is corrupted, has invalid format, or uses absolute paths for its classes.
Explanation: The user is attempting to install (or replace with) an invalid jar. This error often occurs when the jar file
either is not created correctly, has been corrupted, or uses absolute paths for its classes.
Generated By: PAR modules.
For Whom: End User.
Remedy: Correct the JAR file and validate its format using JAR utility. Resubmit the request.

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

7968 The recipient of the result set does not support dynamic result sets.
Explanation: The stored procedure created a dynamic result set to return to the caller or client, but the caller or client
does not support dynamic result sets.
Generated By: Par and Dis modules
For Whom: The stored procedure programmer
Remedy: Have the caller or client support dynamic result sets.

7969 Invalid external name string option specified for Java XSP/UDF ’%FSTR’ because %VSTR.
Explanation: Java XSP/UDF tests whether the external name string is in the correct format. This error occurs on the Create/
Replace Procedure or Create/Replace Function statement. This is also returned when the external name is beyond the
30 character limit. Additionally, if the external name is not specified then the procedure name is used. If this is greater than
30 characters, this error will be returned.
Generated By: PAR modules.
For Whom: End User.
Remedy: Correct the external name string in Create/Replace Procedure or Create/Replace Function statement and
resubmit the request.

7970 Create/Replace Java XSP/UDF passed an unacceptable signature. Correct the signature.
Explanation: Java XSP/UDF tests whether the signature in the external name string is acceptable or not. This error
occurs on the Create/Replace Procedure or Create/Replace Function statement.
Generated By: PAR modules.
For Whom: End User.
Remedy: Correct the Create/Replace Procedure or Create/Replace Function statement to specify a correct signature and
resubmit the request.

7971 Jar “%VSTR” already exists
Explanation: The user tried to create a table, view, macro, trigger, procedure, function, or Jar, and a Jar with that name
already existed. This error occurs on the call to the XSP SQLJ.Install_Jar.
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.

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

7973 Invalid “locspec” option specified for JAR file “%VSTR”.
Explanation: The user failed to supply the locspec argument to the SQLJ.Install_Jar XSP or SQLJ.Replace_Jar XSP in the
correct format to install/replace a JAR on the system.
Generated By: RES/OPU modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

7974 The privilege is not applicable to a Jar.
Explanation: The only applicable privilege is DROP PROCEDURE for a JAR object.
Generated By: RES/OPD modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

7975 Can not execute XSP/UDF “%VSTR”. Java Language is not supported on the system.
Explanation: The user is attempting to execute a Java XSP/UDF. The Java language is not supported on the system.
Generated By: RES modules.
For Whom: End User.
Remedy: Contact the Global Support Center.

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