Re: Can updates via ODBC be disabled while retrievals are allowed?

Using GRANT SELECT ON table_name TO user; should do the trick.

If you have a lot of users and/or tables look into creating a role(s) that are authorized to select a set of tables and then GRANT role_name TO user;

I think the best approach is to assign select to the role(s) for each set of tables. Drop all of the existing users (yeah, I get kind of drastic), Create each of the users, grant them session so they can connect to the database, and then grant them one or more roles as appropriate.

Jerry

Mitchell Nussbaum wrote:
>
> Some of my users have Oracle tables that are updated via PowerBuilder
> applications. The managers of these applications are thinking of
> installing ODBC and MS Access on their users' workstations, to allow them
> to generate ad hoc queries and reports against these tables.
>
> They are concerned, however, that some of these users will try to use
> Access to update the Oracle tables, circumventing the data-integrity checks
> that are built into our PowerBuilder applications. Can anyone suggest ways
> of cutting off this end-run of our system? In particular, is there are way
> to make an Oracle ODBC data source read-only, or to configure the Oracle
> Server (we are running 7.1.5 under Open VMS for AXP) to reject update
> transactions that come via ODBC?
>
> (I know, of course, that we can disable ODBC updates by removing the
> primary keys from our tables. But I'm not sure that trick will always be
> feasible for us.)
>
> Thanks for any help you can offer.
>
> Mitch Nussbaum
> Wisconsin Department of Natural Resources
> nussbm_at_dnr.state.wi.us
Received on Mon Oct 27 1997 - 00:00:00 CST