topic Re: DBD::Oracle causes core dumps in Operating System - HP-UX

DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 06:07:14 GMT

Hi!

I using Perl 5.6.1, DBI-1.22, DBD::Oracle, Oracle 8.0.0.3 on a HP-UX 11.00 machine.

I got lot of trouble compiling and installing all of them.

Now all compiles well, but testing and using the DBD::Oracle driver ends in core-dumps.

Is this forum correct for my problem?
If so, I can post more details on this problem.

Thanks, Markus

Re: DBD::Oracle causes core dumps

Steve Steel — Fri, 24 May 2002 06:17:52 GMT

Hi

This will do

Please give all info you have.

especially messages

If a corefile is created run
file core

Steve Steel

Re: DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 06:31:09 GMT

Re: DBD::Oracle causes core dumps

Steve Steel — Fri, 24 May 2002 06:40:30 GMT

Hi

look at

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x3e777d4cf554d611abdb0090277a778c,00.html

You will see that SIGSEGV is caused bu maxssiz
or the 64 bit equivalent being too small.

Follow the URL above and tune your system values upwards.

Steve Steel

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Fri, 24 May 2002 06:58:27 GMT

Aside the core dumps, I see some other things you might consider to change or redo

The perl you are using is built with gcc-2.95 for hppa-1.1 architecture (32bit). If you want some performance gain and you do not have HP ANSI C, consider upgrading to gcc-3.0.4 or gcc-3.1 The GNU people have gone through great trouble to improve gcc for HP-UX. gcc-3.0.4 is available for 11.00 on http://hpux.tn.tudelft.nl/hppd/hpux/Gnu/alpha.html (amongst other fine HP mirrors) and you can also find binutils-2.12 there.

DBI-1.22 is very new (only a few days) and the only addition is a bulk interface. DBI-1.21 would have been sufficient.

This perl (32bit) cannot be used with 64bit Oracle, but I guess that is not the problem.

Good luck, and happy perl hacking

Re: DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 07:10:30 GMT

OK,

I checked maxssiz:

Parameter: maxssiz
Value: 0x00800000
Default: 0x00800000
Minimum: -
Module: -

There isn't a maxssiz_64 value, because our system is 32bit only.

From the suggested thread I am not sure what value to set.

Sorry, but I am not too sure with this system.
Any hints are valueable for me...
Markus

Re: DBD::Oracle causes core dumps

Steve Steel — Fri, 24 May 2002 07:26:43 GMT

Hi

There is a document attached to the last part of the url I gave you with good info and indeed the default is too small.

maxssiz maxdsiz maxtsiz are indicators of the maximum memory which can be used.

Would recommend

1)Look at the attached document.

2)Make sure you have at least 1.5*default for these values.

Remember that you must reboot to change but you can use kmtune to upgrade the values online to test

see man kmtune

Steve Steel

Re: DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 07:54:23 GMT

OK,

first of all many thanks for helping.
I will try reconfiguring this machine in the afternoon.

BTW, this is a K360 with 1GB RAM.
The suggestions are based upon N- and V- models.

I wouldn't like to run into troubles, so I am unsure if these suggested values are proper for our system.

I think, I have to change maxssiz to 1.5*default as you said.
Shall I apply this to maxdsiz, too? All values mentioned in this doc to prevent more SIGSEGV core-dumps?

Markus

Re: DBD::Oracle causes core dumps

Steve Steel — Fri, 24 May 2002 08:52:43 GMT

Hi

maxs maxd maxtsiz you can do online with kmtune without stopping the machine.

Make sure you have 2 to 4 times your memory in swapspace.

If dbc_max_pct is on 50 and you have at least 3gb of swap then put dbc_max and dbc_mix on 20
and 5 to free up main memory.

Steve Steel

Re: DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 13:06:29 GMT

OK,

I raised maxssiz to 0x05000000.
I left maxdsiz and maxtsiz untouched at 0x04000000.

My physical RAM is 1GB, swapspace is only 512 (typically half filled). I could rais it to 1.5GB, but I would rather left it so.

Still I get that core-dump.

I will try recompiling everthing with gcc 3.x and binutils 2.11.x unless someone can point me to another problem.

Hopeless, Markus :-((

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Fri, 24 May 2002 13:32:06 GMT

binutils-2.12 please

Re: DBD::Oracle causes core dumps

Markus Bonet — Fri, 24 May 2002 14:15:27 GMT

Ok, ok,

binutils2.12.
But, where can I get it?
On the HPUX Porting page there is currently only 2.11.2 available.
Or do I have to 'make' binutils from the source as well?

Markus
PS: Back on monday, now it's weekend :-))

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Fri, 24 May 2002 14:31:24 GMT

A quick search revealed the same to me, so I guess you'll have to rebuild that too :(

Re: DBD::Oracle causes core dumps

Markus Bonet — Mon, 27 May 2002 12:12:58 GMT

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Mon, 27 May 2002 12:16:23 GMT

Can the core dumps tell you wether it is /Oracle/, /DBD-Oracle/, /DBI/, or /perl/ that's getting confused and dumps core?

Re: DBD::Oracle causes core dumps

Markus Bonet — Mon, 27 May 2002 12:25:36 GMT

This perl-script:

#!/opt/perl5/bin/perl
use DBI;

$dbh=DBI->connect('dbi:Oracle:host=localhost;sid=xlab;port=2629', 'xxxxxx', 'xxxxxx') or die "Unable to connect: $DBI::errstr";
print "Connect!\n";
$sth = $dbh->prepare("select * from tbar_account");
$sth->execute();

while (@row = $sth->fetchrow_array) #### Die Werte in das Array @row schreiben
{
print "@row";
# $SHARENAME = $row[0]; #### Den Pfad in eine Variable schreiben
# $ARR_PFAD_PERM[$ARR_GROESSE_PERM] = $SHARENAME; #### Dann den verM-dnderten Datenstring wieder in ein Array schreiben,
# $ARR_GROESSE_PERM += "1"; #### dieses Array wird in den Subroutinen hold_rights und get_old_rights verwendet.
}
# print @ARR_PFAD_PERM;

causes this core-dump:

perl /www/cgi-bin/1test.pl
Segmentation fault (core dumped)
root@U8POA:/home/bonet/DBD-Oracle-1.12# file core
core: core file from 'perl' - received SIGSEGV

Markus

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Mon, 27 May 2002 15:35:25 GMT

Still don't see what version of Oracle you are using.

ALWAYS:

1. use strict;
2. use warnings;

In this case:

a. use DBI debugging to see where the script realy fails

#!/opt/perl5/bin/perl -w

use strict;

use DBI;

DBI->trace (99);
$dbh=DBI->connect ('dbi:Oracle:host=localhost;sid=xlab;port=2629', 'xxxxxx', 'xxxxxx') or die "Unable to connect: $DBI::errstr";
print "Connect!\n";
$sth = $dbh->prepare ("select * from tbar_account");
$sth->execute ();
while (@row = $sth->fetchrow_array) {
print "@row\n";
}

# gdb /opt/perl5/bin/perl core
:
:
:
gdb > where

????

Re: DBD::Oracle causes core dumps

Markus Bonet — Tue, 28 May 2002 06:55:39 GMT

Re: DBD::Oracle causes core dumps

H.Merijn Brand (procura — Tue, 28 May 2002 09:13:28 GMT

So you,ve got Oracle 8. But which? 8.1.7?

Check the README of Oracle installation guide, it states that there are some HP-UX patches are to be installed (pthread related?)

Check the README.hpux for DBD::Oracle

Check the libpthread lib, and if there are still patches available that you did not install

a5:/usr/lib 102 # what libpthread.sl
libpthread.sl:
mutex.c $Date: 2002/01/02 14:04:08 $Revision: r11ros/4 PATCH_11.00 (PHCO_26000)
libpthread.c $Date: 2002/01/10 10:24:01 $Revision: r11ros/8 PATCH_11.00 (PHCO_26000)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26:27 PDT 2001
a5:/usr/lib 103 # ll libcl*
1890 lrwxr-xr-x 1 root sys 9 Sep 24 2001 libcl.0 -> ./libcl.1
1891 -r-xr-xr-x 1 bin bin 1388160 Jun 22 2001 libcl.1
7129 -r-xr-xr-x 1 bin bin 1253376 Jun 12 2001 libcl.2
4500 -r--r--r-- 1 bin bin 1463012 Jun 12 2001 libcl.a
1893 lrwxr-xr-x 1 root sys 9 Sep 24 2001 libcl.sl -> ./libcl.2
a5:/usr/lib 104 # what libcl.2
libcl.2:
Trap Library version UX.11.01.03(GS IB4) - November 16, 1998
Unwind Library version UX.11.01.05 - 00/08/15
fs_amod.s $Revision: 1.9.1.1 $
libcl.sl version B.11.01.08 - Jun 15, 2001
a5:/usr/lib 105 #

Asign points to the answers

Re: DBD::Oracle causes core dumps

Markus Bonet — Tue, 28 May 2002 10:31:22 GMT

It's Oracle 8.0.0.3 EE.

I looked around for patches. Might this be the needed one?

http://support4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_23792&context=hpux:800:11:00

Markus