Hello Pando:

I did implement or try to execute a trace using logon trigger The trc files are indicating some one has and does not have the permissions to do
so. See the following notes:

From the alert log:

Errors in file /home/oracle/admin/ODBMSPRD/udump/ora_60654_odbmsprd.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 4
Fri Aug 16 10:20:36 2002


From udump:

PROD box [AIM]: more ora_61266_odbmsprd.trc
Dump file /home/oracle/admin/ODBMSPRD/udump/ora_61266_odbmsprd.trc
Oracle8i Enterprise Edition Release 8.1.7.1.0 - Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
ORACLE_HOME = /home/oracle/product/8.1.7
System name: AIX
Node name: CG_JDA1
Release: 3
Version: 4
Machine: 0007904F4C00
Instance name: ODBMSPRD
Redo thread mounted by this instance: 1
Oracle process number: 71
Unix process pid: 61266, image: oracle@CG_JDA1 (TNS V1-V3)

*** SESSION ID:(330.524) 2002-08-16 10:20:45.951
Skipped error 604 during the execution of COTPROD.TRACE
*** 2002-08-16 10:20:45.964
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 4

Remember from my previous note, I created a logon trigger as "non-SYS user" by the time you came back to say that should be created as "SYS" user..

This is generating tonnes of trc files in udump and in bdump alert.log files entries..

We have bounced the db for cold backup yday and I have also dropped the trigger this morning as well...

Please suggest..

Thanks, ST2000