Automic Rule #2:
sometimes, you need to modify the database directly, or SQL is the only reasonable way to get something done.
In that case, make up your suggested SQL statement and send it to Automic support to have it approved, along with the reasoning why this is without a reasonable alternative.
If they agree, they will pass your SQL to a developer who will look at it and consider side effects. He will send it back via support. When it comes back and has been modified, one is well advised to check it again, because they might have modified it in a faulty, incompatible with your DB dialect, or worst case, even dangerous way. Over some iterations, consensus can then be reached on a safe SQL statement, and only a few days later, one can execute an automic-approved SQL statement while enjoying full support (hopefully).
At least that's how it worked for me when we insisted that we'd rather run an SQL statement than open and modify about 6000 SAP jobs each, one after another.