In this blog post, let’s learn about the error message “11033 Object name1cannot be dropped because it is being used by trigger name2.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.
Error Message
11033 Object name1cannot be dropped because it is being used by trigger name2.
Reason for the Error
You attempted to drop an object name that is being used by a trigger.
Solution
If possible, drop the trigger first, and then drop the object. You can use the cascade option to drop the object, but you risk dropping all objects that use that object, including the triggers