Teradata SQL Error and Failure Codes from Error 3988 To 3998

3988 The non-existent referenced table must be in the same database as the referencing table.
Explanation: The non-existent referenced table which is forward referenced by the table being created must be in the
same database as the referencing table.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the request and resubmit it.

3989 The request resulted in a cursor conflict.
Explanation: This is only a warning to let the user know that a cursor conflict exists involving the table referenced by the
request. Cursor conflict occurs when one of the following situations happens within a transaction:
1) The request is a searched update or delete on a table that has already been modified through a cursor that is still open.
2) The request is an update or delete made through a cursor on a table that has been modified by another opened cursor
while the first cursor was still open.
3) The request is an update or delete made through a cursor on a table that has already been modified by a searched update
or delete while the cursor was still open.
Note: The request is still processed despite the warning.
Generated By: Gnc modules.
For Whom: End User.
Remedy: None.

3990 Table %VSTR is not specified in the FROM clause or already aliased by another name.
Explanation: Some newly referenced table was not defined in the FROM clause of a SELECT subquery, or was already
aliased by another name. ‘tablename’ specifies first table name that was found missing. There might be more than one missing
table name.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

3991 A FROM clause is missing for a SELECT subquery or view used in join.
Explanation: A FROM clause is missing for a SELECT subquery or view used in join.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

3992 Object table name is not specified for a DELETE statement.
Explanation: When joined tables are specified in the FROM clause of a DELETE, the deleted table name has to be specified
after the DELETE key word.
Generated By: SYN modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

3993 Illegal usage of alias name.
Explanation: For an UPDATE, if a FROM clause is specified for an update, the table name after the keyword UPDATE
could not be followed by an alias name.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

3994 Alias name defined should be used instead of table name %VSTR.
Explanation: A table to be updated or deleted has an alias defined in the FROM clause but the original tablename
instead of the alias was used right after the UPDATE or DELETE keyword.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the syntax and resubmit the request.

3995 Maximum number of subquery nesting levels has been exceeded.
Explanation: A subquery’s nesting level has exceeded the maximum number of nesting levels allowed. This maximum
is defined as CONST ResMaxNestedLevel.
Generated By: RES modules.
For Whom: End User.
Remedy: Rephrase the query with fewer nesting levels and resubmit the request.

3996 Right truncation of string data.
Explanation: The user tried to assign a longer to a shorter string destination. This error can also occur if the length of one
or more range boundaries in a RANGE_N function is a string literal with a length greater than that of the test value.
Generated By: OPUCONEQ, OPT
For Whom: End User.
Remedy: If the error is related to the RANGE_N function, examine the data type of the test value and range boundaries
to determine if range boundaries shorter that the test value may be used. If so, re-write the function expression.

3997 The ESCAPE value for LIKE must be One Character.
Explanation: The user has specified a character string value for the ESCAPE character in a LIKE comparison which has a
length other than one.
Generated By: OptCType module.
For Whom: End User
Remedy: Change the query to use a character string of length one.

3998 The Pattern String for LIKE has an invalid ESCAPE Sequence.
Explanation: The user has specified an ESCAPE character for a LIKE string comparison, and the Pattern string used
includes an instance of the escape character that is not immediately followed by ’_’, ’%’, or the escape character.
Generated By: Opt and Evl modules
For Whom: End User
Remedy: Change the statement to use a Pattern string without the invalid sequence.

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