AFAIK, DBD::Oracle does not support binding record types.  You could either write a PL/SQL wrapper routine that takes individual varchar2 values (instead of the record) and assembles them into the record before calling the actual procedure.  Or maybe use an intermediary table — see Returning a Recordset for the general outline of the idea. Of course, this describes a somewhat different situation (output parameter, etc.), but it should in principle be adaptable...

Personally, I usually use XML data structures (as CLOBs) to pass complex data between Perl and Oracle, as XML support is pretty good on both sides.

If you can't modify the PL/SQL side, though, you're out of luck, I think.


In reply to Re: Calling PL/SQL procedure with input as Record Type by Eliya
in thread Calling PL/SQL procedure with input as Record Type by ssathak

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.