[AccessD] Error 3218 "Couldn't Update; Currently Locked" <<HOW TO TEST?>>

Sad Der accessd666 at yahoo.com
Mon Jan 19 00:27:22 CST 2004


Gustav,

thanx again. However, I'm a 'rent-a-programmer'
(what's the official anglish term?) and this
organisation is completely Oracle minded => SQL-server
is bad, MS sucks and Access...isn't that some sort of
notepad? 

So, I need proof. Is there a correct way to test this?

Sad

--- Gustav Brock <gustav at cactus.dk> wrote:
> Hi Sad
> 
> Those settings are probably to low.
> Try setting them to maximum:
> 
> > These two commands may be set at the console
> screen, they will take
> > effect at once and doesn't require restart of the
> server. If they
> > prove of beneficial, include them in the
> autoexec.ncf file of the
> > server. 
> >
> > SET MAXIMUM RECORD LOCKS = 200000
> > SET MAXIMUM RECORD LOCKS PER CONNECTION = 100000
> >
> > The only drawback is a slightly larger RAM
> allocation which is not
> > significant with today's multimegabyte servers but
> did count in the
> > days of servers running on 8 to 16 MB RAM and
> every 100K was of
> > importance.
> 
> /gustav
> 
> 
> > These are the new settings:
> > Max. Records Lock per Connection: 1000
> > Max. Files Lock per Connection: 5000
> > Max. Records Lock: 40000
> > Max. Files Lock: 400000
> 
> > How can I test these? Ok, for the first one I have
> to
> > lock 999, 1000, 1001 records...question is how do
> I do
> > that?
> 
> > Is importing a file with 999, 1000, 1001 records
> > enough?
> 
> > Any testing tips/links?
> > TIA.
> 
> > SD
> 
> 
> > --- Jim Dettman <jimdettman at earthlink.net> wrote:
> >> <<We use A2K SP1 on a Novell network.
> >> occasionally the users get the following error:
> >> Error 3218 "Couldn't Update; Currently Locked">>
> >> 
> >>   There are lots of things that will cause that
> >> message, but I think you
> >> might be barking up the wrong tree in that it's a
> >> Novell problem.
> >> 
> >>   From your comments abut it being "buggy", I
> would
> >> think more that the app
> >> was poorly written and stepping on it's own toes,
> >> resulting in the above
> >> error.
> >> 
> >>   One way to check that out easily is to copy the
> >> backend to a local drive,
> >> re-link the tables (I'm assuming it's a split
> app),
> >> then test.  If you still
> >> get the error messages it has nothing to do with
> >> Novell.  If the error
> >> disappears, then it's related to locking.
> >> 
> >>   The other test you can do is using the
> SetOption
> >> method of the dbEngine
> >> object, set dbMaxLocksPerFile to a number less
> then
> >> the allowed number of
> >> locks under Novell.  This will ensure that JET
> never
> >> uses more locks then
> >> Novell allows.  If that was the problem, the
> error
> >> messages will disappear.
> >> 
> >> Jim Dettman
> >> President,
> >> Online Computer Services of WNY, Inc.
> >> (315) 699-3443
> >> jimdettman at earthlink.net
> >> 
> >> -----Original Message-----
> >> From: accessd-bounces at databaseadvisors.com
> >> [mailto:accessd-bounces at databaseadvisors.com]On
> >> Behalf Of Sad Der
> >> Sent: Friday, January 16, 2004 7:26 AM
> >> To: Acces User Group
> >> Subject: [AccessD] Error 3218 "Couldn't Update;
> >> Currently Locked"
> >> 
> >> 
> >> Hi group,
> >> 
> >> We use A2K SP1 on a Novell network.
> >> occasionally the users get the following error:
> >> Error 3218 "Couldn't Update; Currently Locked"
> >> 
> >> I noticed that this occurs when a user tries to
> load
> >> interface messages into the DB. The messages have
> >> approx.
> >> 100-150 records. Total size of 12Kb.
> >> 
> >> I read on support.microsoft.com (KB302484) that
> this
> >> has
> >> to do with the number of record locks on the
> Novell
> >> server. But this KB-Article is related to A97!
> >> 
> >> What's the deal with locking in A2k?
> >> 
> >> We 'enherited' this system and error handling, if
> >> any,
> >> is
> >> really buggy. So every time this occurs we get a
> >> lot(!) of
> >> db-pollution!!
> >> 
> >> My question: What can I do to prevent this from
> >> happening?
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus


More information about the AccessD mailing list