Teradata SQL Error and Failure Codes from Error 3639 To 3650

SQLServerF1_Header_Small

3639 Comparing BYTE data with other types is illegal.
Explanation: BYTE data may only be compared with BYTE data.
Generated By: OPT modules.
For Whom: The End User.
Remedy: User has probably referenced wrong column.

3640 Comparing BYTE data in column %VSTR with other types is illegal.
Explanation: BYTE data may only be compared with BYTE data.
Generated By: OPT modules.
For Whom: The End User.
Remedy: User has probably referenced wrong column.

3641 BYTE data cannot be assigned to column %VSTR.
Explanation: BYTE data cannot be assigned to a column of type other than BYTE. User has probably referenced a wrong
column.
Generated By: OPT modules.
For Whom: The End User.
Remedy: Correct the SQL statement and resubmit.

3642 Non-BYTE data cannot be assigned to column %VSTR.
Explanation: Non-BYTE data cannot be assigned to a column of type BYTE. User has probably referenced wrong column.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the SQL statement and resubmit.

3643 Numeric operation on BYTE data is illegal.
Explanation: BYTE data cannot be used in most numeric operations.
Generated By: OPT modules.
For Whom: The End User.
Remedy: User has probably referenced wrong column.

3644 Numeric operation on BYTE data in column %VSTR is illegal.
Explanation: BYTE data cannot be used in most numeric operations.
Generated By: OPT modules.
For Whom: The End User.
Remedy: User has probably referenced wrong column.

3645 COLLATION option not supported at this level.
Explanation: COLLATION option is valid only at session and user level, not in defining individual fields or modifying
expressions.
Generated By: OPT modules.
For Whom: The End User.
Remedy: Remove COLLATION option.

3647 NULL may not be used as the argument for an aggregate function.
Explanation: It is not legal to request the MIN, MAX, AVG, SUM, or COUNT of NULL.
Generated By: OPT modules.
For Whom: The End User.
Remedy: User has entered a query that is not allowed. The aggregate function referencing NULL should be removed
from the query. Then the query can be resubmitted.

3648 Expected subquery is missing.
Explanation: If an expression list is used as the left operand of IN or NOT IN, the right operand must be a subquery.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3649 Compressed NULL and NOT NULL cannot coexist for column %VSTR.
Explanation: A NOT NULL column cannot specify the COMPRESS attribute with no value. A column which specifies
COMPRESS with no value cannot be altered to NOT NULL.
Generated By: OPT modules.
For Whom: End User.
Remedy: If the column does not exist yet, remove the COMPRESS option or indicate a value to be compressed. Otherwise,
(1) if the table is empty, replace the column with ALTER TABLE DROP first, then ALTER TABLE ADD to recreate the
column properly, (2) if the table is not empty, create a new table with proper definition, reload data from the old table to the
new table, and then drop the old table.

3650 Internal error: Unexpected ParTreePtr@.Kind encountered.
Explanation: A node in a Parser Tree has a Kind not valid for the context in which it was encountered. Most commonly
this will be in an OTHERWISE for a CASE on leaf type. The root cause is an internal error in the parser.
Generated By: RES, OPT and GEN modules.
For Whom: System Support Representative.
Remedy: Save all relevant information, and contact your support representative.

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