| |
- Causa
- THE ACTIVATION OF THE object-type OBJECT object-name WOULD EXCEED THE MAXIMUM LEVEL OF INDIRECT SQL CASCADING
Cascading of indirect SQL occurs when a trigger, user-defined function or stored procedure invokes another trigger, user-defined function or stored
procedure which in turn invokes another.
The activation of some of the triggers in this chain might be due to the enforcement of referential constraint delete rules.
The depth of this cascading is limited to 16.
Note that recursive situations where a trigger includes a triggered SQL statement that directly or indirectly causes the same trigger to be
activated are very likely to cause this error.
The trigger should contain logic to check for a terminating condition to prevent this error.
- object-type
- Names the type of object being called.
Object type is TRIGGER, FUNCTION, or PROCEDURE.
- object-name
- Specifies the name of the trigger, user-defined function or stored procedure that would have be activated at the seventeenth level of cascading.
- Ação do sistema
- The original statement could not be executed.
All SQL statements executed by all triggers, user-defined functions, and stored procedures in the cascade chain are rolled back.
External actions performed by the indirect SQL, such as sending a network message might have already occurred.
- Resposta ao Desenvolvedor
- Start with the indirect SQL that is activated by the original SQL operation.
Check for recursive patterns in any invoked user-defined functions or in any triggers defined on the subject of an update operation.
If the chain is not recursive, the cascade chain must be simplified by altering the triggers, user-defined functions, or stored procedures involved.
SQLSTATE: 54038
© Copyright IBM Corp.
|
| |
