Teradata SQL Error and Failure Codes from Error 7986 To 7994

SQLServerF1_Header_Small

7986 Diagnostic BYPASS ACCESSRIGHTS not allowed if logons are enabled.
Explanation: DIAGNOSTIC BYPASS ACCESSRIGHTS is used during the dictionary table conversion. It expects logons
to have been disabled or enabled for DBC when the DBS control flag BypassAccessrights is ON.
Generated By: SYN modules.
For Whom: The DBA.
Remedy: Make sure that logons are disabled.

7987 Internal Error: Assertion violated in Optimizer
Explanation: This error occurs if an assertion failed in the costing or cardinality estimation subsystem of the optimizer.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and the dump, and contact your support representative.

7988 Internal Info: Assertion violated in Optimizer
Explanation: This error occurs if a recoverable assertion failed in the costing or cardinality estimation subsystem of the
optimizer.
Generated By: OPT modules.
For Whom: System Support Representative.
Remedy: Save log information and contact your support representative.

7989 Invalid operand for the %VSTR operator. The operand must have a Period data type that is comparable to the other operand.
Explanation: The operands of the PRECEDES || SUCCEDES || MEETS || CONTAINS operator must have a value of
Period data type. Using of any other value other than Period data type is invalid.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the operands to have value of Period data type and re-submit.

7990 Invalid operands for the %VSTR operator. The operands must have comparable Period data types.
Explanation: The operands of the PRECEDES || SUCCEDES || MEETS || CONTAINS operator must have a value of
Period data type and must be of comparable element type.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the operands to have value of Period data type of comparable element type and re-submit.

7991 Invalid Period argument. Passing an argument corresponding to a parameter with lower precision is not allowed.
Explanation: A Period argument to an UDF, UDM, or XSP must have a precision that is less than or equal to the corresponding
parameter’s precision.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the Period arguments in the statement or the parameters in the UDF , UDM, or XSP to have appropriate
precisions and re-submit.

7992 Invalid input data for period. The beginning bound must be less than the ending bound.
Explanation: The input data parcel for a period contains a beginning bound greater than or equal to the ending bound
resulting in an invalid period value.
Generated By: MOVEROW
For Whom: End User.
Remedy: Correct the period data in the data parcel and re-submit.

7993 Invalid input data for period. The input data precision must not be greater than the described precision.
Explanation: The precision of the seconds value in the input data for a Period value is greater than the described precision
of the Period data type. A time value cannot be converted to a time value of lower precision. For example, if the seconds
value contains the data 53123456 (representing 53.123456) and the element type describes the precision as 3, this data
is invalid. The last three numbers in the data must be zero. 53123000 is valid input for such a data description
Generated By: MOVEROW
For Whom: End User.
Remedy: Correct the described precision and re-submit.

7994 Invalid Period arithmetic operation. One of the operands must be an Interval type.
Explanation: A Period operand must be added to or subtracted from only interval type.
Generated By: Parser modules.
For Whom: End User.
Remedy: Correct the Period arithmetic expression and re-submit.

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