Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Trap ODBC connections?
Cyrus,
This is tricky at best. I have asked ORACLE support concerning the
product_user_profile and ODBC. If you've been around long you will
know that the PRODUCT_USER_PROFILE was added to correct a very LARGE
hole in the DB security. In v5 and v6 one could enforce security
issues through applications (then IAP, IAG, ...) but not for SQL*Plus.
ORACLE's answer was to add the PRODUCT_USER_PROFILE table and make
SQL*Plus query and enforce entries in this table during run time.
However, for ODBC there is no such enforcement. Thus, a valid user
could completely circumvent the security afforded by the PRODUCT_USER_
PROFILE table using ODBC.
As far as I know the entry in the V$SESSION table for ODBC and SQL*Net will be nearly identical. If you can narrow down a difference then you could write some procs/scripts to kill off ODBC connections. I know there is an entry which looks like 'TNS....' but I don't know what the ODBC entry looks like. My guess is it's the same since it is connecting through SQL*Net but using ODBC.
Good luck,
I think this would make a nice slap in ORACLE's face should one want
to pursue it ;)
Marc Marchioli
The DataBase Group, Inc.
http://www.databasegroup.com
Cyrus AU YEUNG wrote:
>
> Dear all experts,
>
> May I know is it possible to trap/stop all ODBC connections to an
> Oracle 7 database? I want to make SQL*NET is the only way to connect to
> the database.
>
> Thanks!
>
> Cyrus
Received on Wed Oct 15 1997 - 00:00:00 CDT