In this blog post, let’s learn about the error message “11003 Trigger TriggerName on table TableName was triggered recursively more than 16 times.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.
Error Message
11003 Trigger TriggerName on table TableName was triggered recursively more than 16 times.
Reason for the Error
During execution, a trigger was generated recursively more than 16 times.
Solution
The threshold of 16 is hard-coded and cannot be changed. You can either rewrite your statement or redesign your triggers for less trigger recursion by adding conditions to your trigger actions