Teradata SQL Error and Failure Codes from Error 5425 To 5435

SQLServerF1_Header_Small

5425 An updatable cursor update or delete is not allowed upon which a trigger has been defined.
Explanation: Teradata does not allow updatable cursor updates or deletes on tables that have triggers defined.
Generated By: RES
For Whom: End User.
Remedy: Do not use updatable cursors on tables with triggers defined.

5426 “%VSTR” is not a trigger.
Explanation: The specified item is a view, macro, or table and the context of the query returning the error requires the item to be a trigger.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

5427 Trigger is greater than 20480 characters after name expansion.
Explanation: The text of the trigger exceeded the maximum length after all names in the referenced trigger were fully
qualified and expanded.
Generated By: RES modules.
For Whom: End User.
Remedy: Simplify the trigger and resubmit the request.

5428 Table “%VSTR” has defined triggers.
Explanation: A table cannot be renamed or dropped if it has defined triggers.
Generated By: RES and OPD modules.
For Whom: End User.
Remedy: Either drop the triggers or do not submit the request.

5429 A triggered action statement contained an invalid reference.
Explanation: A triggered action statement either:
1. Referred to an Old or New correlation name as a table.
2. Referred to an Old_Table or New_Table table as a row.
3. Referred to an Old or New correlation name as a row and used a range constraint to scan rows.
4. Referred to OLD_NEW_TABLE correlation in a row trigger.
5. OLD_NEW_TABLE referencing clause can only be used in an UPDATE trigger.
6. A field reference in a trigger body cannot directly use the OLD_NEW_TABLE correlation name. It has to use the
OLD_NEW_TABLE row alias name.
Generated By: RES modules.
For Whom: End user.
Remedy: Correct the triggered action statement.

5430 The Trigger WHEN clause cannot contain an aggregate or table reference.
Explanation: By ANSI rules, the WHEN clause cannot contain an aggregate or table reference.
Generated By: RES modules.
For Whom: End user.
Remedy: Remove the aggregate or table reference from the WHEN clause and resubmit the request.

5431 The update column list can only be used with UPDATE trigger event.
Explanation: Delete and Insert statements pertain to rows, not columns. The update column list can only be used with
the UPDATE trigger event.
Generated By: RES modules.
For Whom: End user.
Remedy: Either remove the update column list or change the trigger event to UPDATE.

5432 A trigger Order value must be within a range of 0 to 32767.
Explanation: The Teradata database requires the trigger order to fall within the specified 0 to 32767 range.
Generated By: RES modules.
For Whom: End user.
Remedy: Change the order value to a valid number.

5433 The update column list can only contain subject table columns.
Explanation: Only subject table columns can be used in the update column list.
Generated By: RES modules.
For Whom: End user.
Remedy: Remove any columns not in the subject table.

5434 A syntax error occurred in a triggered action statement.
Explanation: While processing a triggered action statement, the parser detected a syntax error.
Generated By: SYN modules.
For Whom: End user.
Remedy: Correct the offending triggered action statement.

5435 Invalid RS operation.
Explanation: Dummy. (a temporary generic rs error code)
Generated By: Syn/Res/Opt modules.
For Whom: End User.
Remedy: Check if system is ready for Change Data Capture.

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