Teradata SQL Error and Failure Codes from Error 2895 To 2904

SQLServerF1_Header_Small

2895 The current cursor row has already been deleted.
Explanation: The user has deleted the current cursor row and is trying to update/delete the same row again.
Generated By: SutSpCsr.
For Whom: User.
Remedy: None.

2897 Table header row for %DBID.%TVMID is too long.
Explanation: The table being created or altered causes the table header row to exceed 64K row size limit.
This can happen if the table has defined with 2048 columns and secondary indexes each consists of 64 columns and referential
constraints each consists of 64 columns Foreign Key or table has more compress columns.
If we get this error during the migration process, which indicates that the Table header row size is exceeding the 64K limit
on target platform. This can happen while migrating the data from 32-bit platform to 64-bit platform.
Generated By: StpCIX, StpMTB, StpCRI.
For Whom: End User.
Remedy: Contact your Support Representative.

2898 Fallback reference index row is in the wrong subtable.
Explanation: Incorrectly distributed reference index rows are detected as the reference index subtables are traversed.
The row is discarded from the remainder of the checking process.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2899 Reference index row contains non existent Foreign Key value.
Explanation: The Foreign Key value contained in the reference index row was not found in the corresponding primary
data subtable.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2900 An informative event was logged.
Explanation: The specific information is encoded within the event message (for example, “Configuration is operational”).
Generated By: DBS Startup.
For Whom: Operator.
Remedy: This message is for information only.

2901 Cannot install CharSet: Invalid ID
Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error
means that an attempt was made to install a CharSet with an invalid ID value.
Generated By: SSSMain (System startup)
For Whom: DBA Site support representative
Notes: When this error occurs during normal system startup, the error message logged on the console will identify both
the name of the CharSet and the offending ID.
Remedy: Update DBC.Translation to use only valid ID’s. A valid ID is between EvlUserMinChar and EvlUserMaxChar,
or between decimal values 65 and 126.

2902 Cannot install CharSet: Non-unique ID
Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error
means that an attempt was made to install two or more CharSets with the same ID value.
Generated By: SSSMain (System startup)
For Whom: DBA Site support representative
Notes: When this error occurs during normal system startup, the error message logged on the console will identify both
the name of the CharSet and the offending ID.
Remedy: Update DBC.Translation so all installed ID’s are unique.

2903 Cannot install CharSet: Exceeded max
Explanation: The CharSet is one of the special character sets defined in the system table DBC.Translation. This error
means that an attempt was made to install more CharSets than the maximum number allowed by the system.
Generated By: SSSMain (System startup)
For Whom: DBA Site support representative
Notes: When this error occurs during normal system startup, the error message logged on the console will identify both
the name of the CharSet and the maximum number.
Remedy: Update DBC.Translation so that the number of installed CharSets does not exceed the maximum given by constant
SysMaxUserTranslations (initially 6).

2904 NVRAM is disabled in the system.
Explanation: NVRAM is equipped but disabled on all AMPs in the configuration.
Generated By: SSSMain or SSSSPF.
For Whom: DBA Site support representative.
Notes: This is a warning more than an error. It should not cause a crash, but should be reported to a user.
Remedy: Enable NVRAM on all AMPs.

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