Teradata SQL Error and Failure Codes from Error 7687 To 7703

SQLServerF1_Header_Small

7687 Data type not supported for dynamic fetch.
Explanation: A data type used in a FETCH of a dynamic cursor or for an ALLOCATE is not supported.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Remove the unsupported data type.

7688 Error occurred generating Evl code for dynamic fetch.
Explanation: An error occurred trying to generate the code for a FETCH of a dynamic cursor or for an ALLOCATE.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Check the data types for the FETCH.

7689 Invalid dynamic SQL statement.
Explanation: Certain SQL statements are not allowed inside the dynamic prepare and execute. For instance, transaction
control statements and CALL SQL statement.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Remove the statement from the prepare and execute, recreate the stored procedure, and resubmit the request.

7691 Table used in cursor select is restructured from compile-time to run-time.
Explanation: The table definition is changed from SP creation to SP execution. That is, the column data types and sizes
might have changed and
the current table structure may not be compatible with cursor definition.
Generated By: RTS modules.
For Whom: End User.
Remedy: Recreate the Stored Procedure with current table definition and resubmit the request.

7692 Maximum using row length exceeded
Explanation: The Using Row components size exceeds the 64K size boundary.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Reconstruct the variables in the call statement to fit within SYSMAXROW size.

7693 User-defined exception is raised from stored procedure
Explanation: User attempted to raise a user-defined exception explicitly through a SIGNAL or RESIGNAL statement in
the stored procedure and the exception is not handled.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Provide a handler for the user-defined exception. Then recreate the corrected stored procedure and resubmit
the request.

7694 An existing result set Cursor is opened from stored procedure.
Explanation: An existing result set cursor is already open from nested stored procedure and it is not closed in either
outer sp or in inner sp.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Close the cursor before submitting the request.

7695 Invalid input parameter specified for a Macro or Stored Procedure
Explanation: When executing a Macro or Stored Procedure, a user can only specify the valid values for its parameters.
Specifying invalid parameters will result in an error.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Correct the statement with valid parameters and resubmit the request.

7700 MDS error range values start.
Explanation: Not used. Place holder for start of MDS error values.
Generated By: None
For Whom: None
Remedy: None

7701 Insufficient memory to process a new transaction.
Explanation: Not enough memory to allocate structures for a new transaction.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7702 Insufficient memory to process new transaction message.
Explanation: Not enough memory to process a new transaction message.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

7703 Insufficient memory to save new transaction message.
Explanation: Not enough memory to copy the new message in MDS memory structures.
Generated By: MDS Gateway
For Whom: System Administrator
Remedy: None

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