You can do with after logon on database trigger
eg as per http://www.orafaq.com/scripts/security/notoad.txt
Note - sys can still connect
And, someone can just alter the name of client application to get around =
it
SQL > CREATE OR REPLACE TRIGGER block_access
2 AFTER LOGON ON DATABASE
3 BEGIN
4 =20
5 RAISE_APPLICATION_ERROR(-20000, 'No one can connect ');
6 end;
7 /
-- --Original Message-- --
[mailto:oracle-l-bounce@(protected)]On Behalf Of Tim Gorman
Sent: Friday, 13 August 2004 1:49 PM
Unfortunately (or rather, fortunately), a failure in an AFTER LOGON =
trigger
does not do anything to interfere with the session...
SQL > connect scott/tiger
Connected.
SQL > create or replace trigger x
2 after logon
3 on schema
4 begin
5 raise_application_error(-20000, 'raise error ');
6 end x;
7 /
NOTICE
=20
This e-mail and any attachments are private and confidential and=20
may contain privileged information
=20
If you are not an authorised recipient, the copying or distribution=20
of this e-mail and any attachments is prohibited and you must not=20
read, print or act in reliance on this e-mail or attachments
=20
This notice should not be removed
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ___
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
