Teradata SQL Error and Failure Codes from Error 2884 To 2894

SQLServerF1_Header_Small

2884 Primary reference index row is missing.
Explanation: The reference index subtable is fallback. However, there is a fallback reference index row which has no corresponding
primary reference index row.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2885 Reference index row hash code is incorrect.
Explanation: A primary (or fallback if an AMP is down) reference index row has incorrect hash code. The hash code is
not corrected in the remainder of the checking process.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2886 Reference index row has duplicate Foreign Key values.
Explanation: A primary (or fallback if am AMP is down) reference index row has the same Foreign Key value as another
row in the same hash code. The row is not ignored in the remainder of the checking process.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2887 Primary and fallback reference index rows do not match.
Explanation: A mismatch is detected when the primary copy of a reference index row is compared to its fallback copy
byte by byte.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2888 Invalid reference index row.
Explanation: The Foreign Key contained in the reference index row was not found in the referenced table (i.e. this particular
Foreign Key value should have caused referential constraint violation).
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2889 Table header has incorrect parent count or child count.
Explanation: The parent(child) count in the table header does not agree with the number of reference index descriptors
in the table header with ChildEntry field sets to false(true)).
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2890 Dictionary child count does not match header child count.
Explanation: This message is displayed if the child count field in the table header does not match the corresponding
child count in the DBC.TVM record for the table.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2891 %VSTR not found for %DBID.%TVMID.
Explanation: The Work Table or Error Table was likely dropped by a concurrently running job that was using an identically
named table.
Generated By: Amp Software.
For Whom: User.
Note: Like ErrAMPWTETMissing, the accompanying error message will indicate the MLOAD resource table that has been
dropped. Unlike ErrAMPWTETMissing however, there is no restart involved, and it is not generated by STPEBE.
Remedy: To avoid this error, ensure that all MLOAD resource table names are unique across jobs that may be run concurrently.
To recover from this error, drop the remaining MLOAD resource tables, perform the required Target Table recovery, then resubmit
the job.

2892 Null value eliminated in set function
Explanation: The user tried TO perform set FUNCTION on a column which has one OR more null values.
Generated By: AGR modules.
For Whom: END User.
Remedy: None.

2893 Right truncation of string data.
Explanation: The user tried to assign a longer to a shorter string destination.
Generated By: EVLUTIL
For Whom: END User.
Remedy: None.

2894 The cursor spool row specified is invalid.
Explanation: The spool row identifier sent by the application in the cursor parcel is invalid.
Generated By: AMP Steps.
For Whom: User.
Remedy: Resubmit the updatable cursor update or updatable cursor delete with the correct spool row identifier.

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