HPE NonStop SQL/MX Error – 11002 Trigger TriggerName on table TableName may be triggered recursively more than 16 times.

In this blog post, let’s learn about the error message “11002 Trigger TriggerName on table TableName may be 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

11002 Trigger TriggerName on table TableName may be triggered recursively more than 16 times.

Reason for the Error

During execution, a trigger was generated recursively more than 16 times.

Solution

None. This message is a warning only

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022