------=_Part_5764_27216683.1189525437333
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
when building the module, you have to specify the ORACLE_HOME
what happens if you have multiple versions of Oracle? How is that handled?
------=_Part_5764_27216683.1189525437333--
The build is not against a Oracle instance per say.
It is a built against an Oracle Client. So it works the same way SQLPlus or
any other SQL GUI Client.
So you can connect to any number of different versions of an Oracle DB. You
may run into problems with Client X and DB Y but that would be more an
Oracle bug than anything else.
Hope this helps
John Scoles
----- Original Message -----
From: "Richard Labutis"
To:
Sent: Tuesday, September 11, 2007 11:43 AM
Subject: DBI with different versions of Oracle
> when building the module, you have to specify the ORACLE_HOME
>
> what happens if you have multiple versions of Oracle? How is that handled?
>
Looking at this again. If you have mulitple ORACLE_HOMEs in you path it is
anyones guess as to which client your DBD::Oracle with compile against. In
Lunix I have see the last one on the list be the one. Your best bet would be
to change the ORACLE_HOME to the client you want to compile against for the
compile and install. After that it should work no mater how many
ORACLE_HOMEs you have set as long as the one you compiled against is there
as well
cheers
----- Original Message -----
From: "Richard Labutis"
To:
Sent: Tuesday, September 11, 2007 11:43 AM
Subject: DBI with different versions of Oracle
> when building the module, you have to specify the ORACLE_HOME
>
> what happens if you have multiple versions of Oracle? How is that handled?
>
------=_NextPart_000_0098_01C7F47C.678A56F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
What would happen in this case it would use the client from 9.2.0.6 not =
the DB. =20
You most likely do not have an TNS entry for your 10g database in your =
9.2.0.6 TNSNAMES.ORA file. =20
So it is more of a connection problem than a DBD::Oracle problem. Now =
if you happend to have your 9 and 10 DBs named the same you will get =
into problems again a Oracle issue not a DBD::Oracle.=20
In actual terms there is little (if any) difference between the OCI =
(Oracle Call Interface is what DBD::Oracle uses under all that Perl =
code) found in a Oracle 9 client and a Oracle 10g client. So there sould =
be no real issues with DBD::Oralce an connecting to different versions =
of Oracle.
Cheers
----- Original Message -----=20
From: Richard Labutis=20
To: John Scoles=20
Sent: Tuesday, September 11, 2007 1:41 PM
Subject: Re: DBI with different versions of Oracle
I have found in the previous version, if ORACLE_HOME is 9.2.0.6 when =
you originally compiled the module and you decide to use oracle 10g, the =
module will try to use use the oracle version that has been set when the =
module was built.=20
this is what I am trying to resolve.
I just don't know how all this handled.
On 9/11/07, John Scoles < scoles@pythian.com> wrote:
Looking at this again. If you have mulitple ORACLE_HOMEs in you path =
it is=20
anyones guess as to which client your DBD::Oracle with compile =
against. In
Lunix I have see the last one on the list be the one. Your best bet =
would be
to change the ORACLE_HOME to the client you want to compile against =
for the=20
compile and install. After that it should work no mater how many
ORACLE_HOMEs you have set as long as the one you compiled against is =
there
as well
cheers
----- Original Message -----
From: "Richard Labutis" < rlabutis@gmail.com>
To:
Sent: Tuesday, September 11, 2007 11:43 AM
Subject: DBI with different versions of Oracle=20
> when building the module, you have to specify the ORACLE_HOME
>
> what happens if you have multiple versions of Oracle? How is that =
handled?
>
------=_NextPart_000_0098_01C7F47C.678A56F0--