Teradata SQL Error and Failure Codes from Error 7976 To 7985

SQLServerF1_Header_Small

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

7977 “%VSTR” operation on “%FSTR” not allowed .
Explanation: The Drop/Alter/Grant/Revoke/Show operation is allowed only the Table Operator. It was attempted on
a Constructor function, or Rename was attempted on either a Table Operator or Constructor function. This is not allowed.
Generated By: RES modules.
For Whom: End User.
Remedy: Try operation on Table Operator associated with the Constructor function.

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

7979 Can not execute XSP/UDF “%VSTR”. Java Language is not supported on this Operating System.
Explanation: The user is attempting to execute a Java XSP/UDF.
Generated By: RES modules.
For Whom: End User.
Remedy: Submit the request on a different Operating System.

7980 A JAVA method in the specified Jar which matches that in the EXTERNAL NAME clause was not found%VSTR.
Explanation: JavaPtest did not find the method matching that specified in the Create/Replace Procedure or Create/
Replace Function statement in the specified Jar file.
Generated By: CUF modules.
For Whom: End User.
Remedy: Either correct the Create/Replace Procedure or Create/Replace Function statement to specify a JAVA method
contained in the specified Jar file, or replace the specified Jar file with a version which contains the required JAVA method
via a call to the XSP SQLJ.Replace_Jar, and resubmit the original request.

7981 Reference to JAR “%VSTR” is not allowed in this context.
Explanation: This error occurs when a Jar is referenced in a DML statement. Jar objects are only used in conjunction with
the Java language routines which reference them and so they are disallowed in all DML statements which would normally
reference a table, view, or macro.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

7982 %VSTR operation is not allowed on a JAR.
Explanation: The user is attempting to perform a DML operation on a JAR object. As JAR objects are only used in conjunction
with Java XSPs which use them, these operations are not allowed.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not perform DML operations on a JAR. These types of operations can, however, be performed on a Java
XSP.

7983 XSP “%VSTR” does not exist in the SQLJ database.
Explanation: The user is attempting to call one of the built-in XSPs for Jar operations: SQLJ.Install_Jar, SQLJ.Replace_Jar,
SQLJ.Remove_Jar, SQLJ.Alter_Java_Path, SQLJ.Redistribute_Jar. These XSPs are normally installed via a DIP script, but
they are not found.
Generated By: RES modules.
For Whom: End User.
Remedy: Re-run the DIPSQLJ script to re-create these XSPs, then re-run the query.

7984 Maximum number of Java XSPs/UDFs referencing one Jar has been exceeded.
Explanation: The user is attempting to create more Java XSPs/UDFs which reference a single Jar than permitted. There
is a dynamic limit on how many Java XSPs/UDFs may reference one Jar; this is calculated when a new Java XSP/UDF is
created.
Generated By: OPD modules.
For Whom: End User.
Remedy: Remove one or more Java XSPs/UDFs which reference the same Jar, or install a new Jar on the system which
will be used by the next Java XSP/UDF.

7985 Diagnostic BYPASS ACCESSRIGHTS not allowed if multiple users logged on.
Explanation: DIAGNOSTIC BYPASS ACCESSRIGHTS is used during the dictionary table conversion. It expects the current
user to be DBC and the only user when the DBS control flag BypassAccessrights is ON.
Generated By: SYN modules.
For Whom: The DBA.
Remedy: Make sure there are no other users logged on.

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