Re: Memory corruption with Perl (DBD::Oracle)

  On 22/11/2010 9:07 AM, Thierry Terrier wrote:
> Thanks for your feedback, we're going to install the preconised 
> patchsets on our 11.1.0.6 client.
>
> What about the warning of compilation BDB-Oracle?
> WARNING: Unable to interpret Oracle build commands from 
> /app/oracle/product/11.1.0/client_1/rdbms/demo/demo_rdbms32.mk.
> (Will continue by using fallback approach.)
>
Not sure about that one.

I know that in 11g  they changed the .mk files up a little.  If it 
compiles with the fallback is should still work ok.

You are using a 32 bit client I hope??

Cheers
John Scoles
> Regards.
>
>> Seems this may be an 11g issue and not a perl/DBI/DBD issuse
>>
>> Have you applied all the patches for 11to the 11g DB??
>>
>> Cheers
>> John Scoles
>>
>>> Date: Fri, 19 Nov 2010 18:06:21 +0100
>>> From: [email protected]
>>> To: [email protected]
>>> Subject: Memory corruption with Perl (DBD::Oracle)
>>>
>>> Hi,
>>>
>>> Our (standalone) Perl scripts often encounter memory corruptions 
>>> after a migration on RHEL5.5 (Perl 5.8.8) with Oracle
>>> client 11.1.0 and DBD-Oracle-1.26.
>>> Some Oracle core dumps are present in the Oracle client directory 
>>> ../incident/incdir_... with the generic error code
>>> "oci-24550".
>>>
>>> We had done before a compilation directly on Oracle libraries with 
>>> perl Makefile.PL -l.
>>> After an installation of Oracle Database 11g Examples and a standard 
>>> compilation the problems remain the same.
>>> The service task stops once or twice a day with an error message 
>>> like 'Attempt to free unreferenced scalar'.
>>>
>>> Once, a debug session session showed corruption on an undef array :
>>> main::(script.pl:73): undef @tache;
>>> DB<3>  x @tache
>>> 0 '($@, $!, $^E, $,, $/, $\\, $^W) = @saved;package main; $^D = $^D 
>>> | $DB::db_stop;
>>> @tache;
>>>
>>> ;'
>>> DB<4>  n
>>> Attempt to free unreferenced scalar: SV 0x8b34580, Perl interpreter: 
>>> 0x83b8008 at script.pl line 73.
>>>
>>> The problem doesn't seem to appear with Apache mod_perl.
>>>
>>> Did anyone encounter similar issues or has an idea what is going 
>>> wrong here?
>>> Tell me what complementary information I can provide.
>>