Why would you need to grant execute or any other privilege on a trigger? It is executed automatically when the corresponding dml is run on the table or action is taken within the database. No privilege is needed outside those granted on the table. I suppose you might need to put an alter privilege on it to allow a non-privileged user the ability to change the trigger if you really wanted to, but I cant think of anything else... On 11/1/07, William Wagman <wjwagman@xxxxxxxxxxx> wrote: > > Greetings, > > I have been playing around trying to grant execute on a trigger to a > particular user. After playing with this for a while and reading docs I > have come to the conclusion that execute on a trigger is not an allowed > grant. Instead the access is given via a public synonym. For example, > give the particular trigger, usera.trigger. If usera wants to allow > userb to use the trigger it is sufficient merely to create a public > synonym, create public synonym trigger on usera.trigger and user b will > then be able to use the trigger. Seems to simplistic for me, is that > correct or am I missing something? > > Thanks. > > Bill Wagman > Univ. of California at Davis > IET Campus Data Center > wjwagman@xxxxxxxxxxx > (530) 754-6208 > -- > //www.freelists.org/webpage/oracle-l > > > -- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'