Bruce Johnson wrote:

On Jan 5, 2010, at 10:11 AM, John Scoles wrote:

Bruce Johnson wrote:
I've got to update DBD::Oracle on a production machine (from our antique 1.17 version to the current one), in the process I'm changing the Oracle client as well.)

will the proper setting of the environment vars (ORACLE_HOME, LD_LIBRARY_PATH, etc) and running "update DBD::Oracle" via cpan suffice or do I have to go in and rip out the old stuff first...


Short answer yes with a but. Long answer No with a Maybe.

Jumping from 1.17 all the way to 1.23 is quite a leap and may not gain anything from it.

What client are you using with 1.17 and what client do you want to use with 1.23 and what version of Oracle do you want to connect to are the big questions to ask and of course what OS are you working in


I've been stuck with 1.17 and the oracle 8.1.6 client libs because of an odd issue with DBD::Oracle and database links to Oracle's RDB-Oracle gateway. (we've dealt with this off-list a couple of times) The host OS is Linux, and is running an Oracle 11.1 database.

The Oracle RDB stuff is going away (At last! Hoorah!), so I don't need to stick to the 8.1.6 client anymore.

Unless there is some special features of the later DBD::Oracle that you want to take advantage of or you are upgrading to ORACLE 10 or 11 I would just leave it running with 1.17.


The problem I have is that the 8.1.6 version of Oracle client we're using doesn't work with PHP-oracle client so we have to use the Oracle 11.1 client. I figured that getting DBD::Oracle up-to-date would be a good idea as well. At the very least I need to recompile 1.17 with the new client.

Yes you will have to do that. There area few Bugs in 1.23 (mostly when you have more than one clob in a query) you might want to go with 1.22, or if you can wait a little while 1.24 which should come out in the next few days and that one will be much faster than other versions for fetching.


The above aside update DBD::Oracle might work if you set the ORACLE_HOME, LD_LIBRARY_PATH, correctly have the same C compiler that built your perl.

Good that's what I hoped, which will make this a pretty simple upgrade.

cheers

Reply via email to