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');
$remote_dbh = $c->call_function('DBI::connect',"dbi:Oracle:host=
$host;sid=$sid", $user, $passwd);
##############################################
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 handles from the other.
>
> This is effectively the proxy solution, but you're just forking and
> proxying to a private sub-process you created.
>
> (Full disclosure: I wrote the RMI modules. If they break for you please
> email me.)
>
> Scott
