On 01/26/2011 02:27 PM, John Scoles wrote:
On 25/01/2011 8:21 PM, William Ward gmail wrote:
In regards to this thread:
http://www.mail-archive.com/dbi-users@perl.org/msg32115.html
(found via google)
I'm having the same problem at $JOB and before we throw ora_envhp=>0
into our connect attribute,
On Wed, Jan 26, 2011 at 12:27 PM, John Scoles wrote:
>> Or, is there some way to verify the OCI environment and reset it when
>> it is found to be unusable - in other words, trap the
>> "OCIHandleAlloc(OCI_HTYPE_ERROR)" error and reconnect?
>>
>
> Well normally an environment will not die unless y
On 25/01/2011 8:21 PM, William Ward gmail wrote:
In regards to this thread:
http://www.mail-archive.com/dbi-users@perl.org/msg32115.html
(found via google)
I'm having the same problem at $JOB and before we throw ora_envhp=>0
into our connect attribute, we were wondering if this will cause
perfor
On 26/01/11 01:21, William Ward gmail wrote:
> In regards to this thread:
> http://www.mail-archive.com/dbi-users@perl.org/msg32115.html
> (found via google)
>
> I'm having the same problem at $JOB and before we throw ora_envhp=>0
> into our connect attribute, we were wondering if this will cause
