On Mon, Sep 26, 2005 at 04:03:08PM +0100, Alan Burlison wrote:
> I've poked at this a bit more - if I install the full client it works
> OK, which suggests there is something odd in the way the client shared
> objects are being linked - a full install relinks the .so files but the
> instant client install doesn't.
Isn't the instant client .so separate from the 'full client' .so?
(I've not looked in ages. I need to fire up my old [cough] Solaris
box and refresh it so I can see what's going on for myself. Might not
happen this week though.)
> I'll try dropping the relinked shared
> objects into the instant client tree and see if that makes the problem
> go away.
>
> Tim, has there been any progress on getting DBD::Oracle to work with an
> Instant Client install? How much work do you think it is, I might be
> persuaded to produce a patch ;-)
Some guys at pythian.com are working on it now but it (has been) proving
slow going. There seems to be more progress now. Hopefully they'll be
an updated subversion branch by the end of the week.
Tim.
> --
> Alan Burlison
> --
>
> >>Anyone seen this?
> >>
> >>----------
> >>#!/usr/perl5/bin/perl
> >>use DBI;
> >>my $dbh = DBI->connect('dbi:Oracle:foo', 'bar', 'baz');
> >>$dbh->disconnect();
> >>----------
> >>
> >>Out of memory!
> >>Callback called exit.
> >>END failed--call queue aborted.
> >>
> >>The environment is Solaris 11 on AMD64, using the latest Oracle 32-bit
> >>instantclient and DBD::Oracle 1.16. The script is barfing in
> >>perl_destroy(), i.e. after the disconnect() statement. Before I get the
> >>rubber gloves out, has anyone seen anything similar?
> >
> >Nope.
> >
> >"Callback called exit" is very odd but may just be a symptom of Out of
> >memory ocuring during perl_destroy(). But then that, in itself, is odd.
> >
> >You'll need the gloves on for this one...
> >
> >Tim.
