COMMIT needed for invoker rights proc?

Question

The following proc EXEC_PROC in a package named PKG_DYNAMIC_SQL is called by the proc RUN_PROCS which is in a different package shown below:
PROCEDURE exec_proc (pi_proc_name IN varchar2 ,pi_acctky IN varchar2 )
AS
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
EXECUTE IMMEDIATE 'BEGIN ' || pi_proc_name || '(:acctky );' || ' END;' USING IN pi_acctky ;
END exec_proc;
PROCEDURE run_procs(pi_proc_names_tab IN pkg_types.t_tab_proc_names)
IS
BEGIN
FOR indx IN pi_proc_names_tab.FIRST .. pi_proc_names_tab.LAST
LOOP
pkg_dynamic_sql.EXEC_PROC ( pi_proc_names_tab(indx) ,pi_acctky) ;
END LOOP;
END run_procs;
The pi_proc_name is a set of stand alone procs that do an UPDATE statement. I find that unless I have a COMMIT statement inside each pi_proc_name I get a RUN TIME ERROR. Am I right in saying that cause I have a BEGIN END ( Anonymous block) pair round the invocation of pi_proc_name I am using INVOKER RIGHTS? Has that something to do with the error when the called proc does not commit before it exits?
Please help me understand why?

Answer 1

does the called proc inherit the AUTONOMOUS TRANSACTION from the caller as in my example?No.
Actually, I'm not sure what you mean:
RUN_PROCS is calling EXEC_PROC (the autonomous transaction).
So: RUN_PROCS is the caller, not EXEC_PROC.
And I would only use autonomous transactions for error logging purposes. Nothing else.
If I understand correctly you're executing several procedures dynamically and each procedure gets committed as a separate transaction, (since they're all autonomous, they cannot 'see' each other anymore, all transactional logic is gone) all in one loop. That's a classic recipe for disaster when unexpected things happen, and they will happen sooner or later.
Are you sure it is safe to execute procedure 'Y' when procedure 'X' went into an error/committed 'the wrong' data/?
In other words: I hope this whole approach a well thought-out strategy, but usually dynamic (PL/)SQL + autonomous transactions = trouble/breaking code/corrupting data.