I have an AFTER UPDATE for each row trigger, which inserts into an audit_table.
How to prevent rolback of triggering statement (UPDATE) when inserting in audit_table is not possible and cause an exception?
AFAIK: no, no chance with triggers. But in DB2 z/OS you can activate the audit traces and if you have the right tools, like DB2PM, you can analyse these information and see who selects, updates or what ever a special table.
Perhaps calling from trigger a stored procedure which inserts into audit_table will solve the problem?
Sorry for asking silly questions, but I'm new to DB2 and I found that DB2 documentation is far more difficult to search and understand than Oracle. In Oracle this trigger situation can be avoided very easy.