Teradata SQL Error and Failure Codes from Error 3764 To 3775

SQLServerF1_Header_Small

3764 Use MODIFY DATABASE or MODIFY USER to drop the journal table.
Explanation: The DROP JOURNAL TABLE option drops the journal table and must be used by MODIFY DATABASE or
MODIFY USER.
Generated By: SYN modules.
For Whom: End User.
Remedy: Use MODIFY DATABASE/USER to drop the journal table.

3765 Conflicting or duplicate JOURNAL options.
Explanation: The request contained two conflicting or duplicate JOURNAL options.
Generated By: SYN modules.
For Whom: End User.
Remedy: Change these JOURNAL options and resubmit request.

3766 Replace WITH by DEFAULT for the JOURNAL TABLE option.
Explanation: The WITH JOURNAL TABLE option is used in the CREATE/ALTER TABLE statement.
Generated By: SYN modules.
For Whom: The end user.
Remedy: Correct the error and resubmit the request.

3767 Updatable cursor SELECT statement must follow FOR CHECKSUM locking modifier.
Explanation: The FOR CHECKSUM locking modifier can only be used with an updatable cursor SELECT statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Resubmit locking modifier with an updatable cursor SELECT statement.

3768 The JOURNAL option is conflicting to the JOURNAL TABLE option.
Explanation: The NO [BEFORE/AFTER] JOURNAL option is conflicting to the DEFAULT/WITH JOURNAL TABLE
option.
Generated By: SYN modules.
For Whom: The end user.
Remedy: Either specify no journal table or no journaling.

3769 Checksum locking modifier must reference the same table as the SELECT statement that follows it.
Explanation: The checksum locking modifier must lock the same table as the one referenced by the SELECT statement
that is associated with it.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change locking modifier so that it references the same table as SELECT that follows it and re-submit the
request.

3770 DEFAULT JOURNAL TABLE = tname is required for JOURNAL option.
Explanation: The DEFAULT JOURNAL TABLE option is required when the JOURNAL option appears in the CREATE
DATABASE or CREATE USER.
Generated By: SYN modules.
For Whom: The end user.
Remedy: Either specify a journal table or no journaling.

3771 Illegal expression in WHEN clause of CASE expression.
Explanation: There are 3 auses of this error are: a) a boolean is specified in a WHEN clause for a simple CASE expression,
Example: SEL CASE t.x WHEN 1=1 THEN t.x ELSE t.y END FROM t; b) a simple expression is specified in a WHEN
clause for a conditional CASE expression, Example: SEL CASE WHEN 1+1 THEN t.x ELSE t.y FROM t; c) an embedded
SELECT is found in the WHEN clause
Generated By: GNCEVL.
For Whom: The end user.
Remedy: Correct and re-submit SQL query.

3772 You cannot DROP a journal that is the default for other databases.
Explanation: An attempt has been made, in MODIFY DATABASE, to drop the permanent journal table in that database,
but there is at least one other database that specifies the table as its default permanent journal. Journal tables may not be
dropped when they are currently listed as defaults in other databases, even if no table is actually using them.
Generated By: OPT modules.
For Whom: End User.
Remedy: Either turn default journaling off for the other database using this journal, or assign default journaling to some other journal. MODIFY DATABASE must be used to turn default journaling off or to change the default journal table
assignments.

3773 You cannot DROP a permanent journal table that is in use.
Explanation: An attempt has been made, in MODIFY DATABASE, to drop the permanent journal table in that database,
but there is at least one table, which may be in any database, that specifies the permanent journal. Journal tables may be dropped only when they are no longer in use.
Generated By: OPT modules.
For Whom: End User.
Remedy: Either turn journaling off for tables using the permanent journal, or drop the tables.

3774 Internal error: Requested option is not yet implemented.
Explanation: Internal Teradata SQL Parser error.
Generated By: SYN modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3775 Invalid hexadecimal constant.
Explanation: An invalid hexadecimal constant was present.
The Teradata DBS internal ASCII form is:DR39140-tn2-01->> [V] [Repertoire] ’hexadecimal digit(s)’XC[ ] [F] Where Repertoire could be _Latin1, _Unicode,
_Graphic, _KanjiSJIS, _Kanji1 or blank. <<-DR39140-tn2-01
The external EBCDIC form is:
X’hexadecimal digits’
Please see “Data Types and Literals” in the Teradata SQL Reference Manual for details.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

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