Teradata SQL Error and Failure Codes from Error 3673 To 3681


3673 Statement not permitted during MLoad.
HELP, INSERT, Null stmts, RELEASE MLOAD and UPDATE are permitted during MLoad.
Generated By: OPT modules.
For Whom: Host Utility MLoad.
Remedy: Correct the statement and resubmit the request.

3674 Bad internal value of the collation.
Explanation: This error occurs when a variable which is supposed to hold a valid collation, doesn’t represent any of the
valid collation values.
Generated By: OPT and GEN modules.
For Whom: System Support Representative.
Notes: This is not a user error.
Remedy: Save all relevant information and the dump, and contact your support representative.

3675 Bad internal value of repr format field.
Explanation: This error occurs when the format field of a repr doesn’t represent a valid value. This may happen when
format was taken from SysMsgHdr.HostCharSet and the HostCharSet had an invalid value. In may cases this error is
related to wrong codes of National Character Sets.
Generated By: OPT and GEN modules.
For Whom: System Support Representative.
Notes: This is not a user error.
Remedy: Save all relevant information and the dump, and contact your support representative.

3676 Default Journal for database ’%VSTR’ does not exist.
Explanation: This error occurs if the resolver finds a database with default journaling which does not have a corresponding
TVM row for the journal table. This situation most likely arises if the database has been restored but not the corresponding
permanent journal table and the user attempts an operation on the journal (e.g. CHECKPOINT).
Generated By: RESNAME2.
For Whom: System Engineer or Database Administrator.
Notes: None.
Remedy: The data dictionary is out-of-synch. You cannot re-submit the request until the referential integrity problem is
resolved. Restore the permanent journal table referenced by the indicated database. If this doesn’t resolve the problem,
something more severe must have happened, so notify your support representative.

3677 %VSTR referenced by %FSTR does not have implied GRANT access to %DBID.%TVMID. User %S does not have implied GRANT access to the referenced table.
Explanation: The user does not have an implied GRANT access rights to execute this request, or the owner of the
requested view or macro does not have the GRANT access right to underlying tables.
This is an interim message for Release 4.1, and the code value is used to log the fact that the access needed was not present,
but to allow the query to execute, using old rules where the GRANT access was unchecked. Starting with Release 4.2, this
message should be obsolete.
Generated By: SQL modules.
For Whom: End User, Database Administrator.
Remedy: Obtain the necessary access rights.

3679 Transaction ABORTed due to resource shortage.
Explanation: A transaction was aborted which required dictionary information that it was unable to receive due to being
blocked by other locks. All available AMP tasks were busy or were also waiting for locks. Accepting this request would
have created a possibility of an unbreakable resource deadlock. The limit of retries for this condition was exhausted and the
transaction was aborted. The application program was informed with a 2631 error that it’s transaction was aborted and that
it must resubmit the request.
This entry and it’s associated information has been placed into the ErrorLog to aid in understanding the ErrAMPLokDead-
Lock (2631) which was reported to the application.
The probable cause of this condition is a long running DDL operation being performed while many other requests are also
being presented to the database.
Generated By: MgcExpRq
For Whom: Database Administrator.
Remedy: No action is required for this error.
If this condition is recurrent, review the use of DDL during the time the events occur.
If adjustments to the use of DDL during these periods cannot resolve the problem, notify your support representative.

3680 Too many collected statistics items for this COLLECT command.
Explanation: Because the optimizer uses spool files for generating statistics, when collecting statistics on a table that has
too many columns/indexes with statistics collected previously, the total number of spool files needed will exceed its limit.
The limit of columns/indexes has been set at 40 according to the limit of spool files.
Generated By: OPT modules.
For Whom: End User.
Remedy: Instead of using “COLLECT STATISTICS on <table>”, collect statistics on each item individually.

3681 Table %DBID.%TVMID with column %VSTR cannot be used as a target.
Explanation: A table that contains one or more of the following column names: ApplySeq, DBCErrorCode, DBCError-
Field, DMLSeq, ImportSeq, SMTSeq, SourceSeq or Uniqueness cannot be used as a Multiload target table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change the table definition.

Above are list of Teradata Errors or Failure Codes from Error 3673 To 3681 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.

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 *