(Fwd) Perl Oracle incompatibility

From: Tim Bunce (Tim.Bunce_at_pobox.com)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 22:13:47 +0100
To: dbi-users@perl.org

----- Forwarded message from Rachita <rachita.sachdeva@bhartitelesoft.com> -----

Delivered-To: tim.bunce@pobox.com
X-Pobox-Antispam: Require PTR Record returned DENY: 202.56.229.147 has no PTR record
X-SPF-Guess: pass (seems reasonable for rachita.sachdeva@bhartitelesoft.com to mail through 202.56.229.147)
From: "Rachita" <rachita.sachdeva@bhartitelesoft.com>
To: <tim.bunce@pobox.com>
Subject: Perl Oracle incompatibility
Date: Thu, 28 Oct 2004 22:16:44 +0530
X-ECS-MailScanner: Found to be clean

Hi Tim,

I have been struggling with this for quite some time, going thru various
articles, faqs and mailing lists, but still not able to go thru. So thought
of bugging u ???

I have perl, v5.6.0 built for i386-linux and DBI 1.20 and DBD::ORACLE 1.12
running with Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production.

I have a perl file for generating summary reports by interacting with the
Oracle database. All the database queries work fine till it encounters the
query where a stored procedure is being called. At this poing I get the
following error:

DBD::Oracle::st execute failed: ORA-06502: PL/SQL: numeric or value error:
character string buffer too small
DBD ERROR: OCIStmtExecute
DBD::Oracle::st fetchrow_array failed: ERROR no statement executing (perhaps
you need to call execute first)

It was working fine with oracle 8.1.6 and 8.1.7 I guess some configuration
settings have to be done for my perl to execute the stored procedure written
in oracle.

Thanks in advance. Awaiting ur reply.

Regards,
Rachita

----- End forwarded message -----

Relevant Pages

  • Re: ANNOUNCE: DBD:Oracle 1.18
    ... Well a warning in one compiler is better than and error in an other so I ... This might be a problem more with the older oracle OCI in your client. ... perl -Mblib t/26exe_array.t ...
    (perl.dbi.users)
  • Re: float bug? perl 5.8, DBI and oracle 10.2.0
    ... If you want to store high precision numbers in oracle, you've got 38 decimal digits to play with, and with minimal coaxing perl will handle them as strings at the appropriate points so that the exact values go in and come out. ... I haven't done any numerical work in 10 years or so, but I seem to recall that one can reasonably expect 6 or so decimal significant digits from a 32 bit floating point number - I'll go out on a limb and hazard that one can expect 12 or so digits from a 64 bit floating point number - at any rate I'd be very surprised to get 18 significant digits. ...
    (perl.dbi.users)
  • RE: Memory fault(coredump) with two DBD type connections
    ... I get a core dump ... all the libraries are the same threaded model(single threaded perl uses ... I am running Perl 5.8.8 with DBD-Oracle 1.19 compiled against Oracle ... when I try to connect to the same Oracle database AND same DB2 database ...
    (perl.dbi.users)
  • Re: Is perl better? :(((
    ... >> Wasthe original PERL script hitting an Oracle database? ... >> Did you run an explain plan on your Oracle SQL? ... Java and perl on another. ...
    (comp.lang.java.databases)
  • Re: Is perl better? :(((
    ... >> Wasthe original PERL script hitting an Oracle database? ... >> Did you run an explain plan on your Oracle SQL? ... Java and perl on another. ...
    (comp.lang.java.programmer)