Up Prev Next
From: Michael Peppler <mpeppler at peppler dot org>
Subject: Re: after 5000 dbe deletes, internal directory control layer
error - why?
Date: Mar 30 2001 4:22PM
Roleigh Martin writes:
> My top-notch DBI perl programmer read your reply and he surmises that he
> needs to do a bind each fetchrow rather than either (a) a do() or a (b)
> (prepare/execute/finish) each fetchrow loop. He guesses that the finish
> command must not be cleaning up all stuff. He doesn't see where he is
> accidentally opening another connection each cycle however.
Have your programmer contact me directly - I suspect a problem with
the code, but as I haven't seen any of it it's hard to tell.
> Last, we've had problems using the CT-Lib Sybase 12.x libraries -- and so we're
> stuck using the CT-Lib Sybase 11.x libraries with our current versions of
> stuff. The databases we're going against are Sybase 12.x version. Is this
> the norm for the versions we're using?
The CT-lib library version is unlikely to be the issue here.
> At 12:38 PM 3/29/2001, you wrote:
> >Roleigh Martin writes:
> > > We have a DBI perl program that after about 5,000 deletes we get this
> > > error message -- something similar happened with another program that did
> > > about 5,000 updates. The update program worked around the problem by
> > > removing use of the second database handle. The program logic basically
> > > has a parent SQL select command that uses one database handle to get a
> > > list of unique index keys of records to update, then inside a while
> > fetchrow
> > > next record loop, it does the update or delete for only one database
> > record
> > > at a time to minimize database locking.
> >I answered this on the other list where you posted - did you not see
> >that message?
Michael Peppler - Data Migrations Inc. - firstname.lastname@example.org
http://www.mbay.net/~mpeppler - email@example.com
International Sybase User Group - http://www.isug.com
Sybase on Linux mailing list: firstname.lastname@example.org