Teradata SQL Error and Failure Codes from Error 7673 To 7686

7673 Unexpected error occured while executing a statement from within stored procedure.
Explanation: An unexpected error occured while the DBS is executing a SQL statement from within stored procedure.
Generated By: dispatcher
For Whom: Field representative.
Remedy: Save the dump information as available and contact the support personnel.

7674 Informational message.
Explanation: An informational message only.
Generated By: RTS
For Whom: None.
Remedy: None.

7676 Insufficient memory in stored procedure cache.
Explanation: There is no sufficient memory in SP cache and the number of extension segments are reached the limit.
Only RTSMaxExtSeg(10) segments of size 64K can be allocated for SP cache.
Generated By: RTS Cache Modules.
For Whom: End User.
Remedy: Try resubmitting the CALL request.

7677 The stored procedure has too many open result set CALL statements.
Explanation: The number of opened CALL statements that return result sets is limited to 15.
Generated By: RTS
For Whom: End User.
Remedy: Rewrite the stored procedure to ALLOCATE and CLOSE the result sets returned by the CALL statements.

7678 No result set exists for procedure %VSTR
Explanation: The ALLOCATE referenced a nonexistent result set. For John this means no result set exists for the given
stored procedure name.
Generated By: RTS
For Whom: End User.
Remedy: Rewrite the stored procedure to ALLOCATE a stored procedure that created a result set.

7680 The result set is already allocated or procedure.
Explanation: The procedure already has an open cursor associated with a result set.
Generated By: RTS
For Whom: End User.
Remedy: Close the cursor before allocating the next result set.

7681 Too many dynamic SQL statements are prepared in the stored procedure (%FSTR).
Explanation: Trying to prepare a dynamic sql statement when the number of dynamic sql statements already prepared
in the stored procedure is MAX_DYNSQL_ALLOWED.
Generated By: RTS Modules.
For Whom: End User.
Remedy: DEALLOCATE any other dynamic sql statement before submitting the request.

7682 OPEN/EXECUTE/DEALLOCATE PREPARE attempted on a unprepared dynamic sql in the stored procedure (%FSTR).
Explanation: The stored procedure in execution is trying to OPEN a cursor, EXECUTE, or DEALLOCATE PREPARE
using a dynamic sql which is not prepared yet.
Generated By: RTS Modules.
For Whom: End User.
Remedy: PREPARE the dynamic sql statement before using OPEN or DEALLOCATE PREPARE statement and resubmit
the request.

7683 Invalid statement specified inside a dynamic declare cursor/SQL statement.
Explanation: For dynamic declare cursor: Certain SQL statements are not allowed inside the dynamic declare cursor
statement. For instance, transaction control statements and CALL SQL statement.
For dynamic SQL statements: Multi-statements are not allowed inside the dynamic SQL statements.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Remove the statement from the declare cursor/SQL statement, recreate the stored procedure, and resubmit the
request.

7685 Multistatement request not supported for mixed statement types.
Explanation: The stored procedure submitted a muli-statement request. The request was mixed with statments that can
support option 3/4 and statements that can only support option 1.
Generated By: Par and Dis modules
For Whom: The stored procedure programmer
Remedy: Separate requests can support the statements.

7686 Inline Lobs access from XSPs with Result Sets are not supported.
Explanation: Inline Lobs access from XSPs with Result Sets are not supported.
Generated By: Par and Dis modules
For Whom: The stored procedure programmer
Remedy: Use Static Locator ’S’ in options parcel.

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