Teradata SQL Error and Failure Codes from Error 3549 To 3559

3549 MLoadTask is not running.
Explanation: The user tried to do an END MLOAD or RELEASE MLOAD and MLoad is not running.
Generated By: OPT modules.
For Whom: The DBA and the End User.
Remedy: Start MLoad prior to submitting these statements.

3550 Table named in MLOAD statement not in list from BEGIN MLOAD.
Explanation: The user named a table to be loaded in an MLOAD statement which was not in the list of tables specified to
be loaded by BEGIN MLOAD.
Generated By: OPT modules.
For Whom: The DBA and the End User.
Remedy: Change table name in statement or add to BEGIN MLOAD list of tables.

3551 The user cannot DROP a database that has descendants.
Explanation: The user tried to drop a database or user which had created other databases or users.
Generated By: OPT modules.
For Whom: The DBA and the End User.
Remedy: Drop the underlying databases or give them to another database. Resubmit the request.

3552 Cannot DROP databases with tables, journal tables, views, or macros.
Explanation: The user tried to drop a database or a user when one or more tables, journal tables, views, or macros
existed in that database.
Generated By: OPT modules.
For Whom: The DBA and the End User.
Remedy: Drop the underlying tables, or issue a DELETE DATABASE statement to drop all the underlying tables. And, if
there is a journal table in the database, then use MODIFY DATABASE to drop it. Resubmit the request.

3553 The user cannot RENAME to a new database.
Explanation: The target table name in a RENAME statement is in a different database than the source table name.
Generated By: OPT modules.
For Whom: End User.
Remedy: Use a CREATE TABLE statement followed by an INSERT statement with a query specification to move the
table to a new database.

3554 HAVING clause must be preceded by GROUP BY clause.
Explanation: The user cannot use a HAVING clause without a corresponding GROUP BY clause. The HAVING clause
selects the values that the GROUP BY clause uses.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct SELECT statement and resubmit request.

3555 Only the last WITH clause can omit the BY information.
Explanation: Omitting the BY portion of the WITH clause implies that the WITH summary must be done on the entire
base table. Since WITH clauses are assumed to appear in increasing scope, following such a WITH with a narrower-scope
WITH should not be done.
Generated By: OPT modules.
For Whom: End User.
Remedy: If possible, reorder the WITH clauses and resubmit the request.

3556 Too many columns defined for this table.
Explanation: As a table is modified and fields are dropped and added, each new added field is given a higher column id
than any prior column id for the table. The range from highest to lowest column id in a table is restricted, for internal reasons, to SYSMAXFIELDS, which is 2560.
Generated By: GEN modules.
For Whom: End User.
Remedy: If the error occurred during ALTER TABLE, then if a new column is absolutely necessary in the table, the table
must be rebuilt. Create a new table with the existing data. If the error did not occur during ALTER TABLE, then the cause must be that some spool file has been defined with too many columns. Examine the query and modify to use fewer columns.

3557 Column %VSTR is an index column and cannot be dropped.
Explanation: An index column cannot be dropped by a ALTER TABLE statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: If the column needs to be dropped, drop the index containing that column with the DROP INDEX statement.

3558 Cannot alter the specified attribute(s) for %VSTR.
Explanation: Most column attributes cannot be modified after the column is created. Exceptions are those attributes
which can be changed without changing the internal storage of the data. Please refer the Teradata SQL Reference : Data
Definition Statements. DR94963-bessc-01: For V2R6.2, the COMPRESS attribute for existing column(s) can be changed with
the ALTER TABLE <table name> ADD <column name> COMPRESS command option. Example: ALTER TABLE Tab1 ADD
Column1 COMPRESS(’OldValue1’, ’OldValue2’, ’NewValue1’, ’NewValue2’); NOTE that the new Compress list
REPLACES the old list.
Generated By: OPT modules.
For Whom: End User.
Notes: Usually, if the modification causes all existing rows to be updated or invalidated, the modification is not allowed.
Remedy: If the attribute needs to be modified, the user may need to create a new table.

3559 Column %VSTR is not NULL and it has no default value.
Explanation: The column is specified as not NULL, and a default value is not defined for it.
Generated By: OPT modules.
For Whom: End User.
Remedy: Either define the column NULL or define a default value for the column.

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