You can audit execute on a given procedure by access or by session, but it is sort of global.

You can audit an individuals execution of any (all) procedures, it'll be global for that user (could be a ton of information as every procedure executed will appear here)


So, path of least resistance - audit execute on procedure_name by session, that'll give you a single record for each session that executes the procedure (regardless of who executed it)

sys%ORA10GR2> connect /
Connected.
ops$tkyte%ORA10GR2> audit execute on p1 by session;

Audit succeeded.

ops$tkyte%ORA10GR2>
ops$tkyte%ORA10GR2> connect a/a
Connected.
a%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

a%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

a%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

a%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

a%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

a%ORA10GR2> connect b/b
Connected.
b%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

b%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

b%ORA10GR2> exec ops$tkyte.p1

PL/SQL procedure successfully completed.

b%ORA10GR2> connect /
Connected.
ops$tkyte%ORA10GR2> select username, owner, obj_name, action_name from dba_audit_trail;

USERNAME OWNER      OBJ_N ACTION_NAME
-------- ---------- ----- ----------------------------
B        OPS$TKYTE  P1    SESSION REC
A        OPS$TKYTE  P1    SESSION REC

It will not be selective by user, but you can always filter that with a where clause.



This is short of renaming (by recreating) the procedure P1 to P1_ORIG and creating something like:

create procedure p1( ... inputs/outputs ... )
as
begin
   if (user = 'X')
   then
       call_autonomous_transaction_to_log_execution;
   end if;
   p1_orig( .... inputs/outputs ... );
end;