Ah, I should have perused the oraus.msg file.
Neat trick, thanks Tanel.
Jared
| "Tanel Poder" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 08/28/2003 01:54 PM
|
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> cc: Subject: Re: How to keep "root" out? |
As an alternative for setting sqlnet.authentication_services to none, you can also set event 10063 which disables usage of OPER & DBA privileges in OSD layer. This one is probably harder to find out for a regular sysadmin (especially when you put it in a wrapped after startup trigger :)
But be careful, I don't know how exactly this event works, but it seems that I can't log on to another test instance under the same user either using sysdba now. And setting this event to "off" didn't help either. Had to bounce (ver 8.1.7.1 on Solaris). Most of events are unsupported as well...
See below,
Tanel.
bash-2.03$ sqlplus "/ as sysdba"
SQL*Plus: Release 8.1.7.0.0 - Production on Thu Aug 28 22:38:51 2003
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.1.0 - Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
SQL> alter system set events '10063 trace name context forever, level 1';
System altered.
SQL> exit
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.1.0 - Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
bash-2.03$ sqlplus "/ as sysdba"
SQL*Plus: Release 8.1.7.0.0 - Production on Thu Aug 28 22:39:03 2003
(c) Copyright 2000 Oracle Corporation. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
