Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PLEASE HELP - "Lock File has Grown Too Large" in INTERBASE

506 views
Skip to first unread message

David Gellad

unread,
Nov 26, 2003, 7:04:02 PM11/26/03
to
Is it normal to have the Lock File has Grown Too Large Error with Interbase
passing through the BDE. From what I read, this is a Paradox tables
problem.

I have a Interbase 5 client/server application running on XP. I get the
this error at least once a day. Any idea what is causing this error and how
to avoid it.

THANKS for HELP ON THIS
David


Bill Todd

unread,
Nov 26, 2003, 7:31:32 PM11/26/03
to
See http://community.borland.com/article/0,1410,15256,00.html .

If you are using cached updates or schema caching you are using
Paradox tables for the cache.


--
Bill (TeamB)
(TeamB cannot respond to questions received via email)

David Gellad

unread,
Nov 26, 2003, 7:40:20 PM11/26/03
to
Bill,
You're right. I'm using Cached Updates.
Does it mean that I have to configure a directory structure and paradox
parametters the way it's described in the article. What is your
recommendation on the best setup to do.

Thks a lot for your reply.
David

"Bill Todd" <n...@no.com> wrote in message
news:g3hasv8fg8fidjcmh...@4ax.com...

Bill Todd

unread,
Nov 26, 2003, 9:23:18 PM11/26/03
to
>You're right. I'm using Cached Updates.
>Does it mean that I have to configure a directory structure and paradox
>parametters the way it's described in the article. What is your
>recommendation on the best setup to do.

There is no "best" setup. You either have the problem or you don't. :)
Any setup that gets rid of the problem is fine.

The directory structure described in the article is not necessary. The
first thing I would try is to set the Session.PrivateDir property to a
directory other than the directory where the EXE is located (sett
TSession in the on-line help for details). That will get the paradox
tables out of the EXE directory. Unless you need Local Share set to
true for other work with Paradox tables make sure it is set to false.
That should be enough to solve your problem.

Patrick Moloney

unread,
Nov 28, 2003, 10:10:10 AM11/28/03
to
I'm don't know whether the other suggestions will avoid creating lock files in
the first place, but I would look for the large lock file (*.LCK) to be sure
what problem I had. These are normally deleted when the user is finished. If a
user ends abnormally, these may not be removed properly and can grow. They can
be deleted when all users are not using them.

I don't know what your app is using tables for, but if they are temporary user
tables, make sure you have a "private directory" defined on the C: drive for
them and lock files will not be created there.

Patrick


quinn wildman

unread,
Dec 1, 2003, 3:30:21 PM12/1/03
to
As long as your private directory is local, setting local share to false
might resolve the problem.
0 new messages