Ok that tells me somethings
Looks like 90% of you DBD::Oracle is ok but
> Date: Mon, 13 Sep 2010 12:11:09 -0500
> Subject: Re: segfault in Oracle libraries when SIGINT received
> From: pc88m...@gmail.com
> To: byter...@hotmail.com
> CC: dbi-users@perl.org
>
> On Fri, Sep 10, 2010 at 12:25 PM, John Scoles <byter...@hotmail.com> wrote:
> >
> > Can you run the test suite of DBD::Oracle and see what you get?
>
> Here's the output of make test for DBD::Oracle 1.23. Let me know if
> there is anything else I can do to help track down this problem.
>
> t/01base................# Test loading DBI, DBD::Oracle and version
> t/01base................ok
> t/10general.............ok
> 2/31 skipped: various reasons
> t/12impdata.............ok
> t/14threads.............skipped
> all skipped: this linux perl 5.008009 not configured to support iThreads
> t/15nls.................ok
> t/20select..............ok
> t/21nchar...............ok
> t/22nchar_al32utf8......ok
> t/22nchar_utf8..........ok
> t/23wide_db.............skipped
> all skipped: Database character set is not Unicode
> t/23wide_db_8bit........skipped
> all skipped: Database character set is not Unicode
> t/23wide_db_al32utf8....skipped
> all skipped: Database character set is not Unicode
> t/24implicit_utf8.......ok
> t/25plsql...............ok
> t/26exe_array...........NOK 11/17
> t/26exe_array...........NOK 14/17
> t/26exe_array...........dubious
> Test returned status 2 (wstat 512, 0x200)
this means there is something awry with the execute_array function
It should pass all of these tests.
This could be casued by a bug in Oracle and you might hit it if DBIx is using
the execute_array from DBI
What version of Oracle are you using and is it Patch set up to date?
> DIED. FAILED tests 11, 14
> Failed 2/17 tests, 88.24% okay
> t/28array_bind..........ok
> t/30long................ok
> 122/479 skipped: various reasons
> t/31lob.................ok
> t/31lob_extended........ok
> t/32xmltype.............ok
> t/34pres_lobs...........ok
> t/40ph_type.............ok 1/19 Placeholder behaviour for ora_type=1
> VARCHAR2 (the default) varies with Oracle version.
> Oracle 7 didn't strip trailing spaces, Oracle 8 did, until 9.2.x
> Your system doesn't. If that seems odd, let us know.
> t/40ph_type.............ok
> t/50cursor..............ok
> t/51scroll..............ok
> t/55nested..............ok
> t/56embbeded............ok
> t/58object..............ok
> t/60reauth..............skipped
> all skipped: ORACLE_USERID_2 not defined.
> t/70meta................ok
> t/80ora_charset.........NOK 9/14
> t/80ora_charset.........NOK 10/14
>
> t/80ora_charset.........NOK 13/14
> t/80ora_charset.........dubious
This is one I am more concerned about.
It indicates that there is some problem with your NLS settings.
you should get your DBA check your NLS_CHARACTERSET and other like settings as
it looks like your client is using one charset and your DB another or your
Instant client is missing some part for NLS settings which I have also seen
Get the above test to run correctly and then apply any changes you did to the
system that is running your DBIx This is the most likely cause of your greif.
Baiscally there is some UTF8 character that DBI or DBD::Oracle is barfing one
whe trying to insert or read.
Hope this helps
> Test returned status 4 (wstat 1024, 0x400)
> DIED. FAILED tests 9-10, 13-14
> Failed 4/14 tests, 71.43% okay
> Failed Test Stat Wstat Total Fail List of Failed
> -------------------------------------------------------------------------------
> t/26exe_array.t 2 512 17 2 11 14
> t/80ora_charset.t 4 1024 14 4 9-10 13-14
> 5 tests and 124 subtests skipped.
> Failed 2/30 test scripts. 6/2108 subtests failed.
> Files=30, Tests=2108, 48 wallclock secs ( 4.60 cusr + 0.88 csys = 5.48 CPU)
> Failed 2/30 test programs. 6/2108 subtests failed.
> make: *** [test_dynamic] Error 4
Hope this helps
