DBI dies on exit

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?

Thanks,

--
Alan Burlison
--

Re: DBI dies on exit

On Wed, Aug 31, 2005 at 06:39:21PM +0100, Alan Burlison wrote:
> 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.

Re: DBI dies on exit

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. 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 ;-)

--
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.

Re: DBI dies on exit

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.

Re: DBI dies on exit

I build DBD::Oracle with instantclient on linux with no particular problems
after following one of the recipies that I found googling for it.

On the other hand I couldn't get this to work on HP-UX, always getting the
OCIClientInitialize error, no matter which combinations of env. variables
and perl configs I tried.

Michael




Extranet
Tim.Bunce@pobox.com - 26/09/2005 21:59

To: Alan.Burlison

cc: Tim.Bunce, dbi-users


Subject: Re: DBI dies on exit


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.




This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.

---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.

Re: DBI dies on exit

Tim Bunce 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?

The instanc client .so's seem to be mostly a subset of the full client
install ones:

Full client:
libagtsh.so libhasgen10.so libocci.so.10.1 libskgxp10.so
libclntsh.so libheteroxa10.so libocijdbc10.so libskgxpd.so
libclntsh.so.10.1 libjmisc.so libocr10.so libskgxpu.so
libcorejava.so libldapjclnt10.so libocrb10.so libsqlplus.so
libcoresh10.so libnjni10.so libocrutl10.so libuini10.so
libdbcfg10.so libnnz10.so libOsUtils.so libxdb.so
libemmas10.so libocci.so libskgxn2.so

Instant client:
libclntsh.so libheteroxa10.so libocci.so.10.1 libocijdbc10.so
libclntsh.so.10.1 libnnz10.so libociei.so libsqlplus.so

libociei.so seems to be the only difference.

> 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.

Where can I grab it from when it appears?

--
Alan Burlison
--

Re: DBI dies on exit

Alan Burlison wrote:

> The instanc client .so's seem to be mostly a subset of the full client
> install ones:

The only libraries that are pulled in by DBD::Oracle (on Solaris at
least) are libclntsh.so.10.1 and libnnz10.so

--
Alan Burlison
--