Error: Lock Table overflow, increase -L on Server (number)
- 21 Apr 2023
- Contributors
- Print
- DarkLight
- PDF
Error: Lock Table overflow, increase -L on Server (number)
- Updated on 21 Apr 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
How do I fix lock table overflow errors?
Answer:
-L is in the OpenEdge Explorer. Under the FOUND database, there is a configuration link then default configuration. Under the default configuration is a "Lock Table Entries" line. Press the edit button, change it and save. The database has to be restarted.
Here are the detailed steps on how to change the Lock Table Entries setting and re-start the database. Note: Since the database is being re-started, you may want to make sure that all users have saved any work they are currently completing and log out of the system. These steps are completed on the FIMS server:
These are the steps if this issue is occurring in your live database:
1. Go to Start\all programs and find the Progress folder
2. In that folder click and open OpenEdge Explorer and log in
3. Once OpenEdge Explorer opens click on the link for the found database which is the live database. Your server name will be named differently but will still have the word 'found' in the name:
Here are the detailed steps on how to change the Lock Table Entries setting and re-start the database. Note: Since the database is being re-started, you may want to make sure that all users have saved any work they are currently completing and log out of the system. These steps are completed on the FIMS server:
These are the steps if this issue is occurring in your live database:
1. Go to Start\all programs and find the Progress folder
2. In that folder click and open OpenEdge Explorer and log in
3. Once OpenEdge Explorer opens click on the link for the found database which is the live database. Your server name will be named differently but will still have the word 'found' in the name:
4. After clicking the link for the found database, click the link for Configuration:
5. On left the left click on the link for configuration.found.defaultconfiguration:
6. Click the edit button on the top left:
7. In the General section find the section labeled Lock Table entries
8. Edit the Lock Table entries (-L) field and enter in a value higher than the number that occurred in the error message. You can also just set the value for 50000 which should be enough to handle any size needed going forward.
9. Click the Save button on the top left to save your change:
10. Restart the found database. There are a couple of ways to do that as outlined in this article:
How to Start and Stop a FIMS Database for On-Premises Environments
Was this article helpful?
