I found two other workarounds. Can you share your opinion on these?
1)Create a PL/SQL package that reads SQL statements from the table and executes them.
2) Have the AFTER SUSPEND trigger write the SQL statement necessary to fix a problem in a table.

But who read the "statement table"? A job!
I think it is better to spawn a job from the trigger instead of waiting that your polling job reaches your statement.
But why not if you reach a suspend event many times.