Teradata SQL Error and Failure Codes from Error 7660 To 7672

7660 Stored Procedure execution caused stack overflow.
Explanation: This error occurs when a stack overflow error is encountered either in the EVL or the RTS subsystem, during
the execution of a stored procedure.
Generated By: RTS Modules.
For Whom: End User.
Remedy: End User should recreate the stored procedure by splitting the large and complex expressions in the stored procedure.

7662 The XSP caused a hardware fault. Please do not resubmit the last request.
Explanation: The external stored procedure caused a hardware fault (access violation, divide fault etc.) and had to be
terminated.
Generated By: RTS Modules
For Whom: End User.
Remedy: Rerun the XSP in protected mode and add diagnostic information to help track down the problem. For example
add FNC_Trace_WRITE_DL calls to the XSP.

7663 The database can only execute %VSTR per session.
Explanation: It is only possible call an XSP (External Stored Procedure) to the nesting level reported in the error message.
Do not exceed that limit.
Generated By: RTS Modules
For Whom: End User.
Remedy: Design the stored procedure calls to that the XSP does not call another XSP or call a SP that calls an XSP that
would exceed the nesting limit.

7664 Illegal attempt to modify CLASS_ORIGIN or SUBCLASS_ORIGIN.
Explanation: The user attempted to change the values of CLASS_ORIGIN or SUBCLASS_ORIGIN in SIGNAL or RESIGNAL
statement, which is not allowed. Modification is allowed only with user-defined condition.
Generated By: RTS modules.
For Whom: End User.
Remedy: Correct the SIGNAL or RESIGNAL statement and resubmit the request.

7665 User-defined condition %VSTR is raised from triggered stored procedure.
Explanation: User defined condition is not allowed in SIGNAL statemetn, if the stored procedure is invoked from trigger.
Generated By: RTS modules.
For Whom: End User.
Remedy: Correct the SIGNAL statement and resubmit the request.

7666 User-defined condition %VSTR is not declared in a stored procedure.
Explanation: User-defined condition is not declared in a stored procedure and also in outer stored procedure, if any.
Generated By: RTS modules.
For Whom: End user.
Remedy: Declare the user-defined condition in a SP or outer SP.

7669 Stored procedure %FSTR does not exist in %VSTR.
Explanation: The stored procedure was replaced or dropped before a statement that references the stored procedure was
processed.
Generated By: RTS Modules.
For Whom: End User.
Remedy: The stored procedure that is referenced no longer exists. If the stored procedure was replaced, please resubmit
the request or otherwise it must be re-created.

7670 Insufficient memory to process stored procedure request.
Explanation: There is no virtual memory available to fetch the stored procedure object code.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Try resubmitting the request and if it fails consistently simplify the stored procedure as it may be too huge and
resubmit the execution request.

7671 The log file that saves the spoil information is bad under the directory %VSTR.
Explanation: A log file is saved in the node for each database level directory that holds the object code files. This error is
logged when the log file is corrupted.
Generated By: rtsexecsp
For Whom: Field Representative
Remedy: If the file is corrupted, then the obsolete object code files cannot be deleted. Check if any of the stored procedures
or the database itself are non-existant. If so, perform a manual delete operation and remove the bad log file. Note that
the clean-up of the obsolete files can no longer be done by the system as long as the bad file exists. The database id can be
obtained from the directory name and the SP ID can be obtained along with version number from the object code file name
within the database directory.

7672 Unwind the stack to the most outer logmark.
Explanation: Unwind the stack for the task to the most outer logmark setup prior to invoking a stored procedure.
Generated By: disrts
For Whom: Internal only.
Remedy: This operation is only internal to the DBS. When the SqlDrivr (combo) task picks up an abort message while
executing a SQL statement within stored procedure, we simply unwind the stack to the most outer logmark which is
placed in disexecutesp so that the abort message could be processed.

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