Teradata SQL Error and Failure Codes from Error 5410 To 5424

SQLServerF1_Header_Small

5410 Invalid TIME Literal.
Explanation: The value of the literal does not represent a valid time.
Generated By: MOVEROW
For Whom: End User.
Remedy: Correct the request and resubmit it.

5413 Invalid Time Zone Specified.
Explanation: The specified expression is not a constant expression or the resulting expression value does not represent a
valid time zone displacement or time zone string. A time zone displacement must be between INTERVAL -’12:59’ HOUR
TO MINUTE and INTERVAL ’14:00’ HOUR TO MINUTE.
Generated By: OPDSSTZ
For Whom: End User.
Remedy: Correct the request and resubmit it.

5416 The trigger action time must be BEFORE or AFTER.
Explanation: An invalid trigger action time was specified. There can only be one action time per trigger and it must be
BEFORE or AFTER.
Generated By: SYN and Resolver
For Whom: End User.
Remedy: Redefine the trigger with the correct trigger action time.

5417 The trigger event must be INSERT, UPDATE or DELETE.
Explanation: An invalid trigger event was specified. There can only be one event per trigger and it must be INSERT,
UPDATE or DELETE.
Generated By: SYN and Resolver
For Whom: End User.
Remedy: Redefine the trigger with the correct trigger event.

5419 Trigger “%VSTR” already exists.
Explanation: The user tried to create a table, view, macro, trigger, procedure, or function and a trigger with that name
already existed. This error occurs on the CREATE TABLE, VIEW, MACRO, TRIGGER, PROCEDURE or FUNCTION statement.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different trigger name and resubmit the request.

5420 No triggers exist for table “%VSTR”.
Explanation: The user tried to enable or disable all triggers for a table that has no defined triggers. This resulted from an
Alter Trigger tablename command.
Generated By: RES modules.
For Whom: End User.
Remedy: Verify the request and make sure that the target table has defined triggers. Resubmit the request.

5421 Cannot drop or rename a column referenced by a trigger.
Explanation: The user tried to drop or rename a column that is referenced by a trigger. To allow this would create inconsistent
trigger definitions.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not drop or rename the specified column, use replace trigger to change the trigger definition or drop the
trigger.

5423 This trigger contains an invalid REFERENCING clause.
Explanation: The REFERENCING clause contains one of the following errors:
1. Old and/or New are used in an improper combination with Old_Table and/or New_Table.
2. A statement trigger used the OLD or NEW correlation name identifier.
3. A row trigger used the OLD_TABLE or NEW_TABLE correlation name identifier.
4. The name specified in this clause was not unique within the trigger.
* DR87420-TS185009-01 * 5. Disallow cascaded row triggers with transition table references.
6. A field without any reference is invalid when OLD_NEW_TABLE correlation name is specified.
Example of an invalid statement in a trigger body: sel * from old_new_tab;
Generated By: Resolver
For Whom: End User.
Remedy: Redefine the trigger with a correct REFERENCING clause.

5424 A triggered action statement is the wrong kind.
Explanation: The following are the valid triggered actions for the AFTER triggers: 1. INSERT 2. DELETE 3. UPDATE 4.
ABORT 5. EXEC macros containing any of the above statements.
The following are the valid triggered actions for the BEFORE triggers: 1. ABORT 2. EXEC macros containing ABORT statements
only. 3. SET (only for BEFORE row triggers)
Generated By: SYN
For Whom: End User.
Remedy: Redefine the trigger with the proper triggered action statement.

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