Teradata SQL Error and Failure Codes from Error 3965 To 3976

SQLServerF1_Header_Small

3965 The GRAPHIC string literal is not supported for the current character set.
Explanation: The GRAPHIC string literal (G’<–>’, or N’<–>’) is only supported in a Kanji IBM platform.
Generated By: Lexer
For Whom: End User.
Remedy: If the current character set is other than one of the IBM Kanji character sets, the hexadecimal graphic form
should be used (e.g., ‘****’XG) instead of a GRAPHIC string literal.

3966 Index of GRAPHIC data with numeric or date is illegal.
Explanation: The user tried to obtain the index of a GRAPHIC data type with numeric or date data.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3968 Cannot drop an unique secondary index which is also a Parent Key.
Explanation: The user tried to drop an unique secondary index which is also defined as a Parent Key. Note that by definition,
the Parent Key (i.e. referenced column(s)) must be defined with unique constraint.
Generated By: OPT modules.
For Whom: End User.
Remedy: The user must drop the referential constraint which has the target secondary index as the Parent Key, and then
resubmit the request.

3969 Referential integrity violation: data rows being deleted are referenced by some Foreign Key values.
Explanation: The data rows in a referenced table cannot be deleted because there are some Foreign Key values that reference it.
Generated By: OPT modules.
For Whom: End User.
Remedy: The user must delete the Foreign Key values that reference the target data rows, and then resubmit the request.

3970 Load table %TVMID cannot be a referenced table or contain any referential constraint(s).
Explanation: BEGIN LOADING is not possible on a table which contains referential constraints or is referenced by some
other table(s).
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraints or the referencing table, and resubmit the FastLoad job.

3971 MLoad target table cannot be a referenced table or contain any referential constraint(s).
Explanation: It is not possible to BEGIN MLOAD on a table which contains referential constraints or is referenced by
some other table(s).
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop referential constraints, and resubmit MLoad job.

3972 This forward referenced table being created conflicts with the constraints defined by table %DBID.%TVMID.
Explanation: The table being created is forward referenced by another table, and its definition is incompatible with the
referencing table due to one of the following reasons: (1) the referenced column is not defined. (2) the referenced column
type is incompatible with the referencing column. (3) the parent key is not defined as an unique primary or unique secondary
index. (4) the parent key was default to a primary key and the parent table does not have one defined.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the request and resubmit it.

3973 Cannot specify multiple constraints in an Alter Table statement.
Explanation: Alter Table does not allow altering more than one constraints (e.g reference, check, primary key, unique) in
a statement.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3974 This table has too many referential constraints.
Explanation: The maximum number of referential contraints a user can define on a single table is 64. The same table can
be referenced by 64 tables. If the referential constraints exceed either of these limits, then this error is returned.
Generated By: RES/OPT modules.
For Whom: End User.
Remedy: Reduce the number of referential constraints and resubmit the request.

3975 Table ’%VSTR’ is an illegal referential constraint target.
Explanation: The user cannot define a referential constraint on a DBC table and a referential constraint defined on a user
table cannot reference a DBC table.
Generated By: RES modules.
For Whom: End User.
Remedy: None.

3976 Incorrect referential constraint definition.
Explanation: The table being created or altered *DR94963-bessc-01* has an incorrect referential constraint definition.
This could have resulted from violating any of the following rules for defining a referential constraint:
(1) The Foreign Key column must have the same column definition as its corresponding Parent Key column. The only
exception is that a Foreign Key column can be defined as Nullable in order to enable circular references. (2) The Foreign
Key must consist of the same number of columns as the Parent Key. (3) A Foreign/Parent Key column must not be compressible
DR112755-paikya-01 unless it is part of a Batch RI or Soft RI (4) If a table has multiple forward references to a Parent
table, referential constraint definition consistency (i.e. item (1), (2), and (3)) must be maintained among those forward
references.
Generated By: RES/OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

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