The application is a third-party application using Merant's ODBC
driver.
How do people normally install the client. Do you do an install to
every workstation???
At 11:39 AM 1/6/2004, Jeffrey Beckstrom wrote:
>Rather than
installing the Oracle client on every client PC, we have been:
>-
installing client on 1 PC
>- copying directory to a network
server
>- extract the registry for "oracle" key
>- fix registry
that was extracted to reference the network drive
>- load registry on
client PCs
>- add the network pc as a search drive to the client
pc.
>
>We are now experiencing problems over the WAN and looking
at ways to
>eliminate the Oracle dll overhead. Short of
installing Oracle on every
>client PC, what are our
options?
There is a reason that Oracle doesn't support configurations
like
this. There is a fair amount of "chatter" between an
application and the
Oracle client DLL's. When this chatter starts
flying over the network
rather than merely going to a local DLL, you start
to get performance problems.
How are your application(s)
designed? It's probably possible to tweak an
OCI application to make
fewer OCI calls. If you're using ODBC, and have
the budget, you
could purchase one of the wire-protocol ODBC drivers.
Justin
Cave
Distributed Database Consulting
--
Please see the official
ORACLE-L FAQ:
http://www.orafaq.net--
Author: Justin Cave
INET: jcave@cableone.net
Fat City
Network Services -- 858-538-5051
http://www.fatcity.comSan Diego,
California -- Mailing list and web
hosting
services
---------------------------------------------------------------------
To
REMOVE yourself from this mailing list, send an E-Mail message
to:
ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in
the message
BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing
list you want to be removed from). You may
also send the HELP command
for other information (like subscribing).