Re: Restricting ODBC access to Oracle

You did not say what release of Oracle you have, but as I understand it in 8.1.5 and up you can set system level triggers, possibly at connect time, that can check (through v$session and v$process) what program and terminal the is being used. If it is not an accepted program, raise an exception that will cause the program to blow. It should work for ODBC and any other technique (home grown PRO*C, for example.)

In article <93fo35$9qktn$3_at_ID-62141.news.dfncis.de>,   "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote:
> create a role with select privileges only. Make this role the default
 role.
> Other roles need to be enabled by issuing the set role command. This
 will
> not work from Access as the command is executed in a separate Oracle
> session.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
>
> "bhogak" <bhogak_at_my-deja.com> wrote in message
> news:93fjfa$178$1_at_nnrp1.deja.com...
> > I wish to restrict end-users from accessing our Prod database using
> > ODBC (MS-Access) or SQL*Plus. In the later case, I think I can use
 the
> > Profile tables to control their access. But how can I control their
> > access thru ODBC?
> >
> > Thx.
> > Bhogak.
> >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
>

--
Joseph R.P. Maloney, CCP,CSP,CDP
MPiR, Inc.
502-451-7404
some witty phrase goes here, I think.


Sent via Deja.com
http://www.deja.com/