Solved

Record Lock Threshold exceeded total violation 656

Posted on 1998-11-10
8
299 Views
Last Modified: 2008-02-01
Hi, I'm currently running an foxpro application in novell 3.12 version.  While run a particular option in the application I would get an error message from the application. "Record in used by another".  I then checked the console of the novell server and got the above "error message"  Pls help ...
0
Comment
Question by:salconen
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 12

Expert Comment

by:mark2150
ID: 1594068
Your foxpro app is in runaway mode. It's recursively locking records in database until the lock manager gets wound around the peg. Check your code and make sure that you're releasing the locks prior to asserting a new one.

M

0
 

Author Comment

by:salconen
ID: 1594069
Yes I did release it before getting new ones.  Would it be the network sides ??
0
 
LVL 1

Expert Comment

by:michelandre
ID: 1594070
At what time???
Is there backups being done?
Is there a  batch file waiting to be process then executed at night???
I think the max for locked is 10,000 locks.
0
PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

 
LVL 12

Expert Comment

by:mark2150
ID: 1594071
You've got to have a logical error somewhere. If you monitor the task from RCONSOLE/MONITOR I think you'll see it locking and locking and locking...

Sometimes you need to wait a bit tween lock release and new requests. Give the server time to digest. Try setting TRUE COMMIT ON in the NET.CFG file. This will prevent the server from pre-acknowledging writes until the disk has really written them.

M

0
 

Accepted Solution

by:
jsyring earned 10 total points
ID: 1594072
Here are the SET-parameters you need to modify:

     (the default values are for NW4.11)
     Maximum Record Locks Per Connection (default: 500, range 10 - 100000)
     Maximum File Locks Per Connection (default :250, range 10 - 1000)
     Maximum Record Locks (default :20000, range 100 - 400000)
     Maximum File Locks (default: 10000, range 100-100000)

     A rule of thumb is to double the parameters and monitor if the problem persists.

0
 

Author Comment

by:salconen
ID: 1594073
Hi jsyring got your setting, where do I have to set it and what is the syntax to set them...  Pls reply as soon as possible

Thanks
0
 

Expert Comment

by:jsyring
ID: 1594074
Salconen

All of the settings can be set in the startup.ncf file and the syntax to set them is as follows

Set Maximum Record Locks Per Connection 1000
Set Maximum File Locks Per Connection 500

I have doubled the default in each setting and would then monitor the problem. You can then set the paramaters higher if you need to. Each of these setting may effect performance so I would not go any higher thean you need to.
0
 

Author Comment

by:salconen
ID: 1594075
yeah... you're right.   but the lines need to entered in the autoexec.ncf
0

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article was originally published on Monitis Blog, you can check it  here . If you have responsibility for software in production, I bet you’d like to know more about it. I don’t mean that you’d like an extra peek into the bowels of the sour…
The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question