Mary, there is no such thing as sql_execute. It sounds like a name of subroutine. Can you browse through your code and see whether you have something like "sub sql_execute {"? there? If not, look at the beginning and see what "use PkgName" or "request PkgName" commands do you have. That sql_execute thing should be structured something like this: sub sql_exec { my ($user,$pass,$db,$SQL,$p1,$p2,$p3)=@_; use DBI; my $dbh=DBI->connect("dbi:oracle:$db", $user,$pass); my $sth=$dbh->prepare($SQL); $sth->execute; return(....); } On 02/19/2004 11:04:36 AM, Mary Bahrami wrote: > I've had a problem with a high number of open cursors that I think is > = > caused by a daily perl job that parses and loads a large file (I > don't > = > know perl). There are 'sql_execute' statements that fire > conditionally > = > for insert, update, delete. It appears to fire a sql_execute once > per > = > line of the input file. Is a cursor opened once for each > sql_execute? > = > And is there a better way to do this? > > Thanks, > Mary > > ---------------------------------------------------------------- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > ---------------------------------------------------------------- > To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx > put 'unsubscribe' in the subject line. > -- > Archives are at //www.freelists.org/archives/oracle-l/ > FAQ is at //www.freelists.org/help/fom-serve/cache/1.html > ----------------------------------------------------------------- > ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------