Teradata SQL Error and Failure Codes from Error 7631 To 7649

SQLServerF1_Header_Small

7631 Fetch/Close attempted on a closed cursor in the stored procedure (%FSTR).
Explanation: The stored procedure in execution is trying to fetch a row from a closed cursor.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Check the reason for the cursor getting closed, recreate the stored procedure to handle the exception, and
resubmit the request.

7632 No rows returned/updated/deleted by the SQL statement.
Explanation: This code is returned in the following situations: (a) SELECT returned no rows (b) No rows updated by
UPDATE SQL (c) No rows deleted by DELETE SQL.
Generated By: RTS Modules.
For Whom: End User.
Remedy: It is a warning message.

7638 %FSTR: Error allocating a segment; segget failed with return code (%VSTR).
Explanation: This is stored procedure run-time subsystem internal error. This error is reported when the segget PDE call
fails.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Save the test case and contact your support representative for an analysis of the log/dump.

7639 %FSTR: Error opening object code file (%VSTR).
Explanation: This is stored procedure run-time subsystem internal error. This error is reported when a problem is
encounterd in opening the stored procedure object code file.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Retry the test-case. If the problem still persists, save the test case and contact your support representative for an
analysis of the log/dump.

7644 %FSTR: Error in RAR message; %VSTR.
Explanation: This is stored procedure run-time subsystem internal error. This error is reported when a problem is
encountered in sending express request for fetching the stored procedure object code. procedure.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Save the test case and contact your support representative for an analysis of the log/dump.

7645 %FSTR: Error writing into file.
Explanation: This is stored procedure run-time subsystem internal error. This error is reported when a problem is
encountered while writing into the stored procedure object code file or log files during SP or DB spoil operations. This can
occur when the directory has no space. This is a system disk directory NOT part of the database.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: The remedy is to make sure the directory has enough space to hold a SP DLL (DLL: Dynamic Linked Library)
or log files for spoil operations.

7646 %FSTR:Invalid variable index (%VSTR) specified.
Explanation: This is stored procedure run-time subsystem internal error.
This error is reported when the index of variable/parameter is incorrect.
This event is logged in the eventlog with the required RTSInfo structure details.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Re-submit the request. If the problem persists, save a test case and contact your support representative.

7647 %FSTR:Internal SQL failed with return code (%VSTR).
Explanation: This is stored procedure run-time subsystem internal error.
This error is reported when PRINT is failed due to DBS internal error.
This event is logged in the eventlog with the required RTSInfo structure details.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Re-submit the request. If the problem persists, save a test case and contact your support representative.

7648 %FSTR:Data buffer overflow, exceeding maximum buffer size.
Explanation: This is stored procedure run-time subsystem internal error.
This error is reported when data buffer size exceeds MAX_RESPONSE_SIZE (64000).
This event is logged in the eventlog with the required RTSInfo structure details.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Re-submit the request. If the problem persists, save a test case and contact your support representative.

7649 %FSTR:Presence bit vector is NULL.
Explanation: This is stored procedure run-time subsystem internal error.
This error is reported when presence bit vector is NULL while building the data buffer or reading the response.
This event is logged in the eventlog with the required RTSInfo structure details.
Generated By: RTS Modules.
For Whom: End User and System Support Representative.
Remedy: Re-submit the request. If the problem persists, save a test case and contact your support representative.

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