Teradata SQL Error and Failure Codes from Error 3862 To 3874

SQLServerF1_Header_Small

3862 The tables in BEGIN LOADING statement must be different.
Explanation: The user specified the same table names for error files or the table to be loaded in BEGIN LOADING statement.
Table names must be different for each BEGIN LOADING statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement to specify different table names and resubmit the request.

3863 Duplicate definition of ’%VSTR’ in NAMED phrase.
Explanation: The name given in NAMED phrase was not unique. It was already used in another NAMED phrase.
In a macro, parameter names are resolved to named phrases. Other names in a statement may be implicitly resolved to
named phrases as well. Macro parameter names should differ from other names to avoid conflict.
Generated By: RES modules.
For Whom: End User.
Remedy: Check the names in NAMED phrase; change any duplicate ones and resubmit the request.

3864 A secondary index cannot be created on table DBC.’%VSTR’ .
Explanation: A secondary index cannot be created on DBC internal tables ErrLog, EventLog, Global, and Session.
Generated By: RES modules.
For Whom: DBA User.
Remedy: None.

3865 The privilege is not applicable to a view.
Explanation: The applicable grant privileges are DROP VIEW, DELETE, INSERT, SELECT, UPDATE, and GRANT for a
table/view object.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3866 The privilege is not applicable to a macro.
Explanation: The applicable grant privileges are DROP MACRO, EXECUTE, and GRANT for a macro object.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3868 A table or view without alias appears more than once in FROM clause.
Explanation: The same table or view appears more than once without NAMED phrase in the FROM clause of a SELECT
statement. This causes ambiguity; the Teradata parser cannot resolve an unqualified column in select list since it can be
found in more than one table/view in the FROM clause.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3869 A system journal table cannot be accessed via Teradata SQL.
Explanation: There are 10 system journal tables:
DBC.TransientJournal ChangedRowJournal LocalTransactionStatusTable UtilityLockJournalTable LocalSessionStatusTable
SysRcvStatJournal SavedTransactionStatusTable OrdSysChngTable RecoveryLockTable RecoveryPJTable
and 1 DBC table:
DBC.ALL
These system journal tables and DBC.ALL are different from regular tables and they are for internal processing only. They
cannot be accessed via Teradata SQL.
Generated By: RES modules.
For Whom: The DBA and System Support Representative.
Remedy: None.

3870 Alias name cannot match another table/alias name in FROM clause.
Explanation: An alias name is found to match another table name or alias name specified in the same FROM clause of
SELECT statement. This causes ambiguity because Teradata Parser cannot tell the user’s intention. Two such illegal queries
are:
SELECT * FROM T1, T2 T1; SELECT * FROM T1 T2, T2 T3;
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3872 Illegal use of an aggregate operation in an UPDATE statement.
Explanation: An UPDATE statement includes an aggregate function such as SUM, MIN, etc. in the assignment list.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the request and resubmit the request.

3873 ’%VSTR’ is not a Journal table.
Explanation: The specified item is a view, macro, or table and the context of the query returning the error requires the item to be a journal table.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3874 No journaling options have been specified.
Explanation: To use a journal table we need to know what type of journaling to do. The options are:
BEFORE, AFTER, DUAL BEFORE, DUAL AFTER.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit.

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