Teradata SQL Error and Failure Codes from Error 5627 To 5638

SQLServerF1_Header_Small

5627 Column “%VSTR” exceeds system limit for COMPRESS.
Explanation: The list of compress value defined for a column exceeds the maximum column size for the ’compressvaluelist’
field in DBC.TVFields table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Reduce the number of compress values for the column.

5628 Column %FSTR not found in %VSTR.
Explanation: Each column reference in a query with one or more subqueries must refer to a table or view in the FROM
clause of the non-correlated subquery in which it is referenced. If not, and the column is qualified with a table or view
name, that table or view is implicitely added to the FROM CLAUSE of the current subquery. Prior to Teradata V2R4.1,
unqualified column references would also cause a table or view from an outer query block containing that column to be
added to the current subquery’s FROM clause.
As of V2R4.1, if a column reference is unqualified and cannot be found in any of the tables or views at the current non-correlated
subquery level, an error is returned indicating the column could not be found.
For correlated subqueries, if a column reference in the select expression list is unqualified and can not be found in any of
the tables or view in the current correlated subqery level, an error is returned indicating the column couldn’t be found.
DR85798-sm210100-01 – For the unqualified column reference in the correlated condition an error or a warning may be
reported depending on the settings of dbs internal parameter CheckCorrColumnRef. This parameter takes three values.
N – For the unqualified column reference in the correlated condition, if the column is not found in any of the tables,views in
the current correlated subquery level or outer queries an error is reported. W – For the unqualified column reference in the
correlated condition, if the column is not found in any of the tables,views in the current correlated subquery level an warning
is reported E – For the unqualified column reference in the correlated condition, if the column is not found in any of the
tables,views in the current correlated subquery level an warning is reported.
The unqualified column %FSTR could not be found in any of the tables or views in the FROM CLAUSE of the query or subquery
at the subquery nesting level of the offending column reference.
%VSTR is the list of tables and views referenced in the FROM CLAUSE of the query block containing the column reference
that could not be resolved.
Generated By: RES modules.
For Whom: End User.
Remedy: Check the spelling of the column name, or see if the table or view in which the column exists is correctly referenced.
If the item named in this message is not intended to be a column, but is intended to be data, verify that you are using
the correct syntax to specify that data type (eg., alphanumeric constant should be enclosed in quotes). correct as appropriate
and re-submit the query.

5630 SAMPLEID must be specified with one or more non-SAMPLEID columns.
Explanation: SAMPLEID must be specified with one or more non-SAMPLEID columns eg: select SAMPLEID, col1, …
from …;
Generated By: OptBySamp
For Whom: End User.
Remedy: None.

5632 Index analysis log entry is bad.
Explanation: The error occurs when the restart fails to load the analysis status from the log entry in the QCD.Analysis-
Log table.
Generated By: Opt modules.
For Whom: End User.
Remedy: Delete the rows from the QCD.AnalysisLog table and submit INITIATE INDEX ANALYSIS statement

5634 The specified workoad is too complex for analysis.
Explanation: The number of tables considered by an Index Wizard Analysis cannot exceed 1024. * <- DR113879-
sb230098-01 *
Generated By: RES modules.
For Whom: End User. * DR113879-sb230098-01-> *
Remedy: Reduce the number of tables by specifying an explicit list of tables in the INITIATE INDEX ANALYSIS|INITIATE
PARTITION ANALYSIS statement.Alternatively,reduce the number of queries defined in the specified workload. * <-
DR113879-sb230098-01 *

5635 Workload is already being analyzed.
Explanation: The workload name specified in the INITIATE INDEX ANALYSIS statement is being analyzed when the
user submitted the SQL INITIATE INDEX ANALYSIS statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Either submit a RESTART INDEX ANALYSIS statement if a CHECKPOINT was specified for the original SQL
INITIATE INDEX ANALYSIS statement or remove the records for the workload from the AnalysisLog and resubmit the
request.

5636 No queries exist in workload ID %VSTR.
Explanation: The workload specified does not contain any associated queries. It is essentially an empty workload.
Generated By: MGC
For Whom: End User.
Remedy: Verify that the queries referenced in the workload exist in the QCD. Missing queries can be attributed to failed
INSERT EXPLAIN statements or manual deletion from the QCD. If missing, recapture the queries into the QCD. If all relative
queries are present, drop and recreate the failed workload.

5637 Specified workload does not exist in ’%DBID’ database.
Explanation: The specified Index Wizard workload does not exist in the specified Query Capture Database. * <-
DR113879-sb230098-01 *
Generated By: RES modules.
For Whom: End User. * DR113879-sb230098-01-> *
Remedy: Verify the specified workload name. * <- DR113879-sb230098-01 *

5638 No match found for specified tables in the workload ’%VSTR’.
Explanation: The tables specified in the Index Wizard Analysis statement are not referenced in any of the queries of the
specified Workload. * <- DR113879-sb230098-01 * * DR128941-SB230098-01-> * or None of the tables in the specified Index
Wizard Analysis statement can be analyzed for new indexes.Certain table types such as Join Indexes and tables with No
Primary Index (NOPI) do not qualify for Analysis. * <- DR128941-SB230098-01 *
Generated By: RES modules.
For Whom: End User. * DR113879-sb230098-01-> * * DR128941-SB230098-01-> *
Remedy: Verify the specified table names and/or table types. * <- DR128941-SB230098-01* * <- DR113879-sb230098-01*

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