You might be better off posting this to the dbi-users mailing list as other than tux I don't think any of the other DBI/DBD maintainers hang around here much.

That error message comes from Driver_xst.h in DBI which is included in every DBD:

static int
dbdxst_bind_params(SV *sth, imp_sth_t *imp_sth, I32 items, I32 ax)
{
    /* Handle binding supplied values to placeholders.        */
    /* items = one greater than the number of params        */
    /* ax = ax from calling sub, maybe adjusted to match items    */
    dTHX;
    int i;
    SV *idx;
    if (items-1 != DBIc_NUM_PARAMS(imp_sth)
    && DBIc_NUM_PARAMS(imp_sth) != DBIc_NUM_PARAMS_AT_EXECUTE
    ) {
    char errmsg[99];
        /* clear any previous ParamValues before error is generated */
        SV **svp = hv_fetch((HV*)DBIc_MY_H(imp_sth),"ParamValues",11,F
+ALSE);
        if (svp && SvROK(*svp) && SvTYPE(SvRV(*svp)) == SVt_PVHV) {
            HV *hv = (HV*)SvRV(*svp);
            hv_clear(hv);
        }
    sprintf(errmsg,"called with %d bind variables when %d are needed",
        (int)items-1, DBIc_NUM_PARAMS(imp_sth));
        DBIh_SET_ERR_CHAR(sth, (imp_xxh_t*)imp_sth, "-1", -1, errmsg, 
+Nullch, Nullch);
    return 0;
    }

[download]

I don't much like the look of that I32 having 1 subtracted from it and then cast to an int but I cannot see how 3443804 was arrived at right now.

Perhaps the tail end of a DBD::Oracle trace when this happens might help. Run your code again with DBI_TRACE=15=x.log set and exported and show us the tail end of the x.log file.

As I said, you'll probably do better on dbi-users mailing list but they are bound to ask for versions of perl, DBI, DBD::Oracle, Oracle, Oracle client and the log file I suggested you provide.

In reply to Re: DBI Oracle Input Array Binds by mje
in thread DBI Oracle Input Array Binds by hhferreira

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.