Teradata SQL Error and Failure Codes from Error 7802 To 7811

7802 Call to %VSTR for UDF/XSP/UDM %DBID.%TVMID ran out of shared memory.
Explanation: A user defined function or external procedure called the specified system “FNC” in protected mode, but
the function could not complete because the shared memory provided was not large enough to hold the results of the call.
Generated By: FNC library
For Whom: Site support representative & UDF developer
Notes: The shared memory for the protected mode function is usually enough for most situations that might be encountered.
If the was encountered in a table function the remedy would be to decrease the size of the “scratch pad” memory that
is allocated. By itself allocating the maximum “scratch pad” would not be enough to cause the memory shortage. However
if the function uses input and result arguments to the maximum limits and writes to a trace table to the maximum limits or executes a FNC function that returns a lot of variable data to the maximum limits, there is the slight chance that the free memory in the shared memory segment could run out.
Remedy: Redesign the UDF to use less shared memory at the same time.

7803 The UDF/XSP/UDM %DBID.%TVMID called %VSTR in an invalid context.
Explanation: A UDF, XSP or UDM cannot execute the functions provided in the “FNC” library in all contexts. For example
it is not possible to call the table functions from a function that is not defined to be a table function. It might be function
that cannot execute on a PE vproc.
This error is also thrown when FNCGetPhaseEx and FNC_GetPhase used in the same table function UDF.
Generated By: FNC library
For Whom: UDF/XSP/UDM developer
Remedy: Redesign the UDF/XSP/UDM to not call the FNC library in a non supported context.

7804 The UDF %DBID.%TVMID called %VSTR in invalid mode/phase.
Explanation: Some functions in the “FNC” library are only available in CONST mode. The UDF listed called the FNC
function in VARY mode but it is only supported in CONST mode. Additionally, this error may indicate the function is
called in an inproper mode/phase combination.
The following functions have restrictions on the mode/phase in which they may be used: FNC_TblControl,
FNC_TblAllocCtrlCtx, FNC_TblGetCtrlCtx, FNC_TblOptOut, and FNC_TblFirstParticipant.
Generated By: FNC library
For Whom: UDF developer
Remedy: Redesign the UDF to not call the FNC library in a non supported MODE.

7805 The UDF %DBID.%TVMID called FNC_TblFirstParticipant incorrectly.
Explanation: This error indicates that FNC_TblFirstParticipant and FNC_TblOptOut have not been called correctly. An
inconistent state has been found. This error is detected when one of the following rules about using
FNC_TblFirstParticipant has been violated: 1) If a table function’s call to FNC_TblFirstParticipant fails, FNC_TblOptOut
MUST be called. 2) If the call to FNC_TblFirstParticipant succeeds, FNC_TblOptOut should NOT be called.
Generated By: FNC library
For Whom: UDF developer
Remedy: Redesign the UDF to not call the FNC library in a non supported state.

7807 The Table Function %DBID.%TVMID called %VSTR incorrectly.
Explanation: This error indicates that FNC_TblFirstParticipant and/or FNC_TblControl have not been called correctly.
An inconistent state has been found. This error is detected when one of the following rules has been violated: 1)
FNC_TblFirstParticipant is called a second time from the same amp, or FNC_TblFirstParticipant is called after the amp has already called FNC_TblControl 2) FNC_TblControl is called a second time from the same amp, or FNC_TblControl is
called after the amp has already called FNC_TblFirstParticipant
Generated By: FNC library
For Whom: UDF developer
Remedy: Redesign the UDF to not call the FNC library in a non supported state.

7808 The default connection failed to establish a connection to the database.
Explanation: This error indicates that the external stored procedure (XSP) tried to used the default connection but the
connection had an internal error and the the XSP application server had to be terminated. This could be the result of a prior XSP application compromising the default connection. It could be caused be the current application also.
Generated By: FNC Library
For Whom: XSP application developer
Remedy: Examine the XSP applications to make sure they clean up after they are done. The XSP should not end by not
reading outstanding responses on the default connection. Usually the database will clean up the connection under these
circumstances, but there is always a chance that the application could leave the connection in a state that could cause this error. Once this error is received the application server is terminated and a fresh process is created. So a subsequent run of the XSP application should not result in this error again unless the XSP application (or some other one) causes the situation again.

7809 Table function’s CtrlCtx was not initialized.
Explanation: This error indicates that the table function’s CtrlCtx was not initialized during the TBL_PRE_INIT phase
by the controlling copy of a TBL_MODE_CONST function.
Generated By: FNC Library
For Whom: UDF application developer
Remedy: The UDF must use the FNC_TblAllocCtrlCtx routine.

7810 %VSTR.
Explanation: This error indicates that either 1) metadata (Hash By clause, Local Order By clause, or Columns Definition)
was already specified or 2) The metadata passed as parameter is invalid (e.g., invalid character set, data type)
Generated By: FNC Library
For Whom: UDF application developer
Remedy: Do not set metadata in the contract function if it was already set by the SQL statement. Check that the metadata
passed as a parameter is valid.

7811 %VSTR.
Explanation: User issued an error.
Generated By: FNC Library
For Whom: UDF application developer
Remedy: See error message.

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