Teradata SQL Error and Failure Codes from Error 5386 To 5397

SQLServerF1_Header_Small

5386 INTERNAL ERROR: Can’’t read TLS value.
Explanation: An attempt to access 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.

5387 One or more parameters are bad.
Explanation: At least one parameters in the SQL function are bad.
The problem can be one or more of the following: – The size is bad. – The data type is bad. – The parameter is not within the expected value.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the request and resubmit it.

5388 The Pad Expression for TRIM has an incorrect data type or length.
Explanation: The Pad expression for TRIM must be of the same data type as the expression being trimmed, and represent
a single character or byte.
Generated By: OPT modules.
For Whom: End user.
Remedy: Correct the TRIM expression.

5389 The User Default Character Set cannot be GRAPHIC.
Explanation: The user tried to create or modify a user as User Default Character Set GRAPHIC.
Generated By: OPD modules.
For Whom: End User.
Remedy: Chose another Default Character Set and resubmit it.

5390 The Pad or Trim Expression character data type is invalid.
Explanation: The Pad or Trim Expression’s character type cannot be EVLKANJI1.
Generated By: OPT modules.
For Whom: End user.
Remedy: Correct the character type of the Pad or Trim Expression.

5391 Replicated table(s) detected in database.
Explanation: User cannot delete a database which has a replicated table.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop the table from replication group and resubmit the request.

5392 No locking modifier on a subscriber table.
Explanation: Locking modifier is not allowed on a subscriber table if replication override is not ON. Replication has its own mechanism to place a lock on a subscriber system. Therefore, if the target table is a subscriber table and replication
override is not ON, return an error to user.
Generated By: RES modules.
For Whom: End User.
Remedy: None.

5394 The dictionary cache has been spoiled and restored to a consistent state.
Explanation: The dictionary cache was not in a consistent state. It has been spoiled and restored to a consistent state.
This message is for informational purposes only.
Generated By: Parser.
For Whom: System Administrator.
Remedy: The dictionary cache has been returned to a consistent state.

5395 A ARCHIVE, RESTORE or COPY of selected partitions with LOBs is not supported.
Explanation: A ARCHIVE, RESTORE or COPY of selected partitions is not supported for a table defined with one or
more CLOB or BLOB columns.
Generated By: Resolver.
For Whom: End User.
Remedy: Perform a full table archive, restore, or copy instead or do not use LOB columns with selected partition restores
and copies.

5396 An OLD_TABLE or NEW_TABLE alias was referenced without using a subquery.
Explanation: OLD_TABLE and NEW_TABLE aliases refer to set of rows so they must be referenced as a table with a
FROM clause.
Generated By: Parser.
For Whom: User.
Remedy: In the triggered statements and the WHEN clause use a FROM clause to refer to the OLD_TABLE and
NEW_TABLE aliases.

5397 User caused a Parser crash.
Explanation: The user caused a Parser crash.
Generated By: Parser
For Whom: End User.
Remedy: Do not resubmit the query. Contact the Global Support Center.

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