Downside to ora_envhp=>0 to fix OCIHandleAlloc(OCI_HTYPE_ERROR) problem
[email protected] (William Ward gmail)
| Newsgroups | perl.dbi.users |
|---|---|
| Message-ID | <[email protected]> |
In regards to this thread: http://www.mail-archive.com/[email protected]/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 performance issues? Is there a downside to ora_envhp that isn't described in the thread? 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? -- Check out my LEGO blog at http://www.brickpile.com/ View my photos at http://flickr.com/photos/billward/ Follow me at http://twitter.com/williamward