Teradata SQL Error and Failure Codes from Error 3538 To 3548

SQLServerF1_Header_Small

3538 A MultiLoad UPDATE Statement is Invalid.
Explanation: The user has provided an UPDATE statement in a MultiLoad Complex Import Task that does not fully
specify a primary index value, does not fully specify the values of all the partitioning columns, or modifies the primary index or partitioning columns.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.
The WHERE condition, including any taken from a view definition, must allow for primary index access (and, if partitioned, partition access) with possible ANDed residual conditions. The list of updated fields must not include any column in the primary index or partitioning expression, and only one table may be referenced.

3539 Recipient %VSTR does not exist.
Explanation: The recipient database or user referenced in the Teradata SQL statement does not exist.
Generated By: OPT modules.
For Whom: End User.
Notes: This error may be caused by a misspelled recipient database name or user name.
Remedy: Resubmit statement with a valid recipient name.

3540 Number of tables in join exceeds Parser limit.
Explanation: The user tried to join more tables than the Teradata SQL Parser could process.
Generated By: OPT modules.
For Whom: End User.
Remedy: Simplify the request and resubmit it.

3541 The request to assign new PERMANENT space is invalid.
Explanation: The user tried to give more PERMANENT space to the new user or database than the parent user or database
had available, or the user tried to reduce the space below the amount in use.
Generated By: OPT modules.
For Whom: The DBA and the end user.
Remedy: Either decrease the PERMANENT space in the new database or increase the PERMANENT space in the parent
database.

3542 Object database owns recipient database.
Explanation: In a GIVE, the object database currently owns the recipient database. The GIVE is invalid because it causes a circular path in the database ownership hierarchy.
Generated By: OPT modules.
For Whom: End User.
Remedy: Review and verify the database ownership hierarchy.

3543 Owner has insufficient SPOOL space.
Explanation: The user tried to give more SPOOL space to the new user or database than what the parent has available.
Generated By: OPT modules.
For Whom: The DBA and the End User.
Notes: In a CREATE USER or CREATE DATABASE statement, when the SPOOL space is not specified, the new database
receives the largest possible SPOOL space — the same SPOOL space as the parent.
Remedy: Either decrease the SPOOL space in the new database or increase the SPOOL space in the parent database.

3544 Partial string matching requires character operands.
Explanation: The user used the partial string matching operator (LIKE) with an argument that was not a character
string.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the request and resubmit it.

3545 Only the user %VSTR can execute this statement.
Explanation: The user tried to execute a restricted Teradata SQL statement.
Generated By: SYN and RES modules.
For Whom: The DBA.
Remedy: Log on as one of the users given in the message before executing this statement.

3546 Default values may not be parameterized.
Explanation: Parameter (non data type value) is not allowed as a default option in a create or alter table.
Generated By: OPT modules.
For Whom: The User.
Remedy: Do not use a non data type value as a default option when creating or altering a table.

3547 MLoad target table may not contain unique secondary indexes.
Explanation: It is not possible to BEGIN MLOAD on a table with Unique Secondary Indexes.
Generated By: OPT modules.
For Whom: The User.
Remedy: Remove the Unique Secondary Index.

3548 The user cannot run FastLoad and MLoad at the same time.
Explanation: The user tried to run a FastLoad and MLoad at the same time.
Generated By: OPT modules.
For Whom: The User.
Remedy: End the currently running job before submitting the new one.

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