Hi!
I think administer database trigger privilege isn't an issue here, it's not
needed when creating schema level logon trigger.
Try to run your execute immediate command first from command line under your
user:
exec Execute immediate 'alter session set events=''10046 trace name context
forever,
Does the user whom you created the trigger have alter session privilege?
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 4:39 PM
As system (8.1.7.3):
create or replace trigger TRIGGER_NAME
after logon on
Yes I tried granting alter session first
-Original Message-
Sent: Tuesday, August 12, 2003 11:24 PM
To: Multiple recipients of list ORACLE-L
Does the user whom you created the trigger have alter session privilege?
Tanel.
- Original Message -
To: Multiple recipients of
As system (8.1.7.3):
create or replace trigger TRIGGER_NAME
after logon on SCHEMA.schema
begin
Execute immediate 'alter session set events=''10046 trace name context
forever, level 12''';
end;
When I logon after creating this trigger as the user SCHEMA I get the
error message insufficient
Try with ADMINISTER DATABASE TRIGGER On 2003.08.13 04:29, Jack van Zanen
wrote:
Yes I tried granting alter session first
-Original Message-
Sent: Tuesday, August 12, 2003 11:24 PM
To: Multiple recipients of list ORACLE-L
Does the user whom you created the trigger have alter session
