Functions in pl/sql only take input arguments

Don't think that's true.  At least, I've been using bind_param_inout() with pl/sql function arguments (like the :l_chime in the OP) in quite a number of cases without any problems...

Just to clarify what I meant. Functions in pl/sql only allow input arguments. You cannot write:

FUNCTION fred (arg1 OUT INTEGER) RETURN integer;
[download]

but you can write

FUNCTION fred (arg1 IN INTEGER) RETURN integer;
[download]

and the IN is implied anyway.

Also, I was not saying bind_param_inout would not work on an input only parameter but it is pointless using it and may require an unnecessary overhead on input only arguments.

You cannot write:
FUNCTION fred (arg1 OUT INTEGER) RETURN integer;

Yes you can... (and if you do use such output parameters, bind_param_inout is the way to bind/access them).

create procedure search(chime in varchar, id out number)
[download]

then i could use bind_param_inout to get at the id? For example:

$id = $plsql->bind_param_inout(":id",\$id,16);<br>
print "$id";<p>
[download]

maybe one cant get at the variable on the left side of :=?

It should work (I've done it many times myself...), so I think the problem lies elsewhere.

You certainly can get function return values back in perl. You can also get output arguments back in procedures. I do this all the time with DBD::Oracle.

use DBI;
use strict;
my $h = DBI->connect('dbi:Oracle:xxx','xxx','xxx');
eval {$h->do(q{drop function fred});};
my $sql = <<'EOT';
create function fred(a integer) return integer as
begin
  return (a + 1);
end;
EOT

$h->do($sql);
my $s = $h->prepare(q{begin ? := fred(?); end;});
$s->bind_param(2, 1);
my $res;
$s->bind_param_inout(1, \$res, 100);
$s->execute;
print "fred=$res\n";
[download]

outputs fred=2