Try deleting the file override before issuing the SQL delete statement.
Bear in mind that a major point of “overrides” is to exert external control or influence over internal processes. A process might be created using an internal reference (library/object) but may be executed over a different object without needing to alter the encapsulated code.
As far as the system is concerned, this is a management/security mechanism.
What you’re asking is how to defeat it. I’m not sure how appropriate it would be to discuss in a public forum, assuming such an action is possible.
That’s hardly what you want to hear, and I don’t want to suggest that I am discussing your motivation — I think it’s clear that your motivation involves protecting resources.
But you might not get better advice than what WoodEngineer provided.