Teradata SQL Error and Failure Codes from Error 9808 To 9817

SQLServerF1_Header_Small

9808 Warning: Use of a discontinued diagnostic detected
Explanation: A discontinued diagnostic setting is in effect.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Remove the discontinued diagnostic setting.

9809 Begin or end columns of a derived period cannot be part of a primary index if derived period is a temporal column.
Explanation: Derived period begin or end column can not be part of Primary Index.
Generated By: OPD modules
For Whom: The end user.
Remedy: Remove derived period begin or end column from primary index and submit.

9810 Warning: Ignoring invalid XML plan in effect for emulation. %s
Explanation: XMLPlan specified using DIAGNOSTIC SET XMLPLAN doesn’t match the current optimizer plan. Ignoring
the requested plan and continuing with the current plan. See the event log for the detected differences.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right XML plan specified. Check system and request names for correctness. Make sure to emulate
the other factors such as costs, statistics, and random AMP samples that influence the optimizer plans.

9811 Warning: Ignoring DUMP XMLPLAN diagnostic.
Explanation: Diagnostic DUMP XMLPLAN is ignored either because of not applicable for this request or failures in saving
the feedback information in the XML document.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure DUMP XML plan is used with non cached and for requests producing dynamic plans.

9812 Duplicate row exists in SystemFE.Opt_XMLPlan_Table.
Explanation: Diagnostic DUMP or SET XMLPLAN is issued with duplicate values for the combination of system name
and request name columns.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit diagnostic DUMP or SET XMLPLAN with non-duplicate values for for the combination of system
name and request name columns in SystemFE.Opt_XMLPlan_Table.

9813 XML plan does not exist in SystemFE.Opt_XMLPlan_Table.
Explanation: Unable to locate a row in SystemFE.opt_xmlplan_table with the specified system name and request name.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Check the system and request name for correctness or import the captured XMLPlan from the source system
before issuing this diagonstic.

9814 EXPLAIN is not supported for Diagnostic DUMP and SET XMLPLAN.
Explanation: Diagnostic DUMP/SET XMLPLAN is is supported with EXPLAIN modifier.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Submit diagnostic DUMP/SET XMLPLAN without EXPLAIN modifier.

9815 BLOCKCOMPRESSION attribute were not copied.
Explanation: This is only a warning to inform the user that the target table will not be inherited BLOCKCOMPRESSION
attribute from the source table.
For example,
CREATE VOLATILE TABLE Table1 AS Table2 WITH [NO] DATA;
CREATE GLOBAL TEMPORARY TABLE Table1 AS Table2 WITH [NO] DATA;
BLOCKCOMPRESSION attribute on Table2 (if exist) will not be copied to Table1.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

9816 XML plan logging is disabled in DBSControl settings.
Explanation: Diagnostic DUMP XMLPLAN failed since DBSControl DisableXMLPLANLogging option is disabled.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit Diagnostic DUMP XMLPLAN after enabling DisableXMLPLANLogging DBSControl option.

9817 Diagnostic DUMP/SET XMLPLAN is in effect already.
Explanation: Diagnostic DUMP/SET XMLPLAN failed since it is already active in the same session.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit Diagnostic DUMP/SET XMLPLAN in a new session or after deactivating the existing one.

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