Before you just commit, make it an autonomous transaction (so you don't
commit more than you thought you were). It shouldn't matter (caveat) -
since they are just now logging in, they should *not* have any other
transactions they might want to rollback later. I haven't tested it, but
does the logon trigger fire when I do a remote 'SELECT...FROM
table_at_server_where_logon_trigger_lives'?
Peter Sylvester wrote:
> Well, for one thing, I don't see this committed anywhere...
>
> --Peter
>
> Lisa McGrath wrote:
>
>> I'm trying to create a simple logon trigger but it never seems to fire.
>> We're running Oracle 8.1.7.3.0 on a UNIX AIX system.
>>
>> The trigger I'm trying to create is:
>>
>> CREATE OR REPLACE TRIGGER set_id_on_logon
>> AFTER logon ON DATABASE
>> BEGIN
>> insert into uwsias.rls_trigger_test
>> values (user, 'Executing logon trigger',sysdate);
>> END;
>>
>> I have already created the uwsias.rls_trigger_test table and have
>> granted all on the table to PUBLIC and directly to SYS, SYSTEM, and
>> CSILVA (a test id). I've created this trigger both as SYS and as
>> SYSTEM, and have created it both as ON DATABASE trigger and ON
>> CSILVA.SCHEMA trigger. Nothing seems to work.
>>
>> The trigger created ok, is valid and enabled. When I logon as CSILVA I
>> connect ok - no 'insufficient privileges' or other error message, but
>> no record is inserted either. Am I missing a step? Does the database
>> need to be restarted before a logon trigger will take effect? Some
>> parameter that needs to be set?
>>
>> Thanks for any help.
>>
>> Lisa
>> --
>> Lisa McGrath
>> Lmcgrath_at_uwsa.edu (608) 263-4535
>> Office of Information Services
>> University of Wisconsin System Administration
>> --
>>
>>
>
Received on Thu Nov 21 2002 - 16:07:56 CST
