Teradata SQL Error and Failure Codes from Error 7596 To 7608

SQLServerF1_Header_Small

7596 Operation not allowed: %DBID.%TVMID is being archived.
Explanation: This error occurs when the user issues the LOGGING ONLINE ARCHIVE OFF or drop table statement
during the archive.
Generated By: AMP.
For Whom: End User.
Remedy: Do not issue the LOGGING ONLINE ARCHIVE OFF or drop table statement until the archive job completes or
aborts.

7597 Operation not allowed: GROUP LOCK/ GROUP READ LOCK is not allowed on logging activated tables.
Explanation: This error occurs when the user uses the option GROUP READ LOCK or GROUP LOCK on logging activated
tables.
Generated By: AMP.
For Whom: End User.
Remedy: Do not use GROUP READ LOCK or GROUP LOCK option on logging activated tables.

7598 Operation aborted due to maximum number of online archive active logs.
Explanation: This error occurs when the system reaches maximum limit on the number of tables on which logging is
active. The maximum limit is 10,000.
Generated By: AMP.
For Whom: End User.
Remedy: Balance online archive jobs. Turn off online archive logging for for tables or wait for completion of the archive job(s).

7600 Internal error in RTS subsystem.
Explanation: This is stored procedure run-time subsystem internal error.
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.

7601 Case not found for CASE statement.
Explanation: None of the search conditions of CASE statement is true and there is no ELSE clause specified.
Generated By: RTS Modules.
For Whom: End user.
Remedy: Correct the CASE statement, recreate the stored procedure, and resubmit the request.

7602 Illegal usage of variable/parameter/alias %VSTR.
Explanation: This error is reported in one of the following situations: (a) IN parameter, System Variables or Aliases are
passed as arguments for INOUT/OUT parameters of inner stored procedure. (b) OUT parameter is passed as argument for IN/INOUT parameter of inner stored procedure.
Generated By: RTS Modules.
For Whom: End user.
Remedy: Correct the CALL statement, recreate the stored procedure, and resubmit the request.

7603 Unhandled user-defined condition %VSTR.
Explanation: User attempted to raise a condition explicitly through a SIGNAL or RESIGNAL statement and the condition
is not handled in the stored procedure. %VSTR contains the condition name.
Generated By: RTS Modules.
For Whom: End user.
Remedy: Add a handler for the condition, recreate the corrected stored procedure and resubmit the CALL stmt.

7604 Invalid data for condition number.
Explanation: The user specified NULL or a value less than one or greater than the number of conditions stored in the
diagnostics area, in an GET DIAGNOSTICS statement.
Generated By: RTS modules.
For Whom: End User.
Remedy: Check the value of the condition number in the statement, correct as needed, recreate the corrected stored procedure,
and resubmit the request.

7606 Too many cursors are opened in the stored procedure (%FSTR).
Explanation: Trying to open another cursor when the number of cursors already opened in the stored procedure is
MAX_CURSORS_ALLOWED.
Generated By: RTS Modules.
For Whom: End User.
Remedy: Close any other opened cursor before submitting the request.

7607 Referenced cursor is not positioned in a row.
Explanation: This exception is reported while trying to update a cursor which
(a) is not opened or (b) is not fetched or (c) didn’t have any rows to update
Generated By: RTS Modules.
For Whom: End User.
Remedy: Recreate the stored procedure if the cursor is not opened or fetched and resubmit the request or insert data and
resubmit the request.

7608 Mismatch between the number of columns returned by the cursor specification and the fetch target list.
Explanation: The number of columns returned by the cursor SELECT statement do not match the number of stored procedure
output parameters or local variables specified in the fetch target list.
Generated By: RTS modules.
For Whom: End User.
Remedy: Correct the FETCH statement and then recreate the corrected Stored Procedure, and resubmit the request.

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