RE: :Oracle PPDs for both 8.0 and 9.2 clients on Windows?
> From: "Jeff Urlwin" <[EMAIL PROTECTED]> > Date: 2005/08/14 Sun PM 07:43:53 CDT > > It may be possible to fudge @INC and put DBD::Oracle on the network, heck > it's probably > easier to put all of perl on the network and fudge the registry to point > there. That > would probably be easier. I run a 20 WinXP node network, and I set up Oracle 8i and 91 on the network for shared access by all users. I also have Perl 5.8.0 (customer requirement) and Perl 5.8.6 set up on the network. The workstations have the Oracle registry settings imported and the Oracle JVMs and program shortcuts copied over (including the Oracle Home Selector), and access to batch files to switch between the Perl environments. Most of the users don't use them, and none of them really understand how it works, but it does So, yes, it is possible to do all this, no problem... :-) Will I share my notes? I haven't been able to get management to agree to OSS contributions, although I think they're close. So, at this point, the answer is no, but hopefully, that will change... > Jeff HTH, amonotod -- `\|||/ amonotod@| sun|perl|windows (@@) charter.net | sysadmin|dba ooO_(_)_Ooo _|_|_|_|_|_|_|_|
RE: :Oracle PPDs for both 8.0 and 9.2 clients on Windows?
> > > Hey all, > > We're (finally!) migrating our Windows XP Oracle clients from > 8.0.5 to 9.2.0.6. While testing some AS Perl v5.6 that uses > DBD::Oracle, we've found that it doesn't work with the 9i > client. It keeps looking for the 8.0.5 or previous OCI DLLs. > Using PPM, we see that DBD::Oracle is v1.12, but the > Oracle.pm that's installed with it says v1.06. We confirmed > this by manually downloading v1.12 from ActiveState's site. > We then upgraded a test box to v1.16 and it works fine with Oracle 9i. > > Tbe problem is that we may not be able to upgrade all Oracle > clients at the same time. One thought is that we'd need a > DBD::Oracle module that can use both an 8.0.5 and 9.2.0.6 > Oracle client. Does this exist? I would try the DBD::Oracle from ftp.esoftmatic.com, and upgrade your perl while you are at it. ActiveState doesn't/didn't support recent DBD::Oracle builds with more recent perls. > > To compound the problem, it's not feasible to install Perl on > all of these, so compiled versions of the Perl programs are > created using Perl2exe and run from a Winders network share. It may be possible to fudge @INC and put DBD::Oracle on the network, heck it's probably easier to put all of perl on the network and fudge the registry to point there. That would probably be easier. Jeff
