Teradata SQL Error and Failure Codes from Error 3924 To 3934

3924 Internal error: Invalid memput attempted.
Explanation: Internal Teradata Parser inconsistency exists. Either a memput was attempted with release.offset <=
header.offset, or a memput was attempted with release.base <> header.base.
Generated By: MEM modules.
For Whom: System Support Representative.
Remedy: Save all relevant information, including the dump, and notify your support representative.

3925 Internal error: Invalid statistics or a NUSI is almost a USI, for table %VSTR.
Explanation: Internal Teradata inconsistency exists. Either the statistics say a non-unique secondary index has more
rows than the total for the table, or a non-unique secondary index has no rows when the base table has rows.
This error could sporadically occur if a NonUnique SecondaryIndex(NUSI) is almost UNIQUE.
Generated By: MGC modules.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3926 Parcel length exceed maximum using data size.
Explanation: The user sent a parcel that parcel length exceeded the maximum using data size. The maximum using data
size can store 65535 bytes.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Modify query and resubmit the request.

3927 Response Parcel requested a max byte count less than 256.
Explanation: The smallest permitted value for the maximum byte count for responses to the Host is 256 Bytes.
Generated By: SQL TEQPastd, DIS DISPastd, SCP DISPastd modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3930 The dictionary cache is full.
Explanation: No items were available for removal when the user tried to add something to the dictionary 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. In this case, rather than cause a Teradata restart, the parser catches the error, spoils the cache, and returns an error.
Creation of a large table with defaults and titles probably caused this error. The error was probably received during an alter table which means that a huge table still exists and will probably return this error on an Insert or Select All .
Generated By: MGC modules.
For Whom: Internal.
Remedy: Increase the DBS Control Record field DictionaryCacheSize. See Teradata Utilities Manual for information on
DBS Control fields. Simplify the table by reducing the number of columns or shortening or removing some of the titles or
defaults .

3931 Journaling was declared with no declared or default Journal table.
Explanation: A statement has attempted to create a table with some type of permanent journaling declared, either
explicitly or by the database default, and there is no explicitly declared journal table and no default journal table for the
Generated By: OPT and GEN modules.
For Whom: End User.
Remedy: Either specify a journal table, or specify no journaling.

3932 Only an ET or null statement is legal after a DDL Statement.
Explanation: A DDL statement was issued previously. By our current rules, the only time that a DDL statement can be
issued inside an explicit transaction is when it is the last statement in that Transaction. In an explicit transaction, the only
statements allowed after a DDL statement are an END TRANSACTION , an unconditional ABORT, or a NULL statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Either do the DDL statement as a single statement transaction, or commit the containing transaction immediately
after the DDL statement.

3933 The Maximum Possible Row Length in the Table is too Large.
Explanation: During a CREATE, or ALTER TABLE the user has tried to specify a table whose potential Row Length is
greater than we currently allow. For example:
CREATE TABLE TooLong ( A VARCHAR(40000), B VARCHAR(40000) );
Produces this error because if allowed it could create a table with a row length of over 80,000 bytes. Our current maximum
row length is limited to approximately 64,000 bytes.
If we get this error during the migration process, which indicates that the data row size is exceeding the 64K limit on target
platform. This can happen while migrating the data from 32-bit platform to 64-bit platform.
Generated By: OPT modules.
For Whom: End User.
Remedy: Either remove some of the fields defined in the table or decrease the length of some of the Character, graphic,
and Byte fields.

3934 Session is in wrong state for cleanup request.
Explanation: Session control has sent the Parser a cleanup request for a session that is not in a state where it can be
cleaned up safely. For example, the session should never show that the Parser is processing a request.
Generated By: CON modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

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