Ben wrote:
> Brian Peasland wrote:
>> Ben wrote:
>>> Oracle 9.2.0.5 Ent Ed AIX5L.
>>>
>>> Is it possible to determine the driver / type of connection that is
>>> being used by different users to connect to the database.
>> Look at the Oracle Reference guide (http://tahiti.oracle.com) for a view
>> called V$SESSION. In that view, you can see columns like PROGRAM,
>> MODULE, ACTION, and CLIENT_INFO. Unfortunately, it is up the application
>> program to set most of this information, which very few apps do. But in
>> all of this, I have yet to see anywhere one can see that the app
>> connected to the database with ODBC, JDBC, OCI, or any other driver. And
>> for the most part, one should not care. I don't care *how* the apps
>> connect to my database, and that is the beauty of a tiered networking
>> approach.
>>
>>> Our ERP system came with an ODA driver that is read only. If any of our
>>> users want to use MS Access to connect to our database they are
>>> supposed to use that driver with linked tables. We have had some data
>>> corruption lately with some rows being updated and some being deleted.
>>> No one is supposed to have the Ora92 driver to avoid this situation,
>>> but we are wondering if someone is using the Oracle supplied driver.
>>> How can I figure this out?
>> I'm not sure why the driver is the issue here. The driver is just the
>> interface to the database. It links the app to the instance. It is up to
>> the app to update and delete data. Oracle manages concurrent DML
>> operations with its transactional control. How does the driver
>> *inadvertantly* update or delete rows of data?
>>
>> Cheers,
>> Brian
>>
>> --
>> ===================================================================
>>
>> Brian Peasland
>> dba_at_nospam.peasland.net
>> http://www.peasland.net
>>
>> Remove the "nospam." from the email address to email me.
>>
>>
>> "I can give it to you cheap, quick, and good.
>> Now pick two out of the three" - Unknown
>
>
> The ODA driver that came with our ERP system does not allow your
> connection to perform updates and deletes. Even the Oracle driver will
> let you setup a connection that is read-only. If the DSN connection
> that you setup, using the Oracle Driver, is set to read-only, then
> wouldn't you expect it to be a read-only connection?
>
Please read the response from Ed in this thread.
It should not be up to the driver to impose read-only "status" on the
session. What if someone uses another driver or turns off the read-only
flag? What if someone uses SQL*Plus or any other application to connect
to the database? How do you guarantee that they cannot modify data?
The only way to ensure they cannot modify data is through appropriate
privileges at the database level, not the driver level. That way, no
matter how they connect to the database, they cannot modify the data.
Cheers,
Brian
--
===================================================================
Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net
Remove the "nospam." from the email address to email me.
"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown
Received on Fri Sep 08 2006 - 08:16:53 CDT
