Teradata SQL Error and Failure Codes from Error 5373 To 5385

SQLServerF1_Header_Small

5373 Internal error: The Title must be a constant of Unicode character data type.
Explanation: The Title is not a constant of Unicode character data type.
Generated By: OPT modules.
For Whom: End User.
Remedy: Save all the relevant information and the dump, and contact your support representative.

5374 Internal error: The Comment must be a constant of Unicode character data type.
Explanation: The Comment is not a constant of Unicode character data type.
Generated By: OPT modules.
For Whom: End User.
Remedy: Save all the relevant information and the dump, and contact your support representative.

5376 _Kanji1 is not a valid qualifier for constant character strings.
Explanation: The _Kanji1 can only be used as _Kanji1 ’hex string’XC.
Generated By: Lexer.
For Whom: End User.
Remedy: Correct the statement and resubmit it. Use the new form: “_Kanji1 ’…’XC”.

5377 Internal error: Expected character strings of the same type.
Explanation: Processing two character strings that do not have the same character data type (e.g., Latin1).
Generated By: OPT modules.
For Whom: End User.
Remedy: Save all the relevant information and the dump, and contact your support representative.

5378 User has no right to convert the table headers.
Explanation: Someone run the ALTER TABLE CONVERT TABLE HEADER statement without issuing the diagnostic
convert.
Generated By: Resnametb modules.
For Whom: End User.
Remedy: Submit “Diagnostic Convert ON” before running the ALTER TABLE CONVERT TABLE HEADER statement.

5379 Internal Error: Requested internal memory is more than the allowed maximum.
Explanation: An attempt to obtain the memory for building a string constant failed. The requested memory was longer
than the maximum allowed (62000 bytes).
Generated By: Syntaxer.
For Whom: System Support Representative.
Remedy: This is an internal problem, not a user error. If this problem persists, contact your support representative.

5380 Internal error: Unexpected character Data type.
Explanation: Encountered an unexpected character data type while processing a character expression.
Generated By: PAR modules.
For Whom: End User.
Remedy: Save all the relevant information and the dump, and contact your support representative.

5381 Duplicate column names as result of rename column request.
Explanation: Duplication of column name is caused by Alter Table Rename request.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

5382 The word APPLY is not spelled correctly in the Release Mload statement.
Explanation: The user attempted to release an Mload Apply Phase Lock but failed to supply the correct optional clause
in the Release Mload statement. The clause should be ’IN APPLY’.
Generated By: OphERE
For Whom: End User.
Notes: None.
Remedy: Resubmit the Release Mload statement using the word APPLY.

5383 CHARACTER SET specified for non-CHAR data.
Explanation: The user tried to specify CHARACTER SET for data with a type other than CHAR or VARCHAR, or in a
USING clause for non-GRAPHIC character data.
Generated By: SYN, RES and OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

5384 INTERNAL ERROR: Out of TLS Indexes.
Explanation: Out of WinNT TLS indexes.
Generated By: Parser.
For Whom: System Support Representative.
Remedy: This is an internal problem, not a user error. If this problem persists, contact your support representative.

5385 INTERNAL ERROR: Can’’t write TLS value.
Explanation: An attempt to store a TLS value failed.
Generated By: Parser.
For Whom: System Support Representative.
Remedy: This is an internal problem, not a user error. If this problem persists, contact your support representative.

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