Teradata SQL Error and Failure Codes from Error 2147 to 2514

SQLServerF1

2147 Internal error detected while comparing two strings.
Explanation: During the comparison of two strings, an internal error was detected by the float subsystem.
Generated By: Float subsystem.
For Whom: Field Engineer.
Remedy: Contact your Support Representative.

2148 Internal error detected while copying a string.
Explanation: While making a copy of a string, an internal error was detected by the float subsystem.
Generated By: Float subsystem.
For Whom: Field Engineer.
Remedy: Contact your Support Representative.

2149 Internal error detected while comparing two strings.
Explanation: During the comparison of two strings, an internal error was detected by the float subsystem.
Generated By: Float subsystem.
For Whom: Field Engineer.
Remedy: Contact your Support Representative.

2504 Bad Parameter passed to file system.
Explanation: An invalid parameter was passed to a file system routine.
Generated By: JnlLogRd, RedDos, RedSvc, blkReplace, RowBPeek, RowUpdIns, RowReplace, RowRIDL, RowRLHas,
and TabRBlks
For Whom: Site support representative.
Notes: This error results when a sanity check of parameters passed to a file system routine indicates one or more invalid
parameters. This can be caused by internal software problems or data corruption.
Remedy: Contact your System Representative.

2507 Out of spool space on disk.
Explanation: Insufficient disk space was available on the AMP to allow an operation to complete. Context state is
CtxNull and access to the CI and DB is dropped.
Generated By: File System
For Whom: End User
Notes: This indicates that a request has exceeded the physical storage limits imposed by a given configuration without
exceeding the logical limits imposed by PERM or SPOOL space allocations for a given database.
Remedy: If out of SPOOL space, resubmit the request, preferably when there is less activity on the system. If out of
PERM space, reduce permanent space usage by archiving journals or user tables where possible.

2509 AMP internal error (see traceback)
Explanation: One of the AMP software’s many sanity checks has failed, indicating an internal inconsistency in data or
processing state. This error causes a system restart.
Generated By: AMP software.
For Whom: Site support representative.
Notes: One of many fatal error conditions detected by sanity checks in AMP software could have caused this error message.
Because this error is non-specific, it is necessary to qualify any 2509 error with the associated traceback.
Remedy: Save the crashdump for offloading. Have all traceback information ready. Then contact your Support Representative.

2511 Bad locator parameter.
Explanation: A bad locator is specified in a parameter.
Generated By: RowInser.
For Whom: Site support representative.
Notes: This error is strictly for file system internal checking. It may be retired after system integration to improve performance.
Remedy: Contact your System Representative.

2513 A%VSTR data row is too long.
Explanation: The length of the row specified by the caller is greater than SysMaxRow, the maximum length allowed for
any row in the database. The row could be either one specified directly by the user, or an intermediate results row required
for query processing.
Generated By: File System
For Whom: End User Field Engineer
Notes: This indicates that a row is too long. Query processing often requires intermediate results rows that are longer
than the data being selected. For example, ORDER BY and GROUP BY columns require sort keys that increase intermediate
results row size.
Remedy: Reduce the size of row required. Fewer or smaller columns, or less complex queries may solve the problem.
Otherwise, contact support personnel.

2514 Operation not allowed: %DBID.%FSTR is being used to log ARC selected partition restore errors.
Explanation: This error occurs when a user issues a request to access the error table that is actively being used to log errors during an ARC restore of selected partitions to a PPI base table. Only read or drop access is permitted.
Generated By: AMP Steps.
For Whom: End User.
Notes: The table does exist with limited access rights.
Remedy: Wait until the ARC restore is finished, then resubmit the request.

Above are list of Teradata Errors or Failure Codes from Error 2147 to 2514 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 *