Teradata SQL Error and Failure Codes from Error 5566 To 5579

5566 Error in Hash Index DDL, %VSTR.
Explanation: This error covers all the syntax exceptions for Hash Index DDL, including create and delete hash index.
Generated By: RES modules.
For Whom: End User.
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to adhere to
hash index syntax rules and resubmit the request.

5567 Error in Using Hash Index, %VSTR.
Explanation: This error code covers all the errors caused by treating the hash index as table. For example deletes,
updates, inserts, .. etc are not allowed on a hash index.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not treat a hash index like a table.

5568 SQL statement is not supported within a stored procedure.
Explanation: This error occurs when in one of the following situations: a. An unsupported SQL statement is specified in
a stored procedure using the dynamic SQL feature of stored procedures. For instance, DATABASE statement, SET SQL
statements, multi statement requests, CREATE USER/DATABASE statement without FROM clause, SELECT – INTO SQL
or CALL SQL. This is a run-time error.
b. An unsupported SQL statement is specified in a stored procedure. For instance, DATABASE statement, SET SQL statements,
INSERT EXPLAIN or a CREATE USER/DATABASE statement without FROM clause. This is a compile-time error.
** ** Comment modified from DDL to SQL with an example for the ** same (INSERT EXPLAIN) ** **DR81152-GM210039-
01**
Generated By: RES Modules.
For Whom: End user.
Remedy: Correct the SQL statement and, recreate the stored procedure if necessary.

5571 Target samples not found.
Explanation: The user attempted to set the samples on the prime keys system name, database name, table name, but the
corresponding row has not been loaded to SystemFE.OptSampleTable.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name, database name or table name specified or dump samples via DIAGNOSTIC DUMP
SAMPLES.

5572 Target samples not set at session level.
Explanation: The user attempted to undo the samples on the prime keys system name, database name, table name at
session level, but the corresponding samples has not been set.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name, database name, table name or the specified level.

5573 Target samples not set at system level.
Explanation: The user attempted to undo the samples on the prime keys system name, database name, table name at
system level, but the corresponding samples has not been set.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name, database name, table name or the specified level.

5574 Number of samples set exceeds the maximum samples limit at session level.
Explanation: The user attempted to emulate random amp samples for a table at a session-wide level, but the maximum
number of tables for which we can emulate samples has already been reached.
Generated By: OPT modules.
For Whom: End User.
Remedy: Unset the emulation of random amp samples on other tables at the ssession level, or emulate this tables at the
system level.

5575 Number of samples set exceeds the maximum samples limit at system level.
Explanation: The user attempted to emulate random amp samples for a table at a system-wide level, but the maximum
number of tables for which we can emulate samples has already been reached.
Generated By: OPT modules.
For Whom: End User.
Remedy: Unset the emulation of random amp samples on other tables at the system level,or emulate this table at the session level..

5576 The requested replication DDL statement issued from an illegal source.
Explanation: This statement may not be issued directly as a user request and must come through the RCT.
Generated By: RES modules.
For Whom: End User.
Remedy: Resubmit the statement through the Replication Transport.

5578 Statistics cannot be collected on table DBC.’%VSTR’ .
Explanation: Statistics cannot be collected on DBC internal tables SW_Event_Log, HW_Event_Log, EventLog, Global,
SessionTbl or any ResUsage table.
Generated By: RES modules.
For Whom: DBA User.
Remedy: None.

5579 Target samples were overwritten at session level.
Explanation: The user attempted to set the samples on the prime keys system name, database name, table name at session
level, but the corresponding samples has already been set.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name, database name, table name or the specified level.

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