Teradata SQL Error and Failure Codes from Error 6961 To 6971

6961 Statistics are not available in the source table.
Explanation: This is a warning code only. Warning is reported when the user specifies the AND STATISTICS|
STATS|STAT clause in a CREATE TABLE AS and the source table in the CREATE AS does not have any statistics collected
or statistics are not available on the eligible columns in the target table.
Generated By: OPD modules.
For Whom: End User.
Remedy: Informational message only.

6962 Statistics cannot be copied.
Explanation: This is a warning code only. Warning is reported when the user specifies the AND STATISTICS|
STATS|STAT clause in a CREATE TABLE AS and none of the available statistics on the source table are eligible be
copied to the target table either due to changing data or due to changing cardinality in the target table.
Generated By: OPD modules.
For Whom: End User.
Remedy: Informational message only.

6963 Multi-column statistics that exceed the limit have not been copied.
Explanation: This is warning code only. Warning is reported when the user specifies the AND STATISTICS|
STATS|STAT clause in a CREATE TABLE AS and the number of multiple-column statistics exceed the limit. Multicolumn
statistics that exceed the limit are not copied.
Generated By: OPD modules.
For Whom: End User.
Remedy: Informational message only.

6964 Only some of the statistics were copied to the target table.
Explanation: This is warning code only. Warning is reported when the user specifies the AND STATISTICS|
STATS|STAT clause in CREATE TABLE AS and when only some of the statistics on the source table were eligible to
be copied to the target table.
Generated By: OPD modules.
For Whom: End User.
Remedy: Informational message only.
6965 The external stored procedure’s SQL data access and application package are not compatible.
Explanation: Either * The XSP specified either READS SQL DATA or MODIFIES SQL DATA But, the external literal
does not include an application package. or * The XSP included an application package, but has NO SQL access.
Generated By: OPD modules.
For Whom: XSP developer.
Remedy: Resubmit the request with the appropriate application package. Or include a sql data access clause with access
greater than NO SQL.

6966 External Stored Procedure specified with SQL access must run in protected mode.
Explanation: The user attempted to alter the XSP with SQL access to run in not protected mode. That is not allowed.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not resubmit the request.

6968 Attempted to modify SQL.
Explanation: The SQL procedure either has READS SQL access, but has attempted to read or modify SQL data, or it has
called another procedure that has.
Generated By: TEQ modules.
For Whom: End User.
Remedy: Replace the procedure with higher SQL access or so that it does not read SQL.

6969 %VSTR is not allowed on a Period column.
Explanation: Period Data Type column can not have these attributes: COMPRESS or CHECK attributes.
Generated By: Parser.
For Whom: End User.
Remedy: Remove the Period column from the statement or rewrite the statement without using the prohibited attribute
and resubmit.

6970 A foreign key is not allowed on a Period column.
Explanation: A Period column is not allowed to be a foreign key column.
Generated By: Parser.
For Whom: End User.
Remedy: Rewrite the statement without listing the PERIOD column in a foreign key and re-submit.

6971 An index is not supported on a Period column.
Explanation: An index is not allowed on Period column. The index may be due to PRIMARY KEY constraint or
UNIQUE constraint on the Period column.
Generated By: Parser
For Whom: End User.
Remedy: Remove the index, PRIMARY KEY constraint, or UNIQUE constraint, and re-submit.

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