Teradata SQL Error and Failure Codes from Error 5359 To 5372

5359 Not authorized on %VSTR.
Explanation: The CREATE AUTHORIZATION failed because the authorization information is not valid on the number
of specified nodes.
Generated By: RES modules.
For Whom: End User.
Remedy: If the authorization failed then either provide the correct information for the DOMAIN (Windows), USER
name and PASSWORD. Alternatively determine why the authorization is not valid.
An information log entry is generated for each node where the authorization failed. The information provided is the OS
user name that the authorization was attempted for and the host, session, and database user name. The log entry also
serves to warn the site of all failed authorization attempts as a security audit.

5361 The compress value must be in the repertoire of the character column.
Explanation: The COMPRESS phrase was used on a character column with a value that is not in the repertoire of the column.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5362 Internal error: The default value must be a constant of Unicode character data type.
Explanation: The expected DEFAULT value must be 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.

5363 The default value must be in the repertoire of the character column.
Explanation: The DEFAULT phrase was used on a character column with a value that is not in the repertoire of the column.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5366 The resulting substring is larger than expected.
Explanation: This error is returned when trying to add SO and SI to the result of a substring function and the length of
the result exceeds the allocated destination buffer.
Generated By: FLT Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5368 Name %VSTR is longer than 30 bytes when exported to KanjiEBCDIC.
Explanation: An object name was entered which when exported to Kanji character sets is longer than 30 bytes.
Generated By: RES modules.
For Whom: End User.
Notes: The exported length of an object name in KanjiEBCDIC is calculated as follows: ASCII + Katakana + (2 * JIS X
0208) + SO + SI where: ASCII = the number of basic LATIN (ASCII) characters, KATAKANA = the number of half-width
KATAKANA characters, JIS X 0208 = the number of JIS X 0208 characters, SO = the number of transitions from
ASCII/KATAKANA to JIS X 0208, SI = the number of transitions to ASCII/KATAKANA from JIS X 0208.
Remedy: Correct the statement and resubmit it.

5369 Name %VSTR is longer than 30 bytes when exported to KanjiEUC.
Explanation: An object name was entered which when exported to Kanji character sets is longer than 30 bytes.
Generated By: RES modules.
For Whom: End User.
Notes: The exported length of an object name in KanjiEUC is calculated as follows: ASCII + (2 * Katakana) + (2 * JIS X
0208) where: ASCII = the number of basic LATIN (ASCII) characters, KATAKANA = the number of half-width
KATAKANA characters, JIS X 0208 = the number of JIS X 0208 characters,
Remedy: Correct the statement and resubmit it.

5370 Conversion between numeric values and Graphic data is not allowed.
Explanation: A numeric value is being translated to Graphic or vice-versa using the CAST function.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit it.

5371 Internal error: Cannot convert character of one type to character of a different type.
Explanation: This is a strictly an internal error. Module OPTWEXP2 processes conversion. But conversion between characters
of different type is done by another module.
Generated By: OPTWEPX2 module.
For Whom: System Support Representative
Remedy: Save all the relevant information and the dump, and contact your support representative.

5372 Internal error: The StartupString must be a constant of Unicode character data type.
Explanation: The StartupString is not 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.

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