Teradata SQL Error and Failure Codes from Error 5343 To 5358

5343 This statement is not allowed when the target temporary table is already materialized.
Explanation: The user cannot submit any statement that changes the definition of a base temporary table when there is a
materialized instance of that base temporary table either locally in the current session or in any other sessions.
Generated By: RES modules.
For Whom: End User.
Remedy: Wait until the target table is not referenced by any session then resubmit the request.

5344 Delete Database is not allowed due to materialized temporary tables.
Explanation: Delete database is only allowed when the target database does not contain any materialized temporary
table unless the keyword ALL is specified.
Generated By: OPT modules.
For Whom: End User.
Remedy: Resubmit statement with the keyword ALL.

5346 This character set is not supported.
Explanation: The character set specified is invalid.
Generated By: SYN modules.
For Whom: End User.
Notes: The character set is specified during the creation of a column (CHARACTER SET clause) or during specification of
the character set of a user (DEFAULT CHARACTER SET option). Valid character sets are Unicode, Latin1, KanjiSJIS,
Graphic, or Kanji1.
Remedy: Specify a valid character set and resubmit the request.

5347 Invalid default export table id.
Explanation: An invalid default table id was encountered in the DEFAULT EXPORT option of CREATE USER.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the table id and resubmit statement.

5352 Kanji1 data must be assigned to Kanji1 field.
Explanation: A Kanji1 expression was assigned to a field that is not of type Kanji1.
Generated By: OPT modules.
For Whom: End User.
Notes: These are situations when this error is generated —
The constant expression of an INSERT statement is Kanji1, but the field into which the constant expression is being inserted is not of type Kanji1.
In an INSERT SELECT statement: the character data type of the value being selected is of type Kanji1, but the character data type of the field being inserted to is not of type Kanji1.
In an INSERT SELECT statement: the value being selected is a non constant expression, not of Kanji1 type and the field
being inserted to is of type Kanji1.
In an UPDATE statement: the character data type of the update value is of type Kanji1, but the character data type of the field being updated is not of Kanji1 type.
In an UPDATE statement: the update value is a non-constant expression, not of Kanji1 type and the field being updated to is of type Kanji1.
Remedy: Correct the statement and resubmit it.

5353 The internal form of Graphic, i.e., the XG form, is no longer supported.
Explanation: A literal of the form ’<hex digit(s)>’ XG was entered.
Generated By: Lexer.
For Whom: End User.
Remedy: Correct the statement and resubmit it. Use the new form: “_GRAPHIC ’…’XC”.

5354 Arguments must be of type Kanji1.
Explanation: A function that has more than one argument of character data type has been called with a mix of Kanji1
and non-Kanji1 data types.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5355 The arguments of the CAST function must be of the same character data type.
Explanation: The CAST function does not allow casting a character expression of type A to another character expression
of type B not equal to A.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it or use the TRANSLATE function for conversions between character
types.

5356 One of the characters or code point does not exist within the specified repertoire.
Explanation: A character or code point in the literal does not correspond to characters in the specified DBS form-of-use.
Generated By: Lexer.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5358 Expected an argument of type character.
Explanation: The TRANSLATE or TRANSLATE_CHK function was called with an argument other than character.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

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