Teradata SQL Error and Failure Codes from Error 3914 To 3923

SQLServerF1_Header_Small

3914 ABORT request transaction ids do not match.
Explanation: The transaction number of the request, which the Parser is to abort, does not match the transaction number
in the session’s context.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3915 Invalid source for received message.
Explanation: This error code states that a message received originated from an invalid location. The Parser expects most
of its messages to be generated internally. If a message is received from the host or from the console system, the message
must be incorrect.
Generated By: CON, PAR, DIC, MGC and SStTsk modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3916 Requested information not in dictionary.
Explanation: This error code states that a request for dictionary information could not be found. The Parser converts this
error code into a user error. For example, if an attempt is made to delete a nonexistent table, this error will be returned to
the Parser.
Generated By: MGC, RES, GEN and OPT modules.
For Whom: Internal.
Remedy: The Parser converts this into an error code to tell the user how to correct the Teradata SQL statement.

3917 The request is aborted by an ABORT SESSION command.
Explanation: This error is returned to the user because the Parser has received an ABORT SESSION request from the
Monitor Task.
Generated By: ConLogOf, ConClean, ConTsk.
For Whom: System Support Representative.
Remedy: Contact System Operation to determine why the ABORT SESSION was directed against your session.

3918 Internal error: Dictionary cache is inconsistent.
Explanation: No items were available for removal when an item was to be added to the cache. When the cache is full and
an item must be added, data is removed from the cache one at a time until there is enough room for the item to be added. If
after removal, there is still no room in the cache, a logic error must be present.
Generated By: MGC and DIC modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

3919 Table has too many columns.
Explanation: A user table or an internal table (spool file) has too many fields. User defined tables and macros are limited
to 2048 columns. Spool files may have more, for sort keys, etc., but are limited to 2560.
Generated By: RES and OPT modules.
For Whom: User.
Remedy: Tables and views cannot be created or modified to have more than 2048 columns. Response rows and rows of
spool tables used in joins are also restricted.

3920 Table needs EXECUTE MLoad.
Explanation: Tables have been defined by BEGIN MLOAD but have were not declared in the EXECUTE MLOAD
request. It is necessary to do an EXECUTE MLOAD for each table that was defined.
Generated By: OPT modules.
For Whom: User.
Remedy: Resubmit the EXECUTE MLOADs including all tables.

3921 Invalid parcel length.
Explanation: The user sent a parcel that had invalid parcel length specified. (for example, negative, or less than enough.)
Generated By: ParDrivr.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3922 Invalid Repr in DataInfo Parcel.
Explanation: The user sent a DataInfo parcel with an invalid data type code, using the Parameterized SQL mode, in
which statements are first PREPAREd to give the host information on parameter data types, and the host returns a DataInfo
Parcel instead of building a USING phrase for the query.
Generated By: ParDrivr.
For Whom: End User or System Support Representative.
Remedy: Correct the error and resubmit the request.

3923 Primary index has NOT valid flag set.
Explanation: Internal Teradata inconsistency exists.
Generated By: MGC modules.
For Whom: The DBA or System Support Representative.
Notes: The table in question has probably been destroyed.
Remedy: DROP the table. Save all relevant information and contact your support representative.

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