Teradata SQL Error and Failure Codes from Error 6993 To 7417

 

6993 The sample column %VSTR does not match the table’s definition.
Explanation: Random AMP sample emulation cannot be set if the value of the NumIndexes and Fields[0] thru
Fields[NumIndexes-1] columns in the SystemFE.Opt_RAS_Table do not match the number of indexes on the table and the
number of fields that comprise each index respectively as defined in the Data Dictionary.
Generated By: OPT modules.
For Whom: End User.
Remedy: Re-export the random AMP samples from the target system or change the table’s definition on the test system
to match that of the target system.

6994 Invalid CAST. Casting a source value as %VSTR with lower precision is not allowed.
Explanation: A source value cannot be cast as PERIOD(TIME) or PERIOD(TIMESTAMP) with lower precision.
Generated By: Parser modules.
For Whom: End User.
Remedy: Correct the target precision and re-submit.

6995 Invalid CAST. Casting a Period value as %VSTR with lower precision is not allowed.
Explanation: A Period value cannot be cast as TIME or TIMESTAMP with lower precision.
Generated By: Parser modules.
For Whom: End User.
Remedy: Correct the target precision and re-submit.

6996 Invalid conversion or assignment operation on a Period.
Explanation: A value assigned/converted to/from a Period site must be a Period value of comparable element type or
must be a character string value must be in the form of target Period site format if defined or must be in default SDF format.
Generated By: Parser.
For Whom: End User.
Remedy: Rewrite the statement with proper source value and re-submit.

6998 Invalid Period arithmetic operation. Subtracting a Period operand from any other operand is
not allowed.
Explanation: A Period operand must not be subtracted from any other operand.
Generated By: Parser modules.
For Whom: End User.
Remedy: Correct the Period arithmetic expression and re-submit.

6999 Invalid operand for a Period operation. The operands must have comparable Period data
types.
Explanation: If there is a Period operand, the other operands must have Period data type and the operands must have
comparable Period data types.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the operands to be valid for the operation and re-submit.

7413 Current of cursor row no longer exists.
Explanation: The current of cursor row that the user is trying to modify no longer exists due to the fact that the row has
been changed by another request.
Generated By: StpRet, StpUpd, StpDel.
For Whom: End User.
Notes: Should only receive this error if in an updatable cursor txn and the FOR CHECKSUM locking modifier was specified
when the rows were selected.
Remedy: If still want to modify the specified row through a cursor, must commit or abort current updatable cursor txn,
start a new one, and re-submit statement.

7415 Probable stale message (WorkID mismatch)
Explanation: A DBS message failed to match the expected work ID, indicating that it is probably a so-called “stale” message improperly left over from another DBS step. Since a stale message means that DBS processing protocols may have
been compromised, this error causes a system restart.
Generated By: AMP software
For Whom: Site support representative.
Notes: This error is generated by the message sanity check routine AwtMatch, typically used to verify that the work ID in a received message matches the one in its known ancestor message. Since the system message header containing this work ID is normally copied into spawned, redistributed or response messages generated by a DBS step, the work ID in all these messages should match the one in the original step.
Remedy: 1) Save the crashdump for offloading. 2) Have all traceback information ready. 3) Then call your Support Representative.

7416 Collation has not been installed
Explanation: The user defined in the DBC.CollationTbl a collation whose name is not MULTINATIONAL and requested
it to be installed.
Generated By: SSSInXlt (DBS Startup)
For Whom: SysAdmin DBA Site support representative
Notes: This is a warning not an error. It warns the user that the collation he intended to install cannot be installed.
Remedy: Set the DBC.CollationTbl.CollInstall field to ’N’ for that collation.

7417 An invalid value was used as an argument to the HASHAMP function.
Explanation: An argument of the HASHAMP or HASHBAKAMP function doesn’t evaluate to the proper value. It
should evaluate to an integer value in the range [0, 65535].
Generated By: The interpretative expression processor.
For Whom: End user.
Remedy: Check the data against which the function was used.

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