Teradata SQL Error and Failure Codes from Error 3662 To 3672

SQLServerF1_Header_Small

3662 Concatenation between BYTE data and other types is illegal.
Explanation: The user tried to concatenate a BYTE data type with a non BYTE data type.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3663 Index of BYTE data with other types is illegal.
Explanation: The user tried to obtain the index of a BYTE data type with a non BYTE data type.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3664 Request number out of sequence.
Explanation: The request number is out of sequence. Each request in a session should be assigned a request number
which is greater than that of the previous request.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3665 END TRANSACTION without CHECKPOINT LOADING END.
Explanation: This error occurs only if there is an error in the fast load protocol. The INSERT statement in a fast load must be followed at some point by a CHECKPOINT END before an END TRANSACTION is issued.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3666 This View has too many columns to Store or Retrieve comments.
Explanation: When a View has more than 50, entries are not made in the dictionary table Dbc.TVFields (View DBC.Columns).
Comments are normally stored in this table but cannot be stored or retrieved for Views with a large number of columns.
Generated By: OPT modules.
For Whom: End User.
Remedy: None. Comments cannot be stored or retrieved for Views with more columns than the recommended limit.

3667 CHECKPOINT statement used incorrectly.
Explanation: A CHECKPOINT statement was preceded by a DELETE, INSERT or UPDATE statement within an explicit
or implicit transaction.
Generated By: OPT modules.
For Whom: End User.
Remedy: Restructure the operation.

3668 A table listed in the Dictionary is not present.
Explanation: The database Resolver has found an internal identity for a named table in Dictionary table DBC.TVM and
a subsequent effort to access the table header to complete compilation of the query has found no table with that identity.
Generated By: MGC modules.
For Whom: System Engineer or Database Administrator.
Remedy: If the table was being deleted by another session, a retry should indicate that the table is not present. If this error persists on retry, there is an entry in DBC.TVM that does not represent an existing table. The most likely reason would be an uncompleted RESTORE operation.

3669 More than one value was returned by a subquery.
Explanation: If a subquery is used in a unquantified predicate, the subquery must return either no values or one value.
Generated By: OPT modules.
For Whom: End User.
Remedy: Revise the predicate by specifying ANY before the subquery or revise the subquery so that it returns no values
or one value.

3670 ’%VSTR’ is not a User.
Explanation: The specified item is a database but not a User. Users have passwords and logons are permitted to Users. A
database has no password and cannot be logged onto.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3671 An invalid HostId has been specified.
Explanation: The range for Host Id’s is 1 to 1023. A value outside of this range or a non-integer value has been specified,
or a value in range has been specified in a context where the HostId must be in the current or next configuration for the system,
but is not.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3672 No logging to end.
Explanation: The user tried to do an END LOGGING statement and there was no data to end.
Generated By: OPT modules.
For Whom: End User.
Remedy: Do a BEGIN LOGGING prior to the END LOGGING.

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