> >
> > my ($stmt);
> > eval {
> > $stmt=$db->prepare_cached ("update job_queue set
> > status_flag='JDP' where sid= $sid ");
> > $stmt->execute;
> > $stmt->finish;
> > };
>
> This is not necessarily the reason for the core dump, but you
should not
> call finish() here. See perldoc DBI for what finish is
really for.
>
Its just that i am trying to make a habit of explicitly freeing
up resources. From what i understand although the statment
would have been destroyed but its always better to explicitly
finish it.
>
> > if ($@) {
> > $error_string=DBI->errstr;
> > print "Some Error ".DBI->errstr."\n";
> > $statement->finish;
>
> Also here no finish, and not sure where $statement came from
anyways.
>
This piece of code is within a loop and ther is an active
handle called $statement. If i dont finish it explicitly then
PERL complains when i am disconnecting from the database due to
some error being caught. It complains about an active handle
being open.
I looked in the oracle udump directory and found a big trace
file. I have opened up a TAR with Oracle becuase from some
articles on metalink it might be some Oracle Bug that i am
running into.
Thanks
Ali
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
