Teradata SQL Error and Failure Codes from Error 3597 To 3607

SQLServerF1_Header_Small

3597 Request requires too many SPOOL files.
Explanation: The request was too complex and exceeded the maximum number of SPOOL files allowed in the Teradata
database Parser.
Generated By: OPT modules.
For Whom: End User.
Notes: SPOOL files are generated as intermediate work files, as well as result files.
Remedy: Simplify the request and resubmit it.

3598 Concurrent change conflict on database — try again.
Explanation: During processing of the user’s transaction, another user changed the database.
Generated By: ITB, RES, GEN and OPT modules.
For Whom: End User.
Remedy: Resubmit the transaction.

3599 Cannot apply Japanese Date or Time markers to a column of type Kanji1.
Explanation: The FORMAT statement contains Japanese Date or Time marker and is being applied to a Kanji1 field.
Generated By: OPT, EVL, FLT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3600 Comparisons are not allowed for the type %VSTR.
Explanation: This type is not allowed to be compared with equals, less than, greater than, etc. Users cannot modify the
type in any way that will allow it to be comparable because the functionality has been denied internally. Array types are an
example of a kind of type that cannot be compared.
Generated By: OPT modules.
For Whom: End User.
Remedy: Remove the comparison and resubmit. If a comparison is needed, there may be functions that allow comparisons
between the desired types. For example, Array types use the following functions for comparisons: ARRAY_GT,
ARRAY_GE, ARRAY_LE, ARRAY_EQ, ARRAY_NE.

3601 A crash dump has been saved.
Explanation: A Teradata database crash dump has been copied from the primitive dump area into a table. The table
name in which the dump was saved is displayed with this entry.
Generated By: SEM modules.
For Whom: The DBA and the System Support Representative.
Notes: The dump areas are automatically cleared after the save dump is completed.
If an AMP is down and comes back online, the crash dump for that AMP will be added to this dump.
Remedy: This is for information only. The user may want to unload the crash dump to tape (via the DUL program) and
send the tape to your support representative for analysis.

3602 A CLEAR DUMP statement was executed.
Explanation: A CLEAR DUMP statement was issued to clear the primitive dump areas on all processors.
Generated By: OPT modules.
For Whom: The DBA and the System Support Representative.
Remedy: This message is for informational purposes only.

3603 Concurrent change conflict on table — try again.
Explanation: During processing of a user’s transaction, another concurrent session had changed the table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Resubmit the transaction.

3604 Cannot place a null value in a NOT NULL field.
Explanation: The user tried to place a null value in a field specified as NOT NULL. The error has been detected in code
evaluation at a point where the identity of the Table.Column is not available to the error handling routine.
Generated By: OPT modules.
For Whom: End User.
Remedy: Revise the operation so that a null value does not exist.

3605 Illegal multi-table UPDATE operation.
Explanation: The user tried an incorrect UPDATE operation that involved more than one table. For example, the user
tried to change fields in two different tables with one UPDATE.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3606 Two values were given for one field.
Explanation: The user tried an UPDATE operation that specified two or more values for one target field.
Generated By: OPT modules.
For Whom: End User.
Remedy: Decide which value to specify and resubmit the request.

3607 Too many expressions in the select list of a subquery.
Explanation: The user specified a subquery in a set conditional. The subquery specified more values than are specified
in the conditional.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the conditional and resubmit request.

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