Re: Stop users from connecting to database

"Peter" <peter_at_nomorenewsspammin.ca> wrote in message news:f8uncvsoe5qfp33jv0bi2vgnhghjfr4vtd_at_4ax.com...
> On Tue, 20 May 2003 11:17:24 GMT, b.sandmann_at_gmx.net (Bernd Sandmann)
> wrote:
>
> How about creating a role and only allow that role to do batch jobs?
>

Since a role is a collection of privileges, and there's no privilege to distinguish a 'batch job' from a non-batch job, this isn't going to get you anywhere.

The best I can think of is to use 8i's Resource Manager. There, you create groups of users, such as "DBAs", "BATCH" and "OLTP". You can't stop a group member logging on, but by creating a Resource Plan that says 'BATCH users get 0% of the CPU during normal hours', you can lock them up so they can't actually do anything. (The options get subtler in 9i... let them log on, let them do work, but if one of their jobs is *estimated* to take longer than X seconds, lock them up, for example).

You can then create another plan for non-normal hours, where BATCH members get 100% of the CPU.

Resource Manager seems to me to be the way to go.

Regards
HJR
>
> >Hello,
> >
> >what is the best way to avoid users from connecting to a database but
> >some other users should connect anyway.
> >
> >The reason for this is that some batch jobs should run under a special
> >users while other users should not connect to the database.
> >
> >regards.
> >Bernd Sandmann
>
Received on Thu May 22 2003 - 07:01:20 CDT