Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

dBASE for DOS Error 217:Lock Table is full.

Posted on 1998-09-08
1
Medium Priority
?
447 Views
Last Modified: 2010-07-27
How do I correct this error? I can't find any locked records or any references to the table in the manual. Where is the table and how can I either reset or repair the table?
0
Comment
Question by:Daniel7
[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
1 Comment
 
LVL 9

Accepted Solution

by:
cymbolic earned 400 total points
ID: 1025655
Generally, locking has to happen so quickly that it does not go through a table in your dbase app, but is provided as a server capability.  For instance, in many of the .dbf languages, records are locked by using the server locking capability, locking only one byte in a file per record, often at some virtual address many times larger than the actual record byte address, which allows a virtual lock by the development system/application, rather than an actual physical lock on the record.  Generally, running out of locks means that you have an application problem, or most likely, a network problem that is preventing what are usually very transitory locks to complete and become unlocked.  You won't find any physical locked records marked, but you should be able to use your server Administrative tools to see what items and tables are locked on the server when you get this problem, and diagnose/track down the source of the problem from there.

Generally, closing out the application(s) generating the locks will free them up and allow you to continue, but this only works reliably when your network is not having problems as well.

Look not unto your development system or your application for information on current locks, but to your server to find them.  Look to your application for potential coding problems/methods that lock up many records without unlocking, or to your network for communication problems that don't allow the locking process to release, or to a setting maximum locks allowed on your server.
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

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

In this blog post, we’ll look at how using thread_statistics can cause high memory usage.
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
Suggested Courses

604 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