Teradata SQL Error and Failure Codes from Error 2714 To 2723

2714 Resusage discarded some monitoring information because of insufficient resources %s
Explanation: ResUsage software was not able to keep up with its workload, as described in the message. This usually
happens because the system is too busy to handle the resusage log rate specified in the control GDO.
Generated By: SSSRSS — resource usage monitoring.
For Whom: System Administrator, System Support Representative.
Notes: This event is informational.
Remedy: Consider setting longer resusage collect and log intervals or disabling one or more ResUsage tables. If this is
infeasible or the explanation does not seem to fit your case, contact your Support Representative.

2715 Convert Time function failed %s
Explanation: Converttime function failed for the given secs value and ResUsage table.
Generated By: resd daemon.
For Whom: System Support Representative
Notes: This indicates the corruption of rss data buffers.
Remedy: Contact the Support Representative.

2716 Convert Date function failed %s
Explanation: Convertdate function failed for the given secs value and ResUsage table.
Generated By: resd daemon.
For Whom: System Support Representative
Notes: This indicates the corruption of rss data buffers.
Remedy: Contact the Support Representative

2717 Segget failure occured in sssrss %s
Explanation: segget function failed for bundling the resusage rows into the segment due to lack of segments.
Generated By: resd/restpad daemon.
For Whom: System Support Representative
Notes: This indicates that resusage data will not be logged or some of the rows will be missed. There will be no impact
other than this on the system – although other areas may be affected by lack of segments.
Remedy: Contact the Support Representative

2718 FASTLOAD CHECKPOINT must be within the Data Loading transaction.
Explanation: The CHECKPOINT LOADING statement and the FASTLOAD INSERT statement must be in the same
transaction.
Generated By: AMP FASTLOAD Processing.
For Whom: Host FASTLOAD Utility.
Remedy: Put the CHECKPOINT statement within the same transaction as the INSERT statement.

2719 FASTLOAD END LOADING cannot be inside the Data Loading phase.
Explanation: The END LOADING statement cannot be inside the same transaction as the INSERT statement.
Generated By: AMP Fastload Processing.
For Whom: Host Fastload Utility.
Remedy: Put the END LOADING statement outside the transaction which contains the INSERT statement.

2720 Fast/MLoad or FastExport has already been terminated.
Explanation: If this was a FastLoad or MLoad job then the load operation on the DBS side has already been terminated,
but data parcels are still being sent down from the host. Possible cause is the Host Load Utility is ignoring the error
returned from DBS.
If this was a FastExport job then the FastExport session has been logged off. The SQL Select is either aborted or if it has been
completed then the logoff results the answer set inaccessible. In the latter case, the host must submit an End Request to delete any spool files created on the AMPs.
Generated By: AMP Load Processing.
For Whom: Host Load Utility.
Notes: The Utility should terminate if there is any error returned while it is sending data parcels to the DBS.
Remedy: Cancel the Load job on the Host. Correct the Utility if it is ignoring errors.

2721 Fast Load Utility fails to recognize error in previous request.
Explanation: DBS has decided to abort this Fast Load due to some error conditions caused by the previous request during
the data loading phase, but the Host Fast Load Utility fails to acknowledge the error returned and continues to send
data parcels to the DBS.
Generated By: AMP Fast Load Processing.
For Whom: Host Fast Load Utility.
Remedy: Correct the Host Fast Load Utility.

2722 Too many in-doubt 2PC transactions.
Explanation: There are more in-doubt 2PC transactions than can be accommodated.
Generated By: AMP
For Whom: End User.
Notes: This error means that an AMP has as many in-doubt 2PC transactions as it can accommodate.
Remedy: Resolve the in-doubt 2PC transactions and resubmit the request.

2723 Too many Locks used by 2PC transactions.
Explanation: During a COLDWAIT restart, the number of locks for in-doubt 2PC transactions to be placed on a catch-up
AMP to bring it on-line exceeded the lock manager lock resources.
Generated By: AMP
For Whom: Operator. DBA.
Notes: This error causes a COLD restart of the DBC to bring the system back up, but the catch-up AMP will not be on
line.
Remedy: Resolve the in-doubt 2PC transactions, then COLDWAIT restart the DBC if the AMP must be brought on-line
immediately.

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