SegFault on unique constraint (DBD::Oracle)
- From: edwinrrivera@xxxxxxxxxxx
- Date: 12 Mar 2007 12:02:33 -0700
Good afternoon,
We are experiencing a problem with DBI, DBD::Oracle.
Whenever we access the Oracle database (10g) via PERL and trigger a
unique constraint error, apache segfaults and the thread that handled
the request hangs. It's severe enough that apache does not even log
the offending request to neither the access_log nor the error_log.
We've been able to replicate the error consistently by isolating it to
whenever we issue a command via DBI that triggers a unique constraint
error.
Is this a known bug or something anyone else here has experienced? We
got around it temporarily by patching oci8.c and commenting out some
code that basically looks like it is responsible for setting DBI-
errstr as far as i can tell.
Basically, commenting out (and a few other lines):
SV *errstr = sv_newmortal();
errcode = oci_error_get(errhp, status, what, errstr, DBIS->debug);
Our setup is:
apache with mod_perl (Server: Apache/1.3.28 (Unix) mod_perl/1.26)
DBI v1.35
DBD::Oracle v1.16
PERL 5.6.2
Oracle 10g
FC3
Any assistance/pointers you can provide would be greatly appreciated.
As you can imagine, at this point, we can no longer even retrieve DBI-
errstr, even on simple prepare/execute statements because of ourpatch.
Thanks in advance!
.
- Prev by Date: 24implicit_utf8.t fails when compiling DBD-Oracle-1.19 ( 'Rearing it's ugly head again')
- Next by Date: Failed Insert: SQL syntax error
- Previous by thread: 24implicit_utf8.t fails when compiling DBD-Oracle-1.19 ( 'Rearing it's ugly head again')
- Next by thread: Failed Insert: SQL syntax error
- Index(es):