Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Memory fault(coredump) with two DBD type connections

44 views
Skip to first unread message

Paula J Capacio

unread,
Sep 12, 2008, 4:30:56 PM9/12/08
to dbi-...@perl.org
Hello,
I am running Perl 5.8.8 with DBD-Oracle 1.19 compiled against Oracle
10.2 libs and DBD-DB2 1.0 compiled against DB2 8.1 libs. I can
successfully connect to Oracle databases via a Perl script. Similarly I
can successfully connect to DB2 databases via a Perl script. However,
when I try to connect to the same Oracle database AND same DB2 database
in a script, I get a Memory fault coredump. The core dump occurs when
attempting the second connection; it makes no difference which database
type I connect to first. Any ideas?

The output from perl -V follows.
Thanks in advance for any assistance.
Paula

--- perl -V ----
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=hpux, osvers=11.00, archname=PA-RISC1.1-thread-multi
uname='hp-ux bertha b.11.00 u 9000800 136901587 unlimited-user
license '
config_args='-ders -Dcc=cc -Dusethreads -Duseithreads -Ud_sigsetjmp
-Uinstallusrbinperl -Ulocincpth= -Uloclibpth= -Dd_attribut=undef
-Dd_attribute_warn_unused_result=undef -Dd_u32align=define
-Aprepend:libswanted=cl
-Dvendorprefix=/opt/perl_32 -Darchname=PA-RISC1.1
-Doptimize=-fast +Onolimit +Opromote_indirect_calls +DAportable
+DS2.0
-Accflags=+Z -Accflags=-DUSE_SITECUSTOMIZE -Duselargefiles
-Accflags=-DNO_HASH_SEED -Dinc_version_list=5.8.7/$archname 5.8.7
5.8.6/
$archname 5.8.6 5.8.4/$archname 5.8.4 5.8.3/$archname 5.8.3 5.8.2/
$archname 5.8.2 5.8.1/$archname 5.8.1 5.8.0/$archname 5.8.0
-Dconfig_heavy=Config_static.pl -Dprefix=/opt/perl_32
-Dcf_by=ActiveState -Dcf_email=sup...@ActiveState.com'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef
useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags =' -D_POSIX_C_SOURCE=199506L -D_REENTRANT -Ae
-D_HPUX_SOURCE
-Wl,+vnocompatwarnings +Z -DUSE_SITECUSTOMIZE -DNO_HASH_SEED
-D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 ',
optimize='-fast +Onolimit +Opromote_indirect_calls +DAportable
+DS2.0',
cppflags='-Aa -D__STDC_EXT__ -D_HPUX_SOURCE
-D_POSIX_C_SOURCE=199506L -D_REENTRANT
-D_HPUX_SOURCE -Wl,+vnocompatwarnings +Z -DUSE_SITECUSTOMIZE
-DNO_HASH_SEED'
ccversion='B.11.X.32509-32512.GP', gccversion='', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='/usr/bin/ld', ldflags =''
libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib
libs=-lcl -lcres -lnsl -lnm -lndbm -lmalloc -ldld -lm -lcrypt -lsec
-lpthread -lc
perllibs=-lcl -lcres -lnsl -lnm -lmalloc -ldld -lm -lcrypt -lsec
-lpthread -lc
libc=/lib/libc.sl, so=sl, useshrplib=false, libperl=libperl.a
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_hpux.xs, dlext=sl, d_dlsymun=undef, ccdlflags='-Wl,-E
-Wl,-B,deferred '
cccdlflags='+Z', lddlflags='-b +vnocompatwarnings'

Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT
PERL_MALLOC_WRAP USE_ITHREADS USE_LARGE_FILES
USE_PERLIO USE_REENTRANT_API USE_SITECUSTOMIZE
Locally applied patches:
ActivePerl Build 817 [257965]
Iin_load_module moved for compatibility with build 806
Avoid signal flag SA_RESTART for older versions of HP-UX
PerlEx support in CGI::Carp
Less verbose ExtUtils::Install and Pod::Find
Patch for CAN-2005-0448 from Debian with modifications
Partly reverted 24733 to preserve binary compatibilty
27528 win32_pclose() error exit doesn't unlock mutex
27527 win32_async_check() can loop indefinitely
27515 ignore directories when searching @INC
27359 Fix -d:Foo=bar syntax
27210 Fix quote typo in c2ph
27203 Allow compiling swigged C++ code
27200 Make stat() on Windows handle trailing slashes correctly
27194 Get perl_fini() running on HP-UX again
27133 Initialise lastparen in the regexp structure
27034 Avoid "Prototype mismatch" warnings with autouse
26970 Make Passive mode the default for Net::FTP
26921 Avoid getprotobyname/number calls in IO::Socket::INET
26897,26903 Make common IPPROTO_* constants always available
26670 Make '-s' on the shebang line parse -foo=bar switches
26379 Fix alarm() for Windows 2003
26087 Storable 0.1 compatibility
25861 IO::File performace issue
25084 long groups entry could cause memory exhaustion
24699 ICMP_UNREACHABLE handling in Net::Ping
Built under hpux
Compiled at Mar 20 2006 19:44:08
@INC:
/opt/perl_32/lib/5.8.8/PA-RISC1.1-thread-multi
/opt/perl_32/lib/5.8.8
/opt/perl_32/lib/site_perl/5.8.8/PA-RISC1.1-thread-multi
/opt/perl_32/lib/site_perl/5.8.8
/opt/perl_32/lib/site_perl
/opt/perl_32/lib/vendor_perl/5.8.8/PA-RISC1.1-thread-multi
/opt/perl_32/lib/vendor_perl/5.8.8
/opt/perl_32/lib/vendor_perl
.
---END---

Paula J Capacio

unread,
Sep 15, 2008, 10:36:34 AM9/15/08
to Martin Gainty, dbi-...@perl.org
Martin,
Thanks for the suggestion, I'm just not sure how to follow through on
it.
Based on the output from perl -V, I am running 32-bit in a
multi-threaded mode. I ran chatr commands on Oracle.sl and DB2.sl
files; both outputs show 32-bit. I don't know how to check the
threading. Is that somewhere here in the chatr output or are there
specific commands I can issue?
Thanks in advance,
Paula
---chatr output
chatr
/opt/perl_32/lib/site_perl/5.8.8/PA-RISC1.1-thread-multi/auto/DBD/Oracle
/Oracle.sl
/opt/perl_32/lib/site_perl/5.8.8/PA-RISC1.1-thread-multi/auto/DBD/Oracle
/Oracle.sl:
shared library
shared library dynamic path search:
SHLIB_PATH disabled second
embedded path enabled first
/usr/oracle/client/10.2/lib32:/usr/oracle/client/10.2/rdbms/lib32
shared library list:
dynamic /usr/oracle/client/10.2/lib32//libclntsh.sl.10.1
dynamic /usr/lib/libm.2
shared vtable support disabled
explicit unloading enabled
static branch prediction disabled
executable from stack: D (default)
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
third quadrant private data space disabled
fourth quadrant private data space disabled
third quadrant global data space disabled
data page size: D (default)
instruction page size: D (default)
nulptr references disabled
shared library private mapping disabled

chatr
/opt/perl_32/lib/site_perl/5.8.8/PA-RISC1.1-thread-multi/auto/DBD/DB2/DB
2.sl
/opt/perl_32/lib/site_perl/5.8.8/PA-RISC1.1-thread-multi/auto/DBD/DB2/DB
2.sl:
shared library
shared library dynamic path search:
SHLIB_PATH disabled second
embedded path disabled first Not Defined
shared library list:
dynamic /opt/db2admin/sqllib/lib32/libdb2.sl
dynamic /usr/lib/libcl.2
shared vtable support disabled
explicit unloading enabled
static branch prediction disabled
executable from stack: D (default)
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
third quadrant private data space disabled
fourth quadrant private data space disabled
third quadrant global data space disabled
data page size: D (default)
instruction page size: D (default)
nulptr references disabled
shared library private mapping disabled

---end of output

-----Original Message-----
From: Martin Gainty [mailto:mga...@hotmail.com]
Sent: Friday, September 12, 2008 8:59 PM
To: Capacio, Paula J; dbi-...@perl.org
Subject: RE: Memory fault(coredump) with two DBD type connections


check
all the libraries are the same bit model (e.g. use 32Bit perl with 32
bit libraries)
all the libraries are the same threaded model(single threaded perl uses
single threaded model)
(multi-threaded perl uses multi-threaded model)

?
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission.


> Subject: Memory fault(coredump) with two DBD type connections
> Date: Fri, 12 Sep 2008 15:30:56 -0500
> From: PCAP...@amfam.com
> To: dbi-...@perl.org

See how Windows connects the people, information, and fun that are part
of your life. See Now

Richard T Malafa

unread,
Sep 23, 2008, 9:25:40 AM9/23/08
to dbi-...@perl.org
Greeting,

Has anyone been successful installing DBD-SQLAnywhere-1.16 on a HP-UX
machine???

Thank You
Rich

Martin Evans

unread,
Sep 23, 2008, 9:52:17 AM9/23/08
to dbi-...@perl.org

According to

http://www.cpantesters.org/show/DBD-SQLAnywhere.html#DBD-SQLAnywhere-1.16

no one has reported a result on HP-UX and in fact all are failures.
However this may just be because it says "Please set the SQLANYxx
environment variable (where xx is version number)" and most of the tests
were automated ones.

Have not tried it myself.

Your posting implies you might be having problems installing - if so
what were they.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

Richard T Malafa

unread,
Sep 23, 2008, 11:09:35 AM9/23/08
to Martin Evans, dbi-...@perl.org, Mark...@sybase.com, bruce....@sybase.com, smir...@sybase.com

Hi Martin,
That is very interesting information.   I see all linux but no HPUX or SUN machines in that list.  Using HP UX 11i V2 on this test machine.

I didn't have any problems with the environment variables.   As a matter of fact I've installed the sqlanywhere version 10.  
 Before you can bring up the server version using "dbsrv10"  (don't use dbeng10 - that is for a personal DB and it won't propagate to another machine in your network)  You have to install the environment variables by sourcing it either "sa_config.sh" or "sa_config.csh".    That will take care of all the environment variables for you.  

Then bring up the server with "dbsrv10 -n demo10 /opt/sqlanywhere10/demo.db -ud".   The server is brought up for sanity testing..
 
You can run dblocate to check this.
root@wsmisdb2> dblocate
SQL Anywhere Server Enumeration Utility Version 10.0.1.3419
Server Name             Address
-----------             -------
demo10                  wsmisdb2.cscproj.local:2638  this is the one we just brought up
sqldbserver             mars1.cscproj.local:2638 different sql server - not sybase
 
You then can get  through "perl Makefile.PL" and "make".     There is a notice about some missing debug code in make but no errors generated.  

The show stopper is in "make test".   In the "t" subdirectory you have to change every instance at the top of the location of perl if you're not using their location.
That's minor.  

The killer is in trying to connect to the database, It just hangs there.    You can use the  "dbisqlc" command line utility to check that the connect is working and use select statements.

I haven't been able to figure out yet why it hangs at the connect test  in "make test" yet.

How did you get that ""Please set the SQLANYxx environment variable (where xx is version number)" and most of the tests
were automated ones." message????  Right after running "make test"???  Did you run
"sa_config.sh" or "sa_config.csh" first???

Thanks
Rich







This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.



Martin Evans <martin...@easysoft.com>

09/23/2008 09:52 AM

To
dbi-...@perl.org
cc
Subject
Re: DBD-SQLAnywhere-1.16


Martin Evans

unread,
Sep 23, 2008, 11:31:21 AM9/23/08
to dbi-...@perl.org

I didn't get "Please set the SQLANYxx environment variable (where xx is
version number)" as a message. I just saw that for those people who had
reported a test failure to cpan-testers they nearly all got it - see
http://www.cpantesters.org/show/DBD-SQLAnywhere.html#DBD-SQLAnywhere-1.16
and click on a few failures. I don't have DBD::SQLAnywhere installed at
all - I only thought a) there may be some failures in the test results
that you'd find useful and b) you didn't actually tell us what did not
work. Beyond, that I do use Adaptive Server Anywhere.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

> *Martin Evans <martin...@easysoft.com>*

0 new messages