Hi All,

This morning my nightly test cycle suddenly started generating lots of
#9480 errors. The database in question contained only 263 tables (so
well below the 4096 limit).

I traced one of the errors to a line where a simple "alter table" sql
query was executed.

-restarting the database server didn't help
-restarting the machine on which the server was running didn't help

Then I deleted the dbisam.lck file from the database directory, and all
was well again.

Any ideas on what could be causing the error in the first place?

OS: WinXP - all patches installed
DBISAM: version  4.22 C/S


TIA.

--
Robert.

Whatever you are, be a good one
===
http://robertcram.blogspot.com

Robert


I had something along these lines a year or three back. In my case it was down to creating memory tables. I think I got round it by setting exclusive to TRUE before opening so they never got added to the .lck file.

Roy Lambert

Hi Roy,

I don't use memory tables, so it must be something else in my case.

Apparently I somehow manage to drop tables without that being reflected
in the .lck file. I run my testsuite every night, so the number of
entries in the .lck file steadily grows over time, eventually resulting
in a #9480 error.

At least, that's what I think is happening...


--
Robert.

Whatever you are, be a good one
===
http://robertcram.blogspot.com

Robert


I think you are correct - I don't think tables are deleted from the .lck file - its obviously where FaceBook modelled their systems from

Roy Lambert

Robert,

<< Apparently I somehow manage to drop tables without that being reflected
in the .lck file. I run my testsuite every night, so the number of entries
in the .lck file steadily grows over time, eventually resulting in a #9480
error. >>

This is correct.  If you are constantly creating and then deleting a lot of
tables, then you will run into this error unless you remove the .lck file
occasionally.  If you can do so, I would simply remove the .lck file before
the process that you're running at night executes.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I must be misunderstanding this. Are you telling me that if I have an
application where I create and delete one table, that application will
result in an #9480 error after running it 4096 times?

Please tell me this isn't so...


--
Robert.

Whatever you are, be a good one
===
http://robertcram.blogspot.com

Robert,

<< I must be misunderstanding this. Are you telling me that if I have an
application where I create and delete one table, that application will
result in an #9480 error after running it 4096 times? >>

Yep.  Although, the issue is that the table is opened non-exclusively that
causes the lock file entry.  If you are creating and deleting temporary
tables, then setting Exclusive=True when opening the table will prevent it
from being added to the lock file.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Is the entry in the lock file related to the name of the table? In
other words: would creating and deleting a table with the same name
over and over again increase the number of lock file entries?


> Robert,
>
> << I must be misunderstanding this. Are you telling me that if I have
> an application where I create and delete one table, that application
> will result in an #9480 error after running it 4096 times? >>
>
> Yep.  Although, the issue is that the table is opened non-exclusively
> that causes the lock file entry.  If you are creating and deleting
> temporary tables, then setting Exclusive=True when opening the table
> will prevent it from being added to the lock file.



--
Robert.

Whatever you are, be a good one
===
http://robertcram.blogspot.com

Robert,

<< Is the entry in the lock file related to the name of the table? >>

Yes.

<< In other words: would creating and deleting a table with the same name
over and over again increase the number of lock file entries? >>

No.

--
Tim Young
Elevate Software
www.elevatesoft.com

Can I ask why deleting the file doesn't delete the lock file entry? I
guess there must be a good reason, and thinking about it I don't think
I'll be affected by this, but it seems odd.

/Matthew Jones/