Subject RE: [firebird-support] Re: FB deadlock during big table indexing on Linux
Author Rick Debay
Do you have the sticky bit set for the /tmp directory? If not other
users can delete your files. You might also want to check for a /tmp
cleanup program, some distributions have them and it's possible yours is
cleaning up files too aggressively.

Rick DeBay

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of taliyev
Sent: Saturday, April 22, 2006 4:27 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: FB deadlock during big table indexing on
Linux

Here is an error that I get in the ISQL interractive mode:

Command:

SQL> alter index oag_flights_1 active;

In a 30-40 minutes I get an error:

Statement failed, SQLCODE = -902

I/O error for file "/tmp/fb_sort__9zRpkn"
-Error while trying to read from file
-No such file or directory

It looks like FB is loosing temp file handle or something like that..


--- In firebird-support@yahoogroups.com, "taliyev" <taliyev@...>
wrote:
>
> We have huge database ( 30 GB) that seems to be working ok on
> Windows. We need to port this database to Linux. Transportable backup
> file is about 20GB in size. Biggest table is about 185 millions of
> records.
>
> This backup file can be restored on the Windows server, but when
we
> try to restore it on the Linux box FB gets deadlocked when it
needs
> to activate indexes. We have managed to restore database without index

> activation. Then we have activated indexes manually one by one... all
> but the indexes on the biggest table. Any attempt to activate or drop

> and restore indexes on the 185 Mln. records table cause either
> deadlock , if run through the script, or when we run
it
> interactively, then after a certain period of time we get an error
> that FB cannot read from the temporary file in the temp directory...
> sort operation failed..
>
> We have checked , and we have enough disk space on the Linux box.
> Both Windows and Linux machines have similar hardware configurations.
> Both have about 250GB SCSI disk space and 2GB of memory.
>
> The Linux box has no problem creating indexes on the smaller
tables,
> but the big one is a trouble. All indexes are based on the single
> field with high number of values. Both machines have FB 1.5.3 in Super

> Server configuration.
>
> As I said before, this database works fine on the Windows server...
We
> have tried to play with firebird.conf parameters, but none of our
> ideas gave as any success in indexing of the big table on Linux..
>
> If anybody has any suggestions, your help will be greatly appreciated.
>






++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Visit http://firebird.sourceforge.net and click the Resources item on
the main (top) menu. Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Yahoo! Groups Links