Teradata SQL Error and Failure Codes from Error 3752 To 3763

SQLServerF1_Header_Small

3752 Too many digits in exponent.
Explanation: Four or more digits were used in the exponent for a floating constant. Only 3 are allowed.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3753 Too many digits in integer or decimal constant.
Explanation: Too many digits were used. The maximum number of digits for an integer is 10. If an integer greater than
the maximum representable value is specified, the parser attempts to represent the constant as a Decimal, with no fractional
digits. If the number of digits exceeds the maximum specified for decimal total digits (currently 18), this error is reported.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3754 Precision error in FLOAT type constant or during implicit conversions.
Explanation: Accuracy was lost while converting a number or when doing implicit conversions. Real numbers are representable
to 15 digits of precision in the database. If more digits are used an error is reported.
Generated By: LEX/OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3755 Numeric overflow error.
Explanation: Overflow occurred while converting a number.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3756 Numeric divided-by-zero error.
Explanation: Division by zero occurred while converting a number.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3757 Numeric stack overflow error.
Explanation: Stack overflow occurred while converting a number.
Generated By: LEX modules.
For Whom: System Support Representative.
Remedy: Save information and notify your support representative.

3758 Numeric stack underflow error.
Explanation: Stack underflow occurred while converting a number.
Generated By: LEX modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3759 Numeric illegal character error.
Explanation: Conversion error.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3760 String not terminated before end of text.
Explanation: A closing quote is missing on a string.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3761 Nothing to be modified in ALTER TABLE.
Explanation: There is no modification in the submitted ALTER TABLE statement. For an ALTER TABLE statement with
a MODIFY PRIMARY INDEX clause, at least one of the options must be specified that alters the table’s primary index from
its existing definition. For example, only specifying the primary index be UNIQUE when it is already unique is not
allowed. Note that specifying a new partitioning expression even if it is syntactically the same or would compute the same
mapping is considered to be altering the primary index’s definition.
Generated By: SYN and RES modules.
For Whom: The end user.
Remedy: Specify modification(s) and re-submit.

3762 Lock object must be TABLE in FOR CHECKSUM locking modifier.
Explanation: The FOR CHECKSUM locking modifier can only be used to lock a table.
Generated By: RES modules.
For Whom: End User.
Remedy: Change lock object to TABLE and resubmit request.

3763 Conflicting NAMEs for this column.
Explanation: The CREATE TABLE has a NAMED phrase.
Generated By: SYN modules.
For Whom: End User.
Remedy: Remove NAMED phrase and resubmit the request.

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