HPE NonStop SQL/MX Error – 11036 No triggers are defined on table table-name.

In this blog post, let’s learn about the error message “11036 No triggers are defined on table table-name.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

11036 No triggers are defined on table table-name.

Reason for the Error

You attempted to “alter trigger enable/disable all of” on a table that does not have triggers.

Solution

None

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