Shutting the listener down is often efficient for preventing access from a client ... Otherwise a login trigger can sometimes work wonders to make a user understand that he isn't really welcome. You can check the contents of some table and, depending on the contents and the current user, allow or deny using the database.
The problem is that none of these solutions solves the issue of people who are already connected when they shouldn't. I presume that your problem is to perform maintenance operations on an application that shares the database with another application that must keep on running?
On Mon Dez 18 22:35 , dba1 mcc sent:
we have ORACLE 9ir2 on LINUX server. I knew I can
startup database on "restrict mode" and only allow DBA
Does there has other way to allow only dedicate users
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around