Teradata SQL Error and Failure Codes from Error 9818 To 9827

9818 Warning: XML Plan can’t be logged since the request is either not eligible for IPE or does not qualify.
Explanation: Request specified using DIAGNOSTIC DUMP XMLPLAN is either not eligible for IPE or doesnot qualify.
Hence, XML plan can’t be logged.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right request should be resubmitted with diagnostic DUMP XMLPLAN that is eligible for IPE
and also qualify for IPE.

9819 Warning: XML Plan can’t be applied since the request is either not eligible for IPE or does not qualify.
Explanation: Request specified using DIAGNOSTIC SET XMLPLAN is either not eligible for IPE or doesnot qualify.
Hence, XML plan can’t be applied.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right request should be resubmitted with diagnostic SET XMLPLAN that is eligible for IPE and
also qualify for IPE.

9820 A table cannot have more than one system-time period.
Explanation: A table must have only one SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the additional SYSTEM_TIME column and resubmit.

9821 System-versioning cannot be specified without system-time period.
Explanation: A table can be a system-versioned table only if SYSTEM_TIME period is present in the table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Add SYSTEM_TIME column to the table and resubmit.

9822 The ValidTime column must be defined using a derived period definition in a systemversioned table.
Explanation: If the table is a system-versioned table then the ValidTime column in the table must be defined using
derived period.
Generated By: RES modules.
For Whom: The end user.
Remedy: Define ValidTime column using derived period and resubmit.

9823 Invalid system-time period definition.
Explanation: The data type of the start and end columns of the SYSTEM_TIME column must be of data type TIMESTAMP(
6) WITH TIME ZONE. The start column must be defined with GENERATED ALWAYS AS ROW START and end
column must be defined with GENERATED ALWAYS AS ROW END. The columns with GENERATED ALWAYS AS ROW
START and GENERATED ALWAYS AS ROW END must participate only in SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Correct the SYSTEM_TIME column definition and resubmit.

9824 Invalid use of system-time period start or end column specification.
Explanation: The columns with GENERATED ALWAYS AS ROW START and GENERATED ALWAYS AS ROW END
specification must participate only in SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the GENERATED ALWAYS AS ROW START or GENERATED ALWAYS AS ROW END specification
and resubmit.

9825 A table cannot have both TransactionTime period and system-time period.
Explanation: A table cannot have both TransactionTime column and SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove either the TransactionTime column or the SYSTEM_TIME column and resubmit.

9826 The column name specified in the without overlap specification must be a ValidTime column
defined using derived period.
Explanation: If the unique or primary key constraint is defined with <without overlaps specification>, then the Valid-
Time column name specified in the <without overlaps specification> must be of a column defined with derived period definition.
Generated By: RES modules.
For Whom: The end user.
Remedy: Define the ValidTime column using derived period definition and resubmit.

9827 The start or end column of a system-time period cannot be part of a unique column list.
Explanation: The start or end column of a system-time period must not be included in the unique or primary key column
list.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove start or end column of the system-time period from the unique or primary key column list and resubmit.

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