Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

Try RMI::Client::ForkedPipes. Have the child process use one lib, and the parent use the other. The child can give back with one DBI/DBD, and the parent can produce handles from the other. This is effectively the proxy solution, but you're just forking and proxying to a private sub-process y

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

Scott, Would something like this be close: ## $c = RMI::Client::ForkedPipes->new(); $c->call_use_lib($ENV{MY_PERL_INSTALL}.'/some/path/to/other/Oracle_module'); # A build of Oracle DBD using oracle 8 client not normally in @INC $c->call_use('DBI')

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

Just reading about RMI - sounds promising :-) Thanks you very much. On Mon, 2009-12-14 at 20:09 -0600, Scott Smith wrote: > Try RMI::Client::ForkedPipes. Have the child process use one lib, and > the parent use the other. The child can give back with one DBI/DBD, and > the parent can produce h

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

On 2009-12-14 07:18:41 -0500, jeff wrote: > I need to connect simultaneously to both Oracle 8 and oracle 10 from the > same script using 'external' connection (ie, no username or password). > The Oracle libraries, from my experimentations, are not compatible for > external connections. Oracle 8 us

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

You make an incorrect assumption :-( Not trying to fool anyone or hide my identity, just hoping for further input. If you don't want to answer, then don't - but there is no need to be nasty about it. You shouldn't view people so negatively. As it turns out, the proxyserver is not a solution an

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

OK, while you were busy creating new threads, I remembered that this problem was discussed some time ago on this mailing list. I was about to mail you a link to that discussion for further information, like , but then I saw that th

RE: Looking for clever solution: Different versions of Oracle .so files within single Perl build

Have you considered using database links? Instead of 2 connections, you could just do everything thru oracle 10. -Original Message- From: jeff [mailto:j...@roqc.no] Sent: Monday, December 14, 2009 5:19 AM To: dbi-users@perl.org Subject: Looking for clever solution: Different versions o

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

External connect ( no username or password needed ) ? What I've tried so far: I built against Oracle 8 client and external connection ( based on system id ) works only for oracle 8 - oracle 10 uses a wallet. Then I built against oracle 10 - worked with wallet (external connection) but not an ex

Re: Looking for clever solution: Different versions of Oracle .so files within single Perl build

You need only one client version to connect to both 8 and 10, preferably the newer 10 client. It shuld work in 99.9% of all cases. If that doesn't work, try 8. If that still does not work, try 9. Alexander On 14.12.2009 13:18, jeff wrote: I need to connect simultaneously to both Oracle 8 and