On Thu, Oct 21, 2004 at 12:56:37AM +0100, Tim Bunce wrote:
> >
> > t/23wide_db_8bit........set $ENV{NLS_LANG}=AMERICAN_AMERICA.WE8MSWIN1252
> > dubious
> > Test returned status 0 (wstat 11, 0xb)
>
> Odd. If the appended patch doesn't fix (or workaround) it please
> try digging deeper.
$ perl -Mblib t/23wide_db_8bit.t
set $ENV{NLS_LANG}=AMERICAN_AMERICA.WE8MSWIN1252
Segmentation fault
It segfaults upon connect in db_handle. Ummm. My fault. I have
a minimalistic ORACLE_HOME with the 9.2 tree and it was missing
ocommon/nls/admin/data/lx200b2.nlb. Sorry about it. The patch to
t/23wide_db_8bit.t is not needed.
> > t/25plsql...............1..83
> > [...]
> > ok 65
> > After p1=[Hello] p2=[Y] p3=[Y]
> > test nvarchar2 arg passing to functions
> > Can't call method "bind_columns" on an undefined value at t/25plsql.t line 319.
>
> Try the appended patch. But please also run "perl -Mblib t/25plsql.t"
> so I can see what the specific error is.
t/25plsql is now clean. The perl -Mblib yields
ok 61
test bind_param_inout of param that's not assigned to in executed statement
Before p1=[Hello] p2=[Y] p3=[Y]
ok 62
ok 63
ok 64
ok 65
After p1=[Hello] p2=[Y] p3=[Y]
test nvarchar2 arg passing to functions
ok 66
ok 67
ok 68
ok 69
ok 70
ok 71
ok 72
ok 73
ok 74
ok 75
ok 76
ok 77
ok 78
ok 79
ok 80
Can't select from function (ORA-06553: PLS-561: character set mismatch on value for
parameter 'ARG2'
ORA-06553: PLS-561: character set mismatch on value for parameter 'ARG' (DBD ERROR:
error possibly near <*> indicator at char 7 in 'SELECT <*>dbd_oracle_nvctest(:p1, :p2)
FROM DUAL'))
test ping
ok 81
The overall result with 9.2 client and 8.0.5 server is
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0,
'blib/lib', 'blib/arch')" t/*.t
t/01base................ok
t/10general.............ok
t/15nls.................ok
t/20select..............ok
t/21nchar............... Database and client versions and character sets:
Database 8.0.5.2.1 CHAR set is EE8ISO8859P2 (Non-Unicode), NCHAR set is EE8ISO8859P2
(Non-Unicode)
Client 9.2.0.0.0 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'
t/21nchar...............ok
t/22nchar_al32utf8......skipped
all skipped: Database NCHAR character set is not Unicode
t/22nchar_utf8..........skipped
all skipped: Database NCHAR character set is not Unicode
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.......skipped
all skipped: Database NCHAR character set is not Unicode
t/25plsql...............ok
t/30long................ok
131/470 skipped: various reasons
t/31lob.................ok
t/40ph_type.............ok
t/50cursor..............ok
t/60reauth..............skipped
all skipped: no reason given
t/70meta................ok
All tests successful, 7 tests and 131 subtests skipped.
Files=18, Tests=1719, 36 wallclock secs ( 6.93 cusr + 0.87 csys = 7.80 CPU)
The overall result with 9.2 client and 10.1.0.2 server is
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0,
'blib/lib', 'blib/arch')" t/*.t
t/01base................ok
t/10general.............ok
t/15nls.................ok
t/20select..............ok
t/21nchar............... Database and client versions and character sets:
Database 10.1.0.2.0 CHAR set is AL32UTF8 (Unicode), NCHAR set is UTF8 (Unicode)
Client 9.2.0.0.0 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'
t/21nchar...............ok
t/22nchar_al32utf8......ok
t/22nchar_utf8..........ok
t/23wide_db.............ok
t/23wide_db_8bit........ok
t/23wide_db_al32utf8....ok
t/24implicit_utf8.......ok
t/25plsql...............ok
t/30long................ok
122/470 skipped: various reasons
t/31lob.................ok
t/40ph_type.............ok
t/50cursor..............ok
t/60reauth..............skipped
all skipped: no reason given
t/70meta................ok
All tests successful, 1 test and 122 subtests skipped.
Files=18, Tests=1020, 40 wallclock secs ( 8.27 cusr + 1.00 csys = 9.27 CPU)
and the same result for 10.1.0.2 client and 10.1.0.2 server,
except for the
t/40ph_type.............ok 11/19 Placeholder behaviour for ora_type=1 (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.
info which is not odd, provided it is 10g.
Once more, sorry about the bogus bug report about t/23wide_db_8bit.
Yours,
--
------------------------------------------------------------------------
Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/
.project: Perl, mod_perl, DBI, Oracle, large Web systems, XML/XSL, ...
Only self-confident people can be simple.
