Teradata SQL Error and Failure Codes from Error 5664 To 5678

5664 The user cannot perform aggregate operation on LOBs.
Explanation: Aggregate operations are not allowed on LOBs.
Generated By: OPT modules.
For Whom: End User.
Remedy: Rephrase the request and try again.

5665 Ordered Analytical functions can’t sort by LOBs.
Explanation: Ordered Analytical functions sort rows before performing aggregation. LOBs can not be used in the sort. If
no ORDER BY is specified, then the rows are sorted by all of the columns selected.
Generated By: OPT modules.
For Whom: End User.
Remedy: Add an ORDER BY clause without any LOB columns

5666 LOBs are not allowed in indexes.
Explanation: LOBs are not allowed to be part of an index.
Generated By: OPT modules.
For Whom: End User.
Remedy: Don’t use a LOB in an index.

5669 No restart information found for specified index anlaysis ’%VSTR’.
Explanation: There must be an entry in the AnalysisLog table of the specified QCD in case the indicated index analysis
must be restarted. This may be due to the following reasons: 1. The SQL INITIATE INDEX ANALYSIS statement did not
have any CHECKPOINT clause, hence a RESTART is invalid. 2. The restart record from the AnalysisLog table has been
deleted due to some unknown reasons.
Generated By: RES modules.
For Whom: End User.
Remedy: Submit the SQL INITIATE INDEX ANALYSIS statement to restart the analysis Or check the AnalysisLog table
to restore the lost record and re-submit the SQL RESTART INITIATE INDEX ANALYSIS statement.

5670 LOBs are not allowed to be sorted.
Explanation: A LOB column must be cast to a non-LOB column to be included in an ORDER BY clause or a sort key.
Generated By: OPT modules.
For Whom: End User.
Remedy: Cast the LOB column to a non-LOB column.

5671 LOBs can not be used in selects containing WITH.
Explanation: LOBs are not allowed to be part of a SELECT containing a WITH clause.
Generated By: OPT modules.
For Whom: End User.
Remedy: Cast the LOB column to a non-LOB column.

5672 LOBs are not allowed in the GROUP BY clause.
Explanation: A LOB column must be cast to a non-LOB column to be included in the GROUP BY clause.
Generated By: OPT modules.
For Whom: End User.
Remedy: Cast the LOB column to a non-LOB column.

5673 A Locator to a LOB is not allowed to be returned in Field Mode.
Explanation: A Locator to a LOB value is not allowed to be returned in Field response mode.
Generated By: OPT modules.
For Whom: End User.
Remedy: Return the LOB inline or use another response mode.

5674 LOBs are not allowed to be selected in Record or Indicator modes.
Explanation: LOBs are not allowed to be selected in Record and Indicator response modes.
Generated By: OPT modules.
For Whom: End User.
Remedy: Use MultipartRecord response mode.

5675 Keep Response must be set to return Locators to LOB values.
Explanation: Keep Response must be set to return Locators to LOB values. If Keep Response is not set, the Locator is
invalid.
Generated By: OPT modules.
For Whom: End User.
Remedy: Resubmit the query with Keep Response set.

5677 %VSTR
Explanation: This is an informational message that displays: 1. Whether the statement was fetched from cache 2. Number
of cache hits 3. Number of active slots in the cache 4. Number of bad slots in the cache
Can be used with ’DIAGNOSTIC CACHEDEBUG’.
Generated By: DIS
For Whom: Diagnostic information
Remedy: Not a problem.

5678 The user is not authorized to assign the default role ’%VSTR’.
Explanation: Only the user DBC, or a user granted a role WITH ADMIN OPTION, or a user with an applicable role (current
role or a role nested within it) that is granted a role WITH ADMIN OPTION has the right to assign the role as the
default role to a user in CREATE USER statement.
Generated By: OPD module.
For Whom: End User.
Remedy: Have an authorized user re-submit the request.

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