Teradata SQL Error and Failure Codes from Error 2652 To 2661


2652 Operation not allowed: %DBID.%TVMID is being Loaded.
Explanation: This error occurs only when a user issues a request for a table that is being Fast/Multi Loaded.
Generated By: AMP Steps.
For Whom: End User.
Notes: The table does exist, but it is not in a form in which it may be accessed.
Remedy: Wait until the Fast/Multi Load is finished, then resubmit the request.

2653 Fast Load not allowed: table %TVMID has been rebuilt.
Explanation: While the table is being Fast Loaded, a disk error occurred causing the table to be rebuilt.
Generated By: AMP Software.
For Whom: End User.
Notes: Some data is lost, and cannot be recovered.
Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

2654 Operation not allowed: %DBID.%TVMID is being Restored.
Explanation: This error occurs when a user issues a request for a table that is being restored.
Generated By: AMP Steps.
For Whom: End User.
Notes: A table that is being restored may not be accessed for select or update.
Remedy: Wait until the restore operation is completed, then resubmit the request. If a restore is not in process, the operation
may have been aborted, and needs to be restarted or started over, or the table must be dropped.

2655 Invalid parcel sequences during Load
Explanation: This error occurs when the data parcel block sent from the host has an invalid parcel flavor, the flavor is
out of sequence, the length of a parcel is invalid or data was sent without Fast Load/MLoad initialization.
Generated By: StpLin/StpESD/LctStrtR
For Whom: Host Fast Load/MLoad Utility.
Notes: A problem occurred in the processing of a Fast Load/MLoad.
Remedy: Contact your Support Representative.

2656 %TVMID Load error: bad internal status – %VSTR
Explanation: This error occurs when an internal consistency check fails. This may have been caused by one Fast/Multi
Load job started immediately right after another Fast/Multi Load had just finished.
This error may also occur if the load entry is missing. The cause could be due to a network error or session abort.
Generated By: AMP Steps.
For Whom: Site support representative.
Notes: A problem occurred in the processing of a Fast/Multi Load.
Remedy: Try to resubmit the Fast/Multi Load request. If unsuccessful, contact your Support Representative

2657 FALLBACK cannot be added or removed when an AMP is down.
Explanation: This error occurs when a user tries to add or drop the FALLBACK option while an AMP is not available.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Wait until all AMPs are available and resubmit the request.

2658 Data type conversion is not supported in Fast Load.
Explanation: This error occurs when:
(a) a Fast Load operation attempts to store a character string as a numeric, or vice versa, or;
(b) an attempt is made to store one type of numeric data in another type of numeric (for example, INTEGER in DECIMAL).
Generated By: AMP Steps.
For Whom: End User.
Remedy: If it is necessary to convert data types, a host program must be written to do the conversion.

2659 The DBS restarted between FastLoad or MLoad requests.
Explanation: This error is returned when a restart occurs between requests during a FastLoad or MLoad operation.
Generated By: AMP FastLoad/MLoad processing.
For Whom: The FastLoad/MLoad Utilities.
Notes: This error code is designed to be intercepted by a host utility and should never be seen by the end user.
Remedy: None required. The load utility should recover and continue the load.

2660 Illegal INSERT detected after the END LOADING was started.
Explanation: This error occurs during Fast Load if the INSERT statement is retransmitted after END LOADING has
been started.
Generated By: AMP Fast Load Processing.
For Whom: End User.
Remedy: Remove the INSERT statement from the Fast Load request.

2661 Invalid numeric value or bad string length.
Explanation: This error occurs due to either of two conditions:
(1) An attempt was made to move a character or byte string data item into a character or byte field of shorter length (for
example, moving a 5-character data item into a 4-character field).
(2) The row under construction in EvlBuild is appending a numeric field that has a value not consistent with its
evlRepresent_t length definition (for example, integer64 has value of length 2).
Generated By: The interpretative instruction processor.
For Whom: End User for case 1. Site support representative.for either case.
Notes: This is used for development debugging purposes and should never occur in the field.
Remedy: For case 1, the problem can be circumvented by changing the request to use strings of equal length. In either
case, this is an internal error. Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 2652 To 2661 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.

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 *