Index reuild failed with error

[Mokash]

Hi Experts...

After doing binary dump and load, while performing index rebuild i got following error (DB size was around 90 GB):

Unable to open sort file in directory /db1/sort/rhnPAzUuc, errno is 24.
Error: key insertion failed

Initially I thought there may be srt file issue, so I increased my srt file lines so it has total 125 lines of 1 GB each.

After this, I again rebuild the index for particular area in which only one table of size 24GB was present, still I got the same error.

OS - Linux
Progress version: 9.1C

I chekced my srt file..it is correct and got total 179 GB of sort space (i put all available space of server).. still same error.

Kindly suggest me on this.

Thanks in advance!!!

 

[TomBascom]

errno 24 is "too many open files". Just like George said on PEG this morning.

9.1c is ancient, obsolete and unsupported. And begging for trouble.

How many extents does your database have?

Did you check "ulimit -a" to see how many open files your are limited to?

 

[Mokash]

Hi Tom,

Thanks for your reply.

It is a main qaddb has got 36 Areas. After running ulimit -a output is

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 139264
virtual memory (kbytes, -v) unlimited


what is the solution for that?

 

[TomBascom]

# of areas is not the same as # of extents.

The limit on number of open files applies to the total number of file handles that your session has open. Many QAD installations consist of several databases simultaneously connected. You would need to count every data extent, every bi extent and every ai extent. If any of them are variable length (rather than fixed) you need to count them twice (a variable extent uses 2 file handles rather than 1).

If your total is anywhere near 1024 then you should consider increasing the number of file handles available "ulimit -n 2048" will change the limit for a particular process. You can change it systemwide by editing /etc/security/limits.conf.