What (if any) hardware changes have happened? If you've moved to a machine
with lots more RAM a memory intensive program that was paging and swapping
could all of a sudden keep more data in memory and become more CPU
intensive. That memory could be consumed by either Perl or Oracle or both.
-- J
I am trying to compile DBD::Oracle version 1.12 on Solaris 2.8 (Sparc). All
goes well until I do 'make test' I then get:
413.fermat-[DBD-Oracle-1.12]: make test
PERL_DL_NONLAZY=1 /bin/perl -Iblib/arch -Iblib/lib -I/usr/local/lib/perl5/5.6.1/
sun4-solaris -I/usr/local/lib/perl5/5.6.1 -e 'use Tes
It appears that a database procedure with a VARCHAR2 OUT parameter can only
return 32512 bytes to a DBD::Oracle script, even if the buffer length is set higher.
I had been expecting a 32767 limit, as that is the largest size a VARCHAR2 can be in
PL/SQL.
Does anyone know the reason for the di
I am not getting blanks chopped off of the end of a CHAR parameter returned
from a proc when I set the attribute ChopBlanks => 1. I've included an example
PL/SQL procedure and perl script that illustrates this:
PROCEDURE test_char_return_values (po_return_code OUT PLS_INTEGER,
