""Capacio, Paula J"" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
>From lurking around this mail list over the years,
I've seen numerous items relating to building
DBD-Oracle against a specific version of the Oracle
client software on *nix systems.

Natrue of the beast.  DBD::Oracle uses OIC which is part of the Oracle 
client so you change you client you have to rebuild your DBD::Oracle

Example: if DBD-Oracle was built using version 9,
then the Oracle client is upgraded to 10g;
it is necessary to rebuild DBD-Oracle with the 10g client.

Well you could keep you 9 client and still connect to 10g with it. The DB 
would not care that much. You might miss out on any new features that 10g 
introduced though.

I have used Perl on HP/UNIX, AIX, Linux and Windows.
On the *nix systems, Perl came with the OS and I have
had to install the DBI and DBD-Oracle modules using
the standard make process.  On windows, I used
ActiveState Active Perl and PPM to install DBI and
DBD-Oracle modules.  In the windows environment I
never have to worry about which version of the Oracle
client is present and I can upgrade to a different
client version of Oracle without having to reinstall
the DBD-Oracle module.

Well what happens here is that Active State does the DBD::Oracle compile 
perl for you and you just down load the whole thing, compiled code Oracle 
client and perl code and then it points you perl to it. In this case your 
DDB::Oracle is still using the versioin of the client it was compiled with 
so you might have see some isuese say if you were using bulk inserts with 
the array interface. Lets say a million records,  You may have ActiveState 
DBD:Oracle 1.17 installed this operation would take at least half a hour 
plus. If you recompiled your DBD::Oracle to 1.18 or later this operation may 
only take a few mins.


What trick allows PPM modules to work regardless of
Oracle client versions?  Ultimately, I'd like to know
if there is a way to 'make' the modules on *nix systems
so that they don't rely on a specific version?

We would have to percompile and bundle the binaries with the PPM one PPM for 
each version of the Oracle client. One however runs into problems with 
copyright. Oracle has only given public redistribution permission for the 
10g instantclient binarys not its other client products.

hope this clears a few things up.

Thanks in advance,
Paula 


Reply via email to