Teradata SQL Error and Failure Codes from Error 3977 To 3987

SQLServerF1_Header_Small

3977 The Parent Key is not unique or not valid.
Explanation: The referenced column(s) (Parent Key) specified in the referential constraint must either be a valid unique
primary index (UPI) or a valid unique secondary index (USI) of the referenced table. Note that an UPI/USI could exist but
in an invalid state and in which case this error will also be returned.
Generated By: RES/OPT modules.
For Whom: End User.
Remedy: Use the Create Unique Index statement to define the referenced column(s) as unique in the referenced table.

3978 Invalid CHECK condition.
Explanation: Entry-level ANSI does not allow check condition to include subqueries, parameter references, or set functions.
Also, table check condition must not include columns from other tables, and column check condition must not
include columns other than the one being defined.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3979 Check already exists.
Explanation: This error could have resulted from one of the following two cases: (1) The check with the same name
already exists. (2) For an unnamed table check, if the contents of two checks are identical (i.e. exact wording and case) then
this error will be returned. e.g. ’check (f1 > 0)’ and ’check (f1>0)’ are duplicate, however, ’check (f1 > 0)’ and ’check (F1 > 0)’
are not duplicate.
Generated By: OPD modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3980 Cannot drop the column when table check(s) exists that reference it.
Explanation: The column can only be dropped when all the table check(s) referencing it are dropped.
Generated By: OPD modules.
For Whom: End User.
Remedy: Drop the table check(s) and resubmit the request.

3981 The table has too many table checks.
Explanation: Either the table has more than 255 named table checks or there is more than 255 table checks referencing a
column.
Generated By: OPD modules.
For Whom: End User.
Remedy: Delete some check(s) and resubmit the request.

3982 No other table options can be specified when a constraint is specified in the statement.
Explanation: If a constraint is added/dropped/modified via an Alter Table statement then no other table options (e.g.
protection, journal option, add/drop column(s), changing column attribute, etc.) can be specified in the same statement.
Generated By: SYN Modules
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3983 A constraint violation was found caused by the new check.
Explanation: The new check caused a constraint violation on the existing rows.
Generated By: OPD
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3984 Internal error: Check count is zero.
Explanation: Check count is unexpectedly zero.
Generated By: OPD
For Whom: End User.
Remedy: Correct the error and resubmit the statement.

3985 COMMIT must be the last statement in a request
Explanation: The COMMIT WORK statement must be the last statement when more than one statement is in the
request.
Generated By: OPT modules
For Whom: End User.
Remedy: Reorder the statements in the request so that any COMMIT statement occurs last.

3986 The forward referenced table must be created by the same user who created the referencing table.
Explanation: The table being created is already referenced by another table (i.e. forward referencing), which was created
by another user. (Currently, the forward referenced table and its referencing table(s) must be created by the same user.)
Generated By: OPT modules.
For Whom: End User.
Remedy: Change the table name and resubmit the request.

3987 The object name has been reserved as a referenced table.
Explanation: 1) The name of the object being created has been used as a referenced table name for some unresolved referential
constraints. That name cannot be used as the name of another object in the same database. 2) The name of the forward
referenced table has been reserved by another user. That name cannot be used by another user until that table is
created.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change the object name and resubmit the request.

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