Re: Installation of Oracle client for end users

I generally prefer a compromise myself.  Install the client software
locally, but put the tnsnames on the network (read only).  Only give dba's a
local tnsnames.




On Tue, Jul 22, 2008 at 3:55 PM, Jared Still <jkstill@xxxxxxxxx> wrote:

> We only have a few apps that require an oracle client for users, as many
> are application server based (SAP and Agile, and Oracle eBiz)
>
> For those that do require a client, I created an installer to install the
> client
> on the clients using response files for db install and patches.
>
> A network install would be nice, just one of those things I haven't gotten
> to as it isn't really high priority.
>
> Then there are apps that require a particular version of Oracle.
>
> eTrade Equity Edge for example must run on Oracle 9.2.0.6, and the
> client must also be 9.2.0.6.  As the client makes use of exp/imp and
> sqlldr, mixing versions breaks things.
>
> Also of concern is that many folks use laptops and do work away
> from the office.  Loading Oracle clients over the internet can be
> somewhat painful for some slower connections.
>
> Jared
>
>
>
> On Tue, Jul 22, 2008 at 8:45 AM, Jeffrey Beckstrom <JBECKSTROM@xxxxxxxxx>
> wrote:
>
>>  Question, how are you rolling out the Oracle client software for your
>> windows end-users.
>>
>> Are you installing the client software on the local PC and if so how?
>>
>> Are you running the client software from a shared networked drive?
>>
>>
>>
>> Jeffrey Beckstrom
>> Database Administrator
>> Greater Cleveland Regional Transit Authority
>> 1240 W. 6th Street
>> Cleveland, Ohio 44113
>>
>
>
>
> --
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>



-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Other related posts: