Teradata SQL Error and Failure Codes from Error 7856 To 7866

SQLServerF1_Header_Small

7856 Java XSP/UDF failed because available JVM heap memory has run out.
Explanation: The Java XSP/UDF was calling a Java method which needs to allocate a block of memory from the JVM
heap. The allocation failed because JVM has no enough memory.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: User’s Java XSP/UDF attempted to allocate too much memory or there was memory leak. Debug the user’s
Java XSP/UDF.

7857 Java Blob/Clob methods in a Java XSP/UDF failed to open a lob for read and write.
Explanation: The Java XSP/UDF was calling a Java Blob/Clob method. This method failed because the lob could not be
opened.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Unexpected error. Debug User’s Java XSP/UDF.

7858 Java XSP/UDF was calling a Blob/Clob method which is not supported in this release.
Explanation: The Java XSP/UDF was calling a Java Blob/Clob method which is not supported in this release.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Change user’s code.

7859 Java XSP/UDF called a Java Blob/Clob method with invalid parameters.
Explanation: Java XSP/UDF called a Java Blob/Clob method with invalid parameters.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Unexpected error. Debug User’s Java XSP/UDF.

7860 Java execution error because jar file is bad or missing.
Explanation: The jar file was not found in JavaLibraryPath, or could not be read.
Generated By: UDF Subsystem
For Whom: End User.
Remedy: Call either SQLJ.redistribute_jar or SQLJ.replace_jar to update the jar file.

7861 Java XSP/UDF caused a securityException because it tried to terminate the JVM.
Explanation: The error message is generated when Java XSP/UDF tries to terminate or halt the currently running Java
Virtual Machine, by calling System.exit() or similar methods. A securityException will be thrown when Java XSP/UDF
calls these methods.
Generated By: UDF Subsystem
For Whom: End User.
Remedy: The user Java code has to be changed not to call these methods: System.exit(), Runtime.exit(), Runtime.halt(),
and the deprecated Runtime.runFinalizersOnExit() and System.runFinalizersOnExit().

7862 Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() was called in a Java UDF which doesn’t return a lob.
Explanation: Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() can only be called in a JUDF which returns a lob.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Correct user’s Java XSP/UDF.

7863 Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() was called from a Java XSP/UDF which is neither a scalar UDF nor an aggregate UDF.
Explanation: Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() can only be called in a scalar or aggregate JUDF
which returns a lob.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Correct user’s Java XSP/UDF.

7864 Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() was called in a Java aggregate UDF but the call is not in the AGR_FINAL phase.
Explanation: In an aggregate Java UDF, Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() can only be called in
the final phase.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Correct user’s Java XSP/UDF.

7865 Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() failed because its calling context is unknown due to Java UDF subsystem errors.
Explanation: An unexpected error happened in FNC modules so that the calling context of Blob.getUDFOutputBlob() or
Clob.getUDFOutputClob() in a Java UDF is not avaliable.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Debug user’s Java XSP/UDF.

7866 Blob.getUDFOutputBlob() or Clob.getUDFOutputClob() was called to get a lob object which is not of the correct lob type for return.
Explanation: A Java UDF returning Clob(or Blob) called Blob.getUDFOutputBlob()(or Clob.getUDFOutputClob()). The
lob obtained through the two methods must match the return lob type of the calling Java UDF.
Generated By: UDF subsystem.
For Whom: End user.
Remedy: Correct user’s Java XSP/UDF.

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