Teradata SQL Error and Failure Codes from Error 2936 To 2948


2936 No row was found for Bulk Load delete/update.
Explanation: A Bulk Load request to update or delete a row found no row with the specified prime key.
Generated By: StpDel or StpUpd.
For Whom: End User.
Remedy: None.

2937 A control AMP has not been selected.
Explanation: A control AMP has not been selected by the root booter after a timeout period by the software.
Generated By: BootCFG or SSSSPF.
For Whom: End User.
Notes: For some reason, no AMP is selecting itself as the control AMP for startup. The most likely reasons are:
(a) all processors have a single Ynet, and the “One Ynet OK” flag must be set in the version record for an AMP to select
(b) the configuration maps are not correct, in that they define all processors as new or as down during the last execution,
(c) some processor has a configuration map that has a much higher version number than the others, and this processor is
not selectable as the control AMP.
Remedy: None.

2938 Request was aborted by the user.
Explanation: The prime key request was aborted asynchronously by the user.
Generated By: StpPKA and AwtAEGet.
For Whom: End User.
Remedy: No action required.

2939 Maximum number of worker tasks exceeded.
Explanation: The number of AMP worker tasks requested by TOS flow control, as specified by FlwTypes TOSTypes,
exceeds the number specified by the constant AwtMaxWrkTsts in AwtTypes AMPTypes.
Generated By: ActMain.
For Whom: Site support representative.
Remedy: Update the source files so that the number of tasks requested by flow control is fewer than or equal to the number
specified for the AMP.

2940 Invalid option on a case statement.
Explanation: A value has been received for a case statement that is not a legal value.
Generated By: AwtTipUp.
For Whom: Site support representative.
Notes: This is caused by a bad argument to the AwtTipUp procedure.
Remedy: Contact your Support Representative.

2941 There is an AMP down prior to a table rebuild.
Explanation: An irrecoverable I/O error has occurred on a user data table. Because an AMP in the cluster is unavailable,
the table cannot be rebuilt to recover the lost data.
Generated By: RBKMain, RBKRcvy.
For Whom: End User.
Remedy: Run table rebuild after the AMP has been brought back on-line.

2942 Table does not have the fallback option.
Explanation: An irrecoverable I/O error has occurred on a user data table. Because the table does not have fallback, the
data cannot be recovered.
Generated By: RBKMain, RBKRcvy.
For Whom: End User.
Remedy: The table can be recovered by restoring if the dump of the table exists, or by re-entering the data.

2943 The lock blockers segment is full.
Explanation: This is an internal warning message that is issued from one of the Lock Manager routine that was implemented
for the PM&PC and the LokDisp routine. This error means that the lock blocker segment that was built contains
only partial blocked and blocking information.
Generated By: LokQBlks routine.
For Whom: Internal User.
Remedy: Nothing the user can do.

2947 Invalid control AMP selected.
Explanation: The AMP selected as control AMP does not qualify as the control processor because:
(a) it was not on-line during the preceding system execution,
(b) it does not have the same version of software as most of the processors, or
(c) the configuration map on the processor has a lower version number than some other processor.
These conditions can only be detected after a processor has selected itself as the control processor and received messages
from all other processors. The processor sets a flag not to vie for control status and resets the system.
Generated By: BootCfg.
For Whom: End User.
Remedy: The software will correct itself.

2948 Index used for retrieval is not unique.
Explanation: The secondary index defined for retrieval is not a unique index.
Generated By: ExpRSI.
For Whom: Site support representative.
Notes: This is an internal error. The calling routine has specified an invalid index.
Remedy: Contact your Support Representative.

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