There is a problem with that file.  It looks like it's compressed twice.

John

-----Original Message-----
From: John Scoles [mailto:sco...@pythian.com] 
Sent: Friday, February 05, 2010 10:07 AM
To: Carlson, John W.
Cc: Matthew Maglinte; dbi-users@perl.org; tim.bu...@pobox.com
Subject: Re: dbd::oracle behavior

I would say use 1.24 or the trunk version

http://*theoryx5.uwinnipeg.ca/pub/CPAN/authors/id/P/PY/PYTHIAN/DBD-Oracle-1.24.tar.gz

there may be a problem with that file so you might want to try here as well

http://*svn.perl.org/modules/dbd-oracle/trunk


There is some new majik in 1.24 that will speed up any queries you do by 
a few orders of magnitude ;).

cheers
John Scoles
> I was using DBD::Oracle 1.20 in development, and DBD::Oracle 1.21 in 
> integration, test and production.  So far we have only deployed DBD::Oracle 
> to development.  Would you recommend to install something else for 
> integration, test and production?
>
> We had DBI 1.602 in development, and we were having trouble installing 
> DBD::Oracle 1.23, so we upgraded to DBI 1.609 and that seemed to fix the 
> problem.
>
> What DBI and DBD::Oracle do you recommend for production use?
>
> John
>
> -----Original Message-----
> From: John Scoles [mailto:sco...@pythian.com] 
> Sent: Friday, February 05, 2010 9:52 AM
> To: Carlson, John W.
> Cc: Matthew Maglinte; dbi-users@perl.org; tim.bu...@pobox.com
> Subject: Re: dbd::oracle behavior
>
> should be no problem then what was the original version of DBD:Oracle 
> and DBI where you using??
>   
>> So far, I am read only!
>>
>> Thanks,
>>
>> John
>>
>> -----Original Message-----
>> From: John Scoles [mailto:sco...@pythian.com] 
>> Sent: Friday, February 05, 2010 9:31 AM
>> To: Carlson, John W.
>> Cc: Matthew Maglinte; dbi-users@perl.org; tim.bu...@pobox.com
>> Subject: Re: dbd::oracle behavior
>>
>> The bug in 1.23 will hit you if you try to an insert more than one CLOB 
>> at a time.
>> If you are not inserting CLOBs then do not worry about it.
>>
>> Cheers
>> John Scoles
>>
>>
>> Carlson, John W. wrote:
>>   
>>     
>>> Uh.  I just installed DBD::Oracle 1.23 with a patch.  Should I install 
>>> DBD::Oracle 1.22 instead?  What I the nature of the bug?
>>> I am fairly new to the dbi-users group, and I haven't been watching the 
>>> emails.
>>>
>>> John
>>>
>>> -----Original Message-----
>>> From: John Scoles [mailto:sco...@pythian.com] 
>>> Sent: Friday, February 05, 2010 5:07 AM
>>> To: Matthew Maglinte
>>> Cc: dbi-users@perl.org; tim.bu...@pobox.com
>>> Subject: Re: dbd::oracle behavior
>>>
>>> Hard to say what is going on here but me things you are running into the 
>>> 'ping' problem
>>>
>>> Are you using Apache::DBI??
>>>
>>> Many of these warehouse applictions reuse the same connection handel and 
>>> to keep them alive they use $dbh->ping which runs a query to maintain 
>>> the connection.
>>>
>>> What version of DBD::Oracle are you using?
>>>
>>> If you can upgrade to DBD::Oracle 1.22 (do not use 1.23 there is a bug 
>>> in there that might be worse) or get the latest 1.24 version
>>>
>>> that might solve your problem
>>>
>>> cheers
>>> John Scoles
>>>
>>>
>>>
>>>
>>>
>>>
>>> Matthew Maglinte wrote:
>>>   
>>>     
>>>       
>>>> I'm a dba supporting a  warehouse database (production environment) 
>>>> accessed via a custom application built on open source components, one of 
>>>> which is dbd::oracle.
>>>>
>>>> Performance monitoring shows two queries continually consuming 
>>>> considerable resources (cpu waits) - the query text resembling for the 
>>>> most part 'column_info' and 'table_info'.  Over any given day, the 
>>>> column_info select is executed +260 times an hour,  'table_info'  executed 
>>>> +360 times an hour.
>>>>
>>>> Is this level of frequency intended?  And are these calls appropriate 
>>>> (expected) for a static data dictionary environment?
>>>>
>>>> Any response that would help my understanding would be appreciated. 
>>>> Thanks.
>>>>
>>>> Matt Maglinte
>>>> DBA - PeMS/LCS
>>>> Department of Transportation
>>>> W:(916)445-0090
>>>> matthew_magli...@dot.ca.gov
>>>>
>>>>   
>>>>     
>>>>       
>>>>         
>>>   
>>>     
>>>       
>>   
>>     
>
>   


Reply via email to